On 3/06/2016 10:38 p.m., David Kalnischkies wrote: > > btw: I just checked: I introduced the first of the two finds (which is > the more obvious problem as that codepath is used more) on 7 Jul 2015 > (25f27319) [the other is 6 Dec 2015], so that problem isn't recent but > lingers there since 1.1 and I have to wonder if something changed in > regards to this on hurd (or d-i) or if that really is some huge > Baader-Meinhof bias… [2] > > (and I am bit surprised we had nobody on non-hurd complain about > 'strange' messages being emitted while using apt-key – but perhaps that > just means nobody is using apt-key anymore… if only that were true…)
FWIW; I had these messages show up around the end of year after upgrading a previous install. But that installation was screwed up in may ways so I didn't report bugs. The usual apt-keys solution seemed to fix it then but not recently. This bug was already being discussed before I got satisfied that its a bug in apt and not myself. Amos
