Updating khal to fix RC bug #1023341

2022-12-15 Thread Daniele Tricoli
Hello, I tried to update khal to block the autoremoval from testing (due #1023341) but it's not clear to me how to import metadata used to parse the package version with uscan¹ during repack of the tarball. PKG-INFO and the egg.info directory are on salsa¹ upstream branch but I'm not able to

Re: Python 3.11 for bookworm?

2022-12-15 Thread Thomas Goirand
On 12/13/22 10:57, c.bu...@posteo.jp wrote: Am 13.12.2022 10:15 schrieb Timo Röhling: One remaining problem is the unmaintained nose package [...] done some work patching up nose This question is just for my learning: Why is nose patched? Upstream nose is unmaintained for years. I

Re: Python 3.11 for bookworm?

2022-12-15 Thread Thomas Goirand
On 12/13/22 00:51, Graham Inggs wrote: Dear Python Team Looking at the current state of the 'adding Python 3.11 as a supported version' transition [1], the tracker [2] shows only 12 red packages (excluding unknowns and packages not in testing) remaining, copied below for reference. We believe

Re: Python 3.11 for bookworm?

2022-12-15 Thread Thomas Goirand
On 12/13/22 13:34, Julian Gilbey wrote: Hi Graham, On Mon, Dec 12, 2022 at 11:51:11PM +, Graham Inggs wrote: Dear Python Team Looking at the current state of the 'adding Python 3.11 as a supported version' transition [1], the tracker [2] shows only 12 red packages (excluding unknowns and

Re: Python 3.11 for bookworm?

2022-12-15 Thread Dmitry Shachnev
On Thu, Dec 15, 2022 at 04:08:29PM +0100, Thomas Goirand wrote: > It's unfortunately sometimes a bit harder than what one may think. Removing > Nose from (build-)depends in some cases is hard, and IMO we started this > process a way too late. Hopefully, Trixie will be nose-free! In the mean >