Hi Mathias,

Good that you ask.

On 10-03-2023 11:51, Mathias Behrle wrote:
pywebdav currently suffers from missing adaption to Python 3.11. As you know it
is not appropriate to force the decision of our quite late move to Python 3.11
on upstreams or package maintainers. So what I expect to happen is that
pywebdav won't be part of bookworm (i.e. removed from testing), but stay in
unstable (waiting for upstream maintainers to catch up with migration to Python
3.11). I would have assumed that this is already the case with
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029283

No, because that bug only affects the package in unstable. Check: https://bugs.debian.org/cgi-bin/version.cgi?found=pywebdav%2F0.10.0-1;package=src%3Apywebdav;absolute=0;collapse=1;info=1

so basically I don't get what this immediately closed bug is meant for.

Well, without me filing this bug, pywebdav would not be (auto)removed from bookworm, because there is no RC bug affecting the version in bookworm. Because the version in testing passes its autopkgtest (with Python 3.11), so neither bunk (I assume) nor me were seeing this as a Python 3.11 problem. I file most of my "fails to migrate to testing for too long" bugs closing the bug with the version in unstable, because I don't want the bug to *block* migration once the underlying problem is solved. The underlying problem regularly either has it's own bug report already, or may be solvable without changes to the bug I file. To avoid busywork for maintainers, I close the bug when I file it. Because autoremoval knows to only care about bugs affecting testing.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to