Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #179503
| From | Mark Fletcher <mark27q1@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Anyone know what this means when running aptitude update? |
| Date | 2017-03-28 01:00 +0200 |
| Message-ID | <tpLMd-6Ms-11@gated-at.bofh.it> (permalink) |
| References | <tpiTU-2gQ-7@gated-at.bofh.it> <tpjwB-2ws-7@gated-at.bofh.it> <tplyp-3Xa-7@gated-at.bofh.it> <tpEB4-1AA-11@gated-at.bofh.it> <tpFns-2iK-31@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Mar 27, 2017 at 06:06:05PM +0200, Frank wrote: > Op 27-03-17 om 17:14 schreef Mark Fletcher: > >Well, switching from http.debian.net to deb.debian.org seems to have > >fixed that one. The error relating to that has gone away. > > Don't be surprised if it comes back. I think it may just have selected a > different mirror now, but you can't be certain it will always pick that one. Right. So far it hasn't but I get what you are saying. I don't believe, however, that I ran for weeks getting redirected to the same mirror and getting the same error and then at the moment I switched my settings the mirror changed and solved the problem by coincidence. Clearly the change had an impact. So that's good. > > >>>wget -qO- https://dl.google.com/linux/linux_signing_key.pub | sudo > >>>apt-key add - > >> > >>No, please do NOT use "apt-key add" but instead download the key and put > >>it as a file with the suffix ".gpg" into the directory > >>/etc/apt/trusted.gpg.d/ > >> > >I downloaded the file from the above URL, and copied it as root to > >/etc/apt/trusted.gpg.d as instructed. Since all the other files in that > >directory were owned by root I made sure this one was too. And I renamed > >it to add .gpg on the end. > > That's for binary key files. This one is ascii armoured, so it needs an .asc > 'extension'. > Right, for the key issue, that has taken me right back to where I started: W: There is no public key available for the following key IDs: 1397BC53640DB551 Now that is the only complaint, which is a significant improvement on where I started thanks to the fixed mirror, but the key ID issue isn't solved. I tried naming the file linux_signing_key.pub.asc and linux_signing_key.pub.gpg.asc . Neither worked (in the sense that the warning above appeared). Since this is the warning I was getting to start with, it almost feels like this file is either not being read (although naming it ending .gpg causes mayhem so I guess it is) or it doesn't contain what I need. I downloaded it using the wget command above except without the -qO- because I wanted to see what wget was doing and I didn't want the downloaded result going to standard output. Possibly stupid question -- this is Jessie, does this mechanism of dropping the files in trusted.gpg.d work properly in Jessie or is it new? Mark
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-26 18:10 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-26 18:50 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-26 21:00 +0200
Re: Anyone know what this means when running aptitude update? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-03-26 21:00 +0200
Re: Anyone know what this means when running aptitude update? Reco <recoverym4n@gmail.com> - 2017-03-26 21:10 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-26 21:20 +0200
Re: Anyone know what this means when running aptitude update? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-03-26 21:50 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-26 22:10 +0200
Re: Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-27 01:30 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-27 07:50 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-27 11:10 +0200
Re: Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-27 17:20 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-27 18:10 +0200
Re: Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-28 01:00 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-28 07:50 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-28 10:10 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-28 12:10 +0200
Re: Anyone know what this means when running aptitude update? Frank <zuiderduin@gmx.com> - 2017-03-28 13:30 +0200
Re: Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-28 14:40 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-28 10:00 +0200
Re: Anyone know what this means when running aptitude update? Mark Fletcher <mark27q1@gmail.com> - 2017-03-28 14:30 +0200
Re: Anyone know what this means when running aptitude update? Sven Hartge <sven@svenhartge.de> - 2017-03-28 16:20 +0200
csiph-web