Re: update messages
On Thu, Dec 28, 2006 at 01:04:52PM -0500, Greg Folkert wrote:
> > Reading package lists... Done
> > W: There are no public key available for the following key IDs:
> > A70DAF536070D3A1
> > W: GPG error: http://www.debian-multimedia.org etch Release: The following signa
> > tures couldn't be verified because the public key is not available: NO_PUBKEY 07
> > DC563D1F41B907
> > W: You may want to run apt-get update to correct these problems
> >
> install the "debian-keyring" and "debian-archive-keyring"
>
> That should take care of your issue. Once you do that, the keys will be
> in place and no W: (warnings) will be around.
Thanks - that helped. But I am still being left with:
Reading package lists... Done
W: GPG error: http://www.debian-multimedia.org etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
W: You may want to run apt-get update to correct these problems
I thought perhaps the 'NO_PUBKEY' signature name might imply that this
was intentional - but if that is so then presumably everyone with the
multimedia stuff in their sources.list should be seeing this warning??
> Ign just means Ignore. Since the Release file isn't critical for now, it
> is no big deal.
I tried upgrading 'aptitude' with
apt-get install aptitude
because my version didn't quite match the html documentation I just
installed and am reading through, but now when I try to run the 'u[pdate]'
command it crashes out with:
aptitude: symbol lookup error: aptitude: undefined symbol: _ZN9pkgPolicyD2Ev
which doesn't help my confidence :-/ I'm not sure if this new error was
introduced by the upgrade or by the keyring install, as I didn't try
between the two actions.
I suppose I could just go ahead with a dist-upgrade and hope that resolves
things (on the asumption that this error was just some slipup in the
dependency management).
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
Reply to: