On Sat, Mar 03, 2007 at 02:44:29PM +0100, Gerfried Fuchs wrote:
> * Anthony Towns <aj@azure.humbug.org.au> [2007-02-28 14:46]:
> > AFAICS, update-notifier/update-manager just uses regular python-apt
> > to handle all this stuff, which should go through the same code path
> > as aptitude and apt-get. Unless you've got some way of reproducing the
> > problem, I don't think there's a bug here.
>  It's strange - I can't reproduce it myself anymore.  But it happened
> more than once, and the only thing I could think of at that time was
> update-notifier.

My guess would be you hit the archive signing key change, which would've
given you an error until you upgraded the archive signing keyring. That
should be much less of a problem in future with the much longer validity
of the new key.

Cheers,
aj

Attachment: signature.asc
Description: Digital signature

Reply via email to