Re: apt-get update public key problem
On 1/12/06, Richard Lyons <[EMAIL PROTECTED]> wrote: > Thanks for that. It doesn't actually work for me for reasons I'll read > up when I have time. > > bordello:/home/richard# gpg --keyserver hkp://wwwkeys.eu.pgp.net --recv-keys > 1F41B907 > gpg: requesting key 1F41B907 from hkp server wwwkeys.eu.pgp.net > gpg: key 1F41B907: duplicated user ID detected - merged > gpg: key 1F41B907: "Christian Marillat <[EMAIL PROTECTED]>" not > changed > gpg: Total number processed: 1 > gpg: unchanged: 1 > bordello:/home/richard# gpg --armor --export 1F41B907 | apt-key add - > gpg: no ultimately trusted keys found > OK > > (This was the second time I tried it, evidently.) You might have to run "apt-get update" a couple of times. aptitude kept complaining about it to me until the next day, when everything magically worked. -- Michael A. Marsh http://www.umiacs.umd.edu/~mmarsh http://mamarsh.blogspot.com
Re: apt-get update public key problem
On Thursday, 5 January 2006 at 9:13:41 -0800, John L Fjellstad wrote: > Richard Lyons <[EMAIL PROTECTED]> writes: > > > Fetched 2972kB in 1m10s (42.4kB/s) > > Reading package lists... Done > > W: GPG error: ftp://ftp.nerim.net sid Release: The following signatures > > couldn't be verified because the public key is not available: NO_PUBKEY > > 07DC563D1F41B907 > > W: Bizarre Error - File size is not what the server reported 2970292 > > 3951594 > > W: You may want to run apt-get update to correct these problems > > You need to add the marillat keys. Check the faq here: > http://debian.video.free.fr/faq.html Thanks for that. It doesn't actually work for me for reasons I'll read up when I have time. bordello:/home/richard# gpg --keyserver hkp://wwwkeys.eu.pgp.net --recv-keys 1F41B907 gpg: requesting key 1F41B907 from hkp server wwwkeys.eu.pgp.net gpg: key 1F41B907: duplicated user ID detected - merged gpg: key 1F41B907: "Christian Marillat <[EMAIL PROTECTED]>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 bordello:/home/richard# gpg --armor --export 1F41B907 | apt-key add - gpg: no ultimately trusted keys found OK (This was the second time I tried it, evidently.) -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get update public key problem
Richard Lyons <[EMAIL PROTECTED]> writes: > Fetched 2972kB in 1m10s (42.4kB/s) > Reading package lists... Done > W: GPG error: ftp://ftp.nerim.net sid Release: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > 07DC563D1F41B907 > W: Bizarre Error - File size is not what the server reported 2970292 > 3951594 > W: You may want to run apt-get update to correct these problems You need to add the marillat keys. Check the faq here: http://debian.video.free.fr/faq.html -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get update public key problem
Worked for me as well Thanks! --- Begin Message --- On Wed January 4 2006 11:41 am, John Biederstedt wrote: > Today I ran apt-get update and got this: > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release.gpg > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release > Get:1 http://ftp.us.debian.org testing Release.gpg [378B] > Hit http://ftp.us.debian.org testing Release > Ign http://ftp.us.debian.org testing Release > Hit http://ftp.us.debian.org testing/main Packages > Hit http://ftp.us.debian.org testing/main Sources > Get:2 http://security.debian.org testing/updates Release.gpg [189B] > Hit http://security.debian.org testing/updates Release > Hit http://security.debian.org testing/updates/main Packages > Hit http://security.debian.org testing/updates/contrib Packages > Fetched 379B in 8s (44B/s) > Reading package lists... Done > W: GPG error: http://ftp.us.debian.org testing Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 010908312D230C5F > W: You may want to run apt-get update to correct these problems > > > > I install debian-keyring, and set up a link for debian-archive so > apt-key update would work. I became root and imported the debian > keyring (all of them), and added the debian-roles keyring as well. I > also assigned ultimate trust to the debian role keys. > > The above still happens. From googling around, there seems to be a bug > referencing this or something like it, but I'm curious if others have > had the same problem, and if anyone has found a workaround, or a way to > verify the packages. I've hunted around www.debian.org for keys, and am > still looking. I'd like to know if anyone is aware if this is a bug, or > if the archives are compromised somehow. I'm sending this to > debian_user since it seems to me more like a user issue than a real > testing issue. I (as well as others) was having this problem as well untill I saw a message from a Mr. Joey Hess. As per Mr. Hess' instructions, run the following command line: wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key add - Once I ran that, the key problem vanished. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool. pgpBC9h97rGQf.pgp Description: PGP signature --- End Message ---
Re: apt-get update public key problem
On 04 Jan 2006, Rick Friedman wrote: > On Wed January 4 2006 12:28 pm, Tom wrote: > > [04/01/2006 -- 18:10u] Rick Friedman: > > > I (as well as others) was having this problem as well untill I saw a > > > message from a Mr. Joey Hess. As per Mr. Hess' instructions, run the > > > following command line: > > > > > > wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key > > > add - > > > > > > Once I ran that, the key problem vanished. > > > > Maybe the problem vanished for people using the us mirror, but > > ftp.de.debian.org surely isn't okay just yet. I assume other mirrors > > have the same problem, or if it's not about the mirrors: other people > > have the same problem. > > Touché. I didn't realize that using the US mirror made a difference. Hmmm. > > Rick > -- > Rick's Law: What cannot be imagined will be accomplished by a fool. I'm also using ftp.de.debian.org. The error went away yesterday after I imstalled the key as above but it's back again today. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get update public key problem
On Wednesday, 4 January 2006 at 20:58:05 -0500, Rick Friedman wrote: > On Wed January 4 2006 12:28 pm, Tom wrote: > > [04/01/2006 -- 18:10u] Rick Friedman: > > > I (as well as others) was having this problem as well untill I saw a > > > message from a Mr. Joey Hess. As per Mr. Hess' instructions, run the > > > following command line: > > > > > > wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key > > > add - > > > > > > Once I ran that, the key problem vanished. > > > > Maybe the problem vanished for people using the us mirror, but > > ftp.de.debian.org surely isn't okay just yet. I assume other mirrors > > have the same problem, or if it's not about the mirrors: other people > > have the same problem. > > Touché. I didn't realize that using the US mirror made a difference. Hmmm. Hmmm... I wish I understood GPG. FWIW, below is what I just got one of my sid systems after running the wget/apt-key command above. Prior to that I got a list of GPG errors, one for each mirror in sources.list, so the european mirrors are all dealt with by the added key. I don't know what the "Bizarre Error" is all about though! (I've pruned out the detailed hits for brevity): bordello:/home/richard# apt-get update Get:1 http://debian.uni-essen.de sid Release.gpg [378B] Hit http://debian.uni-essen.de sid Release [...] Get:2 ftp://mirror.ox.ac.uk sid Release.gpg [378B] Get:3 ftp://ftp.nerim.net sid Release.gpg [189B] Hit ftp://mirror.ox.ac.uk sid Release Hit ftp://ftp.nerim.net sid Release Ign ftp://ftp.nerim.net sid Release Get:4 ftp://mirror.ox.ac.uk sid/main Packages [2970kB] Hit ftp://ftp.nerim.net sid/main Packages Get:5 ftp://ftp.unina.it sid Release.gpg [378B] Hit ftp://ftp.unina.it sid Release [...] Hit ftp://mirror.ox.ac.uk sid/non-free Packages [...] Fetched 2972kB in 1m10s (42.4kB/s) Reading package lists... Done W: GPG error: ftp://ftp.nerim.net sid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907 W: Bizarre Error - File size is not what the server reported 2970292 3951594 W: You may want to run apt-get update to correct these problems -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get update public key problem
On Wed January 4 2006 12:28 pm, Tom wrote: > [04/01/2006 -- 18:10u] Rick Friedman: > > I (as well as others) was having this problem as well untill I saw a > > message from a Mr. Joey Hess. As per Mr. Hess' instructions, run the > > following command line: > > > > wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key > > add - > > > > Once I ran that, the key problem vanished. > > Maybe the problem vanished for people using the us mirror, but > ftp.de.debian.org surely isn't okay just yet. I assume other mirrors > have the same problem, or if it's not about the mirrors: other people > have the same problem. Touché. I didn't realize that using the US mirror made a difference. Hmmm. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool.
Re: apt-get update public key problem
[04/01/2006 -- 18:10u] Rick Friedman: > I (as well as others) was having this problem as well untill I saw a message > from a Mr. Joey Hess. As per Mr. Hess' instructions, run the following > command line: > > wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key add - > > Once I ran that, the key problem vanished. Maybe the problem vanished for people using the us mirror, but ftp.de.debian.org surely isn't okay just yet. I assume other mirrors have the same problem, or if it's not about the mirrors: other people have the same problem. Cheers, Tom -- "Es bückt sich der Mann, um durch das Tor in das Innere zu sehen." ---(Franz Kafka, Vor dem Gesetz) np: Kraftwerk - Nummern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get update public key problem
On Wed January 4 2006 11:41 am, John Biederstedt wrote: > Today I ran apt-get update and got this: > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release.gpg > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release > Get:1 http://ftp.us.debian.org testing Release.gpg [378B] > Hit http://ftp.us.debian.org testing Release > Ign http://ftp.us.debian.org testing Release > Hit http://ftp.us.debian.org testing/main Packages > Hit http://ftp.us.debian.org testing/main Sources > Get:2 http://security.debian.org testing/updates Release.gpg [189B] > Hit http://security.debian.org testing/updates Release > Hit http://security.debian.org testing/updates/main Packages > Hit http://security.debian.org testing/updates/contrib Packages > Fetched 379B in 8s (44B/s) > Reading package lists... Done > W: GPG error: http://ftp.us.debian.org testing Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 010908312D230C5F > W: You may want to run apt-get update to correct these problems > > > > I install debian-keyring, and set up a link for debian-archive so > apt-key update would work. I became root and imported the debian > keyring (all of them), and added the debian-roles keyring as well. I > also assigned ultimate trust to the debian role keys. > > The above still happens. From googling around, there seems to be a bug > referencing this or something like it, but I'm curious if others have > had the same problem, and if anyone has found a workaround, or a way to > verify the packages. I've hunted around www.debian.org for keys, and am > still looking. I'd like to know if anyone is aware if this is a bug, or > if the archives are compromised somehow. I'm sending this to > debian_user since it seems to me more like a user issue than a real > testing issue. I (as well as others) was having this problem as well untill I saw a message from a Mr. Joey Hess. As per Mr. Hess' instructions, run the following command line: wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key add - Once I ran that, the key problem vanished. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool. pgphkCCF1IGSO.pgp Description: PGP signature
Re: apt-get update public key problem
I`ve had this on all my testing/unstable machines today On Wednesday 04 January 2006 17:41, John Biederstedt wrote: > Today I ran apt-get update and got this: > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release.gpg > Ign cdrom://[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 > Binary-1 (20051107)] etch Release > Get:1 http://ftp.us.debian.org testing Release.gpg [378B] > Hit http://ftp.us.debian.org testing Release > Ign http://ftp.us.debian.org testing Release > Hit http://ftp.us.debian.org testing/main Packages > Hit http://ftp.us.debian.org testing/main Sources > Get:2 http://security.debian.org testing/updates Release.gpg [189B] > Hit http://security.debian.org testing/updates Release > Hit http://security.debian.org testing/updates/main Packages > Hit http://security.debian.org testing/updates/contrib Packages > Fetched 379B in 8s (44B/s) > Reading package lists... Done > W: GPG error: http://ftp.us.debian.org testing Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 010908312D230C5F > W: You may want to run apt-get update to correct these problems > > > > I install debian-keyring, and set up a link for debian-archive so > apt-key update would work. I became root and imported the debian > keyring (all of them), and added the debian-roles keyring as well. I > also assigned ultimate trust to the debian role keys. > > The above still happens. From googling around, there seems to be a bug > referencing this or something like it, but I'm curious if others have > had the same problem, and if anyone has found a workaround, or a way to > verify the packages. I've hunted around www.debian.org for keys, and am > still looking. I'd like to know if anyone is aware if this is a bug, or > if the archives are compromised somehow. I'm sending this to > debian_user since it seems to me more like a user issue than a real > testing issue. > > Any info is greatly apperciated, > > John -- C. Hurschler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
