Control: affects 1070688 + gpg-from-sq apt Hi Farblos, all--
Thanks for this detailed bug report (https://bugs.debian.org/1070688). I'm a bit confused about the following: On Wed 2024-05-08 11:07:28 +0200, Farblos wrote: > Never mind. During one of the last t64 upgrade orgies package gpg-sq got > installed on my system and succeeded to install the diversion to /usr/bin/gpg. > And the sequoia replacement is not very feature complete, as they continue > to stress themselfes. gpg-sq doesn't install any diversions to my knowledge. the only diversions that might be installed are in gpg-from-sq or gpgv-from-sq. If those packages were on your system, then they could indeed have installed a diversion. But nothing explicitly depends on those packages (try running "apt rdepends gpg{,v}-from-sq") so i'm not sure how they got installed during an upgrade. Perhaps it has something to do with the fact that the packages use the Provides field? If you didn't deliberately install either of the *-from-sq packages, and they ended up on your system, is there some way that you can replicate the upgrade path? I'd like to understand that better, as i don't think it should have happened by accident. Perhaps there is some signal either package can give to apt to help it avoid that problem in the future? > For example, referencing a recipient by exact name with "=<recipient>" > does not work in gpg-sq, either. Thanks, i've reported this part upstream: https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/74 --dkg
signature.asc
Description: PGP signature
