Control: tag -1 moreinfo On Thu, Jul 25, 2024 at 09:24:58PM GMT, mh wrote: > Package: apt > Version: 2.9.6 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where > appropriate *** > > * What led up to the situation? > > Err:3 http://dellopti:3142/deb.debian.org/debian unstable InRelease > At least one invalid signature was encountered. > (only a part of the errors) > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > apt(-get) update > * What was the outcome of this action? > see above > * What outcome did you expect instead? > > If there IS an error with a signature apt must have seen it. How will > the user know which particular signature creates *allegedly* problems. > Here with this computer this problem happened all of a sudden (I make > daily dist-upgrade(s)) with repos which work fine with my laptop. So I > now have apt blocked by this problem, apt not telling me by which > signature it feels offended and offers effectivly only a > I'm-not-telling-you-burger. Please improve the message by giving > usefull information.
If you only saw that error and no details later on, then no - we did not get any more details from gpgv or we missed parsing it. gpgv's status fd output is very opaque, it might just not have told us anything or anything we understand and exited with 1. We're going to need the sources file containing the source, the key configured for the source, and the actual InRelease file that failed to validate to analyse this further. Alternatively, it may be that -o Debug::Acquire::gpgv=1 will give enough information. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
