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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]