Control: block 1098533 by -1 Control: block 1098535 by -1 Control: block 1098539 by -1 Control: block 1098575 by -1 Control: block 1098591 by -1 Control: block 1098596 by -1 Control: block 1098598 by -1 Control: block 1098599 by -1 Control: block 1098601 by -1 Control: block 1098607 by -1 Control: block 1098612 by -1 Control: block 1098614 by -1 Control: block 1098616 by -1 Control: block 1098619 by -1 Control: block 1098627 by -1 Control: block 1098628 by -1 Control: block 1098630 by -1 Control: block 1098632 by -1 Control: block 1098633 by -1 Control: block 1098634 by -1 Control: block 1098635 by -1
On Fri, Feb 21, 2025 at 02:34:12PM -0700, Soren Stoutner wrote: > Just to add a bit of additional information, 8.2.0 has been tagged but not > released, which > was probably the confusion that caused it to be uploaded to unstable. > > https://github.com/pallets/click/tags > > https://github.com/pallets/click/releases > > https://pypi.org/project/click/ > > My guess is this is just a bit of upstream confusion. Also perhaps https://github.com/pallets/click/pull/2844. > But the bigger point is that the 8.2.0 release introduces breaking changes > and needs to > be staged in experimental first to give dependent projects time to adjust. I think at least the following RC bugs are due to this - all these packages build cleanly for me with the previous version of python-click: * #1098533 (beancount) * #1098535 (black) * #1098539 (celery) * #1098575 (magic-wormhole) * #1098591 (python-aiovlc) * #1098596 (python-consolekit) * #1098598 (python-dotenv) * #1098599 (python-flasgger) * #1098601 (python-inline-snapshot) * #1098607 (python-pyproject-parser) * #1098612 (python-shippinglabel) * #1098614 (python-uiprotect) * #1098616 (python-whey) * #1098619 (pytrydan) * #1098627 (scriv) * #1098628 (sarsen) * #1098630 (sqlfluff) * #1098632 (tahoe-lafs) * #1098633 (towncrier) * #1098634 (typer) * #1098635 (ytcc) This is just what I got from skimming through https://udd.debian.org/bugs/?release=trixie&ftbfs=only&merged=ign&fnewer=only&fnewerval=14&flastmodval=14&rc=1&sortby=id&sorto=asc&format=html#results and testing ones that looked plausibly related, so there may be others. And it may not technically be the case that all of these are strictly blocked on a revert; I see that #1098595 (python-click-plugins) and #1098629 (sphinx-theme-builder) were fixed more directly. But with this many failures, I tend to agree with Soren that it would make sense to revert and wait for a proper upstream release so that it's more likely that upstreams will sort this out. python-click 8.2.0+really8.1.8-1, maybe? -- Colin Watson (he/him) [cjwat...@debian.org]
