On Fri, Apr 28, 2023 at 07:58:35PM +0200, Fabian Grünbichler wrote: > 2) if the "fork point" corresponds to the version in the soon-to-be-old > stable release, and the semver suffix package is still in testing when > that becomes the stable release (as then the unversioned package in > (old)stable and the semver suffix package in (new)stable ship the same > path) > > is 2) actually true for any of the filed bugs at the moment? if not, > then IMHO we can ignore this until bookworm is out the door, decide on > and ship the fix in debcargo, and ease out the problematic packages by > updating them (basically option 5). like Peter noted below, these are > packages almost certainly only installed on developer machines (or the > odd programmer's who doesn't use the stock, upstream way of doing rust > developement) and in 'unclean' build environments, not on regular > servers or end user machines.
I guess I could have checked that myself before writing - rust-block-buffer is in bullseye with version 0.9.0-4, and rust-block-buffer-0.9 is in bookworm with version 0.9.0-1, so yeah, this affects bullseye->bookworm upgrades, although with all the caveats Peter and I mentioned, which might still be an argument for not "hotfixing" this in bookworm now.
