On Tue, Nov 07, 2006 at 02:18:36PM +0100, Bastian Blank wrote: > On Tue, Nov 07, 2006 at 12:44:56PM +0000, Matthew Vernon wrote: > > What do you mean? are the files no longer there? not being used? what > > symptoms are you observing? etc. etc. Many other people have upgraded > > sarge->etch without a problem, so please provide as much information > > as you can so we can track the problem down. > > There are two solutions for the conflicts/replaces/depends on > openssh-server in etch: > - Install openssh-server and upgrade ssh, > - install openssh-server and remove ssh. > > My apt decided to use the later and as I use --purge for apt-get, it > first purges the old ssh package which also removes the host keys and > later installes the new openssh-server package.
Don't do that, then. There's no way around this - apt is very likely purging ssh before running any maintainer scripts associated with the new package, so in the absence of a time machine to go back and change the old maintainer scripts there is no possible way to preserve the old configuration if you use --purge during the initial upgrade. Not including the Conflicts caused problems (see http://bugs.debian.org/324695). This is a bit more than just the normal case of moving files between packages, so Replaces alone is unfortunately too weak. debian-doc/debian-release: I suggest noting in the release notes that you should not use --purge options to the package management tools until after completing the initial upgrade pass. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
