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

Bug#397439: marked as done (openssh-server - upgrade from ssh in sarge kills host keys)

Your message dated Wed, 6 Dec 2006 05:23:04 +0000
with message-id <20061206052303.GY28442@riva.ucam.org>
and subject line Bug#397439: openssh-server - upgrade from ssh in sarge kills host keys
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: openssh-server
Version: 1:4.3p2-5
Severity: critical

An upgrade from ssh in sarge to openssh-server kills the old host keys.


Is truth not truth for all?
		-- Natira, "For the World is Hollow and I have Touched
		   the Sky", stardate 5476.4.

--- End Message ---
--- Begin Message ---
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.


Colin Watson                                       [cjwatson@debian.org]

--- End Message ---

Reply to: