[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#400935: marked as done (upgrade-reports: Woody -> Sarge upgrade installs debian-archive-keyring before upgrading apt)

Your message dated Mon, 11 Dec 2006 20:36:41 -0500
with message-id <20061212013641.GA10941@nathanst.com>
and subject line upgrade-reports: Woody -> Sarge upgrade installs debian-archive-keyring before upgrading apt
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: upgrade-reports
Severity: normal

When I followed the instructions in the Sarge -> Etch release notes and run
"aptitude upgrade aptitude", that operation also brings in the causes the
"apt" package to be updated as well as installing the new
"debian-archive-keyring" package.

However, at least in my case, it installed the keyring package before
performing the upgrade on apt... and thus /usr/bin/apt-key didn't exist when
the debian-archive-keyring postinst script was run and the new archive keys
were not installed into the apt-key trusted key list.  This in turn meant
that I got a 
  W: There are no public key available for the following key IDs: A70DAF536070D3A1
message  every time I ran an "aptitute update" afterwards.

(Once I figured what happened I was able to fix the problem just by running
"apt-key update" manually.)

I assume that there is some good reason the debian-archive-keyring package
does not already have a dependency on a version of apt that contains
apt-key, and I'm not sure if there is some other way to get aptitude to
automatically perform the update/install operations in the correct order. 
If not, it seems like the issue should at least be mentioned in the release
notes (probably right there in section 4.4.2 "Upgrading aptitude").

Thanks.

						Nathan

--- End Message ---
--- Begin Message --- 
As a fix for bug #401114, the postinst script for apt (0.6.46.3-0.1) was
modified to include a call to "apt-key upgrade" too (in addition to the
one found in the "debian-archive-keyring" postinst script).

That should fix the problem I noticed during Sarge -> Etch upgrades.

						Nathan

--- End Message ---
Reply to: