Re: Sarge -> Etch upgrade issue
On Fri, Sep 15, 2006 at 08:32:13AM +0200, Martin Schulze wrote:
> Alexander Schmehl wrote:
> > * Steve Langasek <email@example.com> [060908 01:46]:
> > > > 1) sarge:
> > > > 1.1) apt-get dist-upgrade -> upgrading to etch
> > [..]
> > > Yes, I can see that apt Recommends: debian-archive-keyring and Suggests:
> > > gnupg. Given that apt should be doing secure archives by default now, the
> > > Suggests: seems like the wrong relationship; I think this warrants a bug on
> > > apt, no?
> > Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK
> > the Release Notes recommend using aptitude instead of apt-get. And
> > aptitude respects recommends should pull in debian-archive-keyring,
> > which depends on gnupg.
> The release notes for sarge recommended aptitude over apt-get due
> to some strange problems with apt-get alone. Will this still be
> the case for etch or rather the sarge -> etch upgrade?
Since apt-get doesn't handle Recommends, I expect that this will be the case
for etch as well. I'm not thrilled with some of the other behavior changes
in aptitude's resolver post-sarge, but I'm not sure they're actually worse
than some of apt-get's own idiosyncracies.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.