gpg: failed to create temporary file '/var/lib/lurker/.#lk0x57392100.hantslug.org.uk.5977': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Wed Oct 7 11:30:02 2009 BST
gpg: using DSA key 20ACB3BE515C238D
gpg: Can't check signature: No public key
On Tue, Oct 06, 2009 at 11:45:41PM +0100, Vic wrote:
> > aptitude (safe-)upgrade
>
> I'm still trying to work out exactly what safe-upgrade actually does.
>
> The page I found describing it says :-
>
> "The new action will upgrade a package only if it does not impact other
> packages, i-e: if it is necessary to add or remove a dependency package
> during upgrade, safe-upgrade won't upgrade."
>
> This seems to say that, although dependencies are checked, they won't be
> actioned in any way. That kinda obviates the usefulness of apt(itude),
> doesn't it?
It follows on from the package update policy for Debian stable,
which is that bug-fixes for packages are always back-ported to the
original pacakge version. Thus, over the lifetime of a stable release,
the "upstream" part of the package version will never change (although
the debian patch version will). This implies that no security upgrade
will ever attempt to install new packages. The safe-upgrade option
matches this policy, and won't ever try to install new packages
automatically as a result of the upgrade.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- In the future, terrorists won't be carrying their ID cards. ---
They'll be carrying yours. -- Henry
Porter, Suspect Nation
