Github messages for voidlinux
 help / color / mirror / Atom feed
From: Vinfall <Vinfall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] buku: fix deprecation warning for python3>=3.11
Date: Wed, 16 Nov 2022 11:26:35 +0100	[thread overview]
Message-ID: <20221116102635.vnKYpfmNdrbiUNfmkVBuAr-YZv1oqbfAmgWzPv8vKoo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40551@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

There is an updated pull request by Vinfall against master on the void-packages repository

https://github.com/Vinfall/void-packages master
https://github.com/void-linux/void-packages/pull/40551

buku: fix deprecation warning for python3>=3.11
#### Changes

Followup of #40526 and jarun/buku/pull/605.

Add the necessary patch to remove the DeprecationWarning `'cgi' is deprecated and slated for removal in Python 3.13` in buku caused by Python3 version update (3.11 as of writing).

#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures:
  - armv6l 
- `xlint` also reports no error.

A patch file from https://github.com/void-linux/void-packages/pull/40551.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-40551.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]



  parent reply	other threads:[~2022-11-16 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16  3:29 [PR PATCH] " Vinfall
2022-11-16  7:29 ` classabbyamp
2022-11-16 10:26 ` [PR PATCH] [Closed]: " Vinfall
2022-11-16 10:26 ` Vinfall [this message]
2022-11-16 10:35 ` Vinfall
2022-11-16 10:36 ` Vinfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221116102635.vnKYpfmNdrbiUNfmkVBuAr-YZv1oqbfAmgWzPv8vKoo@z \
    --to=vinfall@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).