Re: Slink -> Potato upgrade report
Hamish Moffatt wrote:
> On Sat, Feb 26, 2000 at 12:28:45PM +1100, Martijn van Oosterhout wrote:
> > It's because the packages changed names from slink to potato.
> > fvwm => fvwm1
> > fvwm2 => fvwm
> > I've just noticed the last apt-get upgrade trashed my fvwm config
> > without
> > leaning a backup. *sigh*. I'll try to track this down.
> I don't really understand why fvwm is such a special case -- for most
> programs, the next version is an upgrade of the package, not a separate
> package. Yes you got auto-upgraded to fvwm 2, but you want to be
> upgraded to the latest dpkg and libc6 right, so why not fvwm?
fvwm2 was in slink already and I didn't like it then. It looks
sufficiently different to fvwm1 that I don't want it.
Maybe I'm wierd, but I consider fvwm1 and fvwm2 to be completely
different programs and thus auto-upgrading is the wrong thing.
By installing fvwm1 again myself, everything works again.
Martijn van Oosterhout <email@example.com>
Trust the computer industry to shorten "Year 2000" to Y2K.
It was this kind of thinking that caused the problem in the first place.