[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Slink -> Potato upgrade report

Hi, I just upgraded from slink to potato. Though I'm
upgrading off CD and thus a bit behind, there are some
issues that I think are still true and need to be addressed.

1. When I upgraded, fvwm1 got automatically replaced with 
fvwm2. If I wanted fvwm2 I would have installed it myself.
Not just that, but it came up with a message about that
fvwm was using the menu system now and that it had moved
my old config and replaced it and I had to merge my changes

I think this is the wrong way round. It should have kept
my settings by default and I should merge the menu stuff
in myself if I want it.

2. At one stage, apt died half way through because a bug
caused it to misinterpret the Pre-Invoke and Post-Invoke 
options wrong, this leaving my system in a very interesting
half installed stage. I guess this is a message that one
should should upgrade apt before doing a dist-upgrade.

3. When bind upgraded it said the config file had moved to
a new location but it didn't copy any of the config over.
Again, why not just move the old config to the new location
and run with it?

4. The bug upgrading dnsutils bit me and really screwed the

5. The new modutils wants all modules to be owned by root. I
know why this is but is there a way to make it work? I always
install my modules as my normal user.

6. Got many of these. Dunno if they're important.
dhelp_parse: Warning - documents in /usr/doc are no longer supported!

7. I'm against the system time being written to the hardware clock
on shutdown, on the basis that my hardware clock is far more 
accurate than my system clock anyway.

I'm still scanning the logs of the upgrade. 99% of the system
worked fine but there were a few glitches.
Martijn van Oosterhout <kleptog@cupid.suninternet.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.

Reply to: