Re: stable-->testing report
On Wed, Aug 15, 2001 at 03:05:52PM +0200, Gerhard Kroder wrote:
> Colin Watson wrote:
> > Some are packages removed/renamed since stable:
> >
> > * freetype2-dev -> libttf-dev
> > * librpm1 -> librpm0
> > * libwmf0-dev -> libwmf-dev
> > * netscape4 -> netscape-*-477
> > * pnmtopng -> netpbm
> > * tetex-lib -> libkpathsea3
> > * tetex-nonfree
> > * xcontrib -> xbase-clients
> > * xlib6g-dev -> xlibs-dev
> > * xpm4g -> xlibs
> > * xpm4g-dev -> xlibs-dev
>
> there should be a way to observe and resolve this changes somewhat more
> semi-automatically when doing a dist-upgrade.
How about dselect? It'll mention removed packages under
"Obsolete/Local", and tell you the reasons why each package is to be
removed if you ask it.
In this case, though, dist-upgrade seems to have done more or less the
right thing anyway.
> -Is there any work in progress to do some recursivas during upgrade?
Hmm?
> -Can the inconvenience with renamed packages be reduced by using pseudo
> packages with the old name, with depencies on the new one? When an old
> programm/packages to remove comes with a bunch of others in a new
> package, then at least ther should be an default sugesstion set where
> you do not loose functionality after upgrade.
That's sometimes done, although it's not always sensible, e.g. when
library versions change. Conflicts:, Replaces:, and Provides: are more
usual, and should do fine.
> -When packages do no longer belong to distro, there should be a more
> informative message for packaged getting removed during dist-upgrade. Of
> course this could be written to an README.upgrage or such.
When that happens from release to release, there's often a mention in
the release notes. Otherwise, use dselect, or if apt frontends tell you
about removed packages try one of those.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: