Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Unkown Synaptic MessageI would be grateful if someone would explain the following for me: W: There are no public key available for the following key IDs: This appeared during a package reload. Many thanks. Peter HB -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Unkown Synaptic Message
On Mon, Nov 27, 2006 at 17:10:20 +0000, Peter Hillier-Brook wrote:
> I would be grateful if someone would explain the following for me:
>
> W: There are no public key available for the following key IDs:
> A70DAF536070D3A1
>
> This appeared during a package reload.
There is currently a transition to a new archive signing key for Etch.
For the moment you can ignore this message since the Release files are
also still signed with the old key. Key updates will be handled
automatically for you if you install the debian-archive-keyring package.
--
Regards,
Florian
--
Unkown Synaptic Message
Florian Kulzer wrote:
> On Mon, Nov 27, 2006 at 17:10:20 +0000, Peter Hillier-Brook wrote:
>> I would be grateful if someone would explain the following for me:
>>
>> W: There are no public key available for the following key IDs:
>> A70DAF536070D3A1
>>
>> This appeared during a package reload.
>
> There is currently a transition to a new archive signing key for Etch.
> For the moment you can ignore this message since the Release files are
> also still signed with the old key. Key updates will be handled
> automatically for you if you install the debian-archive-keyring package.
>
Many thanks for responding so helpfully.
Peter HB
--
Unkown Synaptic Message
Peter Hillier-Brook(phb@hbsys.plus.com) is reported to have said:
> I would be grateful if someone would explain the following for me:
>
> W: There are no public key available for the following key IDs:
> A70DAF536070D3A1
>
> This appeared during a package reload.
And the answer to this question was first answered on the 20th on this
list, as well as many times since. Googleing or searching this
would/should be your first resource.
WT
--
Everyone can be taught to sculpt: Michelangelo would have had to be
taught how __not to. So it is with the great programmers.
_______________________________________________________
--
Unkown Synaptic Message
On Monday 27 November 2006 23:42, Wayne Topa wrote:
> Peter Hillier-Brook(phb@hbsys.plus.com) is reported to have said:
> > I would be grateful if someone would explain the following for me:
> >
> > W: There are no public key available for the following key IDs:
> > A70DAF536070D3A1
> >
> > This appeared during a package reload.
>
> And the answer to this question was first answered on the 20th on this
> list, as well as many times since. Googleing or searching this
> would/should be your first resource.
>
Recently I started getting the errors that the packages are "Unsigned", so
there ain't no problem of the keys not matching here.
Anybody experiencing the same problem?
BTW I am using apt-get :)
--
Regards,
Amit.
http://copperskullcprogramming.blogspot.com
--
Unkown Synaptic Message
On Tue, Nov 28, 2006 at 15:32:20 +0530, Amit Joshi wrote:
> On Monday 27 November 2006 23:42, Wayne Topa wrote:
> > Peter Hillier-Brook(phb@hbsys.plus.com) is reported to have said:
> > > I would be grateful if someone would explain the following for me:
> > >
> > > W: There are no public key available for the following key IDs:
> > > A70DAF536070D3A1
> > >
> > > This appeared during a package reload.
> >
> > And the answer to this question was first answered on the 20th on this
> > list, as well as many times since. Googleing or searching this
> > would/should be your first resource.
> >
>
> Recently I started getting the errors that the packages are "Unsigned", so
> there ain't no problem of the keys not matching here.
> Anybody experiencing the same problem?
> BTW I am using apt-get :)
Which packages are unsigned? What is the output of
ls /var/lib/apt/lists/*_Release{,.gpg}
--
Regards,
Florian
--
Unkown Synaptic Message
On Tuesday 28 November 2006 18:08, Florian Kulzer wrote:
> On Tue, Nov 28, 2006 at 15:32:20 +0530, Amit Joshi wrote:
> > On Monday 27 November 2006 23:42, Wayne Topa wrote:
> > > Peter Hillier-Brook(phb@hbsys.plus.com) is reported to have said:
> > > > I would be grateful if someone would explain the following for me:
> > > >
> > > > W: There are no public key available for the following key IDs:
> > > > A70DAF536070D3A1
> > > >
> > > > This appeared during a package reload.
> > >
> > > And the answer to this question was first answered on the 20th on this
> > > list, as well as many times since. Googleing or searching this
> > > would/should be your first resource.
> >
> > Recently I started getting the errors that the packages are "Unsigned",
> > so there ain't no problem of the keys not matching here.
> > Anybody experiencing the same problem?
> > BTW I am using apt-get :)
>
> Which packages are unsigned? What is the output of
Well..it was just a regular update;upgrade procedure, so I don't really
remember...
>
> ls /var/lib/apt/lists/*_Release{,.gpg}
>
> --
> Regards,
> Florian
debian:~# ls /var/lib/apt/lists/*_Release{,.gpg}
/var/lib/apt/lists/ftp.debian.org_debian_dists_testing_Release
/var/lib/apt/lists/security.debian.org_dists_testing_updates_Release
/var/lib/apt/lists/security.debian.org_dists_testing_updates_Release.gpg
/var/lib/apt/lists/www.debian-multimedia.org_dists_testing_Release
/var/lib/apt/lists/www.debian-multimedia.org_dists_testing_Release.gpg
Thanks. But I don't know..now it doesn't give me that error message.
--
Regards,
Amit.
http://copperskullcprogramming.blogspot.com
--
Unkown Synaptic Message
On Thu, Nov 30, 2006 at 13:04:50 +0530, Amit Joshi wrote:
> On Tuesday 28 November 2006 18:08, Florian Kulzer wrote:
> > On Tue, Nov 28, 2006 at 15:32:20 +0530, Amit Joshi wrote:
[...]
> > > Recently I started getting the errors that the packages are "Unsigned",
> > > so there ain't no problem of the keys not matching here.
> > > Anybody experiencing the same problem?
> > > BTW I am using apt-get :)
> >
> > Which packages are unsigned? What is the output of
>
> Well..it was just a regular update;upgrade procedure, so I don't really
> remember...
>
> >
> > ls /var/lib/apt/lists/*_Release{,.gpg}
> >
> > --
> > Regards,
> > Florian
>
> debian:~# ls /var/lib/apt/lists/*_Release{,.gpg}
> /var/lib/apt/lists/ftp.debian.org_debian_dists_testing_Release
> /var/lib/apt/lists/security.debian.org_dists_testing_updates_Release
> /var/lib/apt/lists/security.debian.org_dists_testing_updates_Release.gpg
> /var/lib/apt/lists/www.debian-multimedia.org_dists_testing_Release
> /var/lib/apt/lists/www.debian-multimedia.org_dists_testing_Release.gpg
The .gpg file for ftp.debian.org_debian_dists_testing_Release is
missing.
> Thanks. But I don't know..now it doesn't give me that error message.
Probably a temporary problem with the server. If you check the
/var/lib/apt/lists/ directory again you should find a *.gpg signature
for every *_Release file.
--
Regards,
Florian
--