Re: Package splitting and upgrades
On Fri, 01 Mar 2002, Josip Rodin wrote:
> On Fri, Mar 01, 2002 at 11:08:02AM +0000, Andrew Suffield wrote:
> > Further note that people using apt-get do not care about complex
> > package interrelations and are willing to fix things by hand, tracking
> > down individual packages that they need and installing them. (That is
> > what it means to use the back-end tools manually). Ditto for dpkg
> > -iGROEB users.
> Actually, we have so far recommended _everyone_ to use apt-get dist-upgrade
> for cross-release upgrades, not just the advanced users, i.e. those who
> don't mind getting their hands dirty. (Note that I was the release notes
> maintainer for slink->potato.)
We did so in error. It is time to write that down in the release notes.
"apt-get" is NOT to be used like this, and its maintainer has told us so a
number of times (and refused to change the tool so that it could deal with
recommends and suggests sanely, because that is not in the charter for
Real life has teached me that:
1. You want to upgrade dpkg and apt first, unless the release notes tells
you something else.
2. You want to upgrade debconf and make sure perl and glibc are ok after you
upgraded dpkg and apt. Only then you may dist-upgrade the rest of the
3. You must use dselect or aptitude or some other frontend to fix the
borkages using only apt-get will cause, from time to time (I use dselect
> You get shit for recommending apt-get, and you get shit for recommending
apt-get simply will not cut it BY DESIGN. I dislike this (I wish it would, I
like command-line tools), but such is life.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot