Hi,

I have completed a rebuild of the reverse dependencies of python3-click in order
to add support for version 8.3.3. The results are available here:

https://people.debian.org/~cipriano/custom-mass-rebuild/python3-click-8.3.3/

Of the 21 failures, I believe only 11 are related to python3-click. I
opened bug reports for those, which can be found at:

https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-python%40lists.debian.org&tag=python3-click-8.3.3

Besides that, I believe there are other packages, such as typer, that
are working correctly but require this new version of python3-click in
order to be updated to the latest version.

Ben file:

title = "python-click";
is_affected = .build-depends ~ /python3-click/;
is_good = !.uninstallable ~ /yes/;
is_bad = .uninstallable ~ /yes/;

This bug was fixed in the latest version of python-semantic-release.

Hi,

It's been more than two months since I opened the transition bug for
python3-click 8.3.3. At the time, I rebuilt all reverse dependencies [1]
and found that only 21 packages failed to build.

Of those 21 failures, I believed only 11 were actually related to the
new version of click.

During DebCamp 2026, I worked on the bugs I had filed. Here's the
current status:

#1098529 anymarkup - no reverse dependencies, and no upstream activity for seven years.
#1136137 dask.distributed - already broken.
#1136143 python-yamlfix - already broken.
#1136140 python-check-jsonschema - no reverse dependencies, although it may still be useful for the GCC testsuite.
#1136141 python-mkdocs - patch available.

The remaining bugs are done.

Given the current state, I think it's time to upload python3-click 8.3.3
to unstable and raise the remaining transition bugs to serious severity.

[1]: https://people.debian.org/~cipriano/custom-mass-rebuild/python3-click-8.3.3/

Thanks a LOT for doing this work! And sorry I dropped the ball after
I tried to do it last time...

G'luck,
Peter

Thanks for your kind words! No worries.

Control: reopen -1

You must have gotten confused and closed the wrong bug? This is about a
transition for python-click, not about individual issues in rdeps.

Cheers,
Emilio

There's a few regressions listed here. Can you take a look at them?

https://qa.debian.org/excuses.php?experimental=1&package=python-click

Cheers,
Emilio

Yes, I accidentally closed the wrong bug. A few hours later, I corrected
the mistake by sending an email to control@b.d.o:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136152;msg=16

Thanks for pointing this out. I'll take a look!

Hi,

I believe the remaining issues are now in a good state. Here's the
current status of the remaining regressions:

1. Autopkgtest failures unrelated to click (also failing in unstable):

apksigcopier
httpx
pqconnect

2. Autopkgtests that passed after being re-triggered:

cfgrib
google-auth-oauthlib
patroni

3. Fixed:

beangulp
scriv
sphinx-theme-builder
python-whey

Thanks to Puida for fixing the last three.

4. python-click itself was failing, but the latest version in sid
already includes a patch that fixes the autopkgtest. This issue arose
during the transition.

5. Remaining transition bugs:

#1098529 anymarkup - no reverse dependencies, and no upstream activity for seven years.
#1136140 python-check-jsonschema - no reverse dependencies, although it may still be useful for the GCC testsuite.
#1136137 dask.distributed - already broken.
#1136143 python-yamlfix - already broken.
#1136141 python-mkdocs - patch available.
#1142373 python-softlayer - no patch available (new bug).

Control: tags -1 confirmed

Please go ahead.

Cheers,
Emilio

Hi Emilio,

python-click migrated to testing.