Hi,
Karl Goetz wrote:
> > > > 2) Make screen 4.0.3 and screen 4.1.0 installable at the same
> > > > time, i.e. give them different source and binary package names.
> > > This would require a great amount of work
> >
> > I fear so, yes.
> >
> > > to fix a tiny problem which presents itself just for the length of
> > > the upgrade process, if at all.
> >
> > Correct. It's an option nevertheless, so I mentioned it.
>
> Sorry if I've misunderstood, but doesn't this problem manifest for
> *anyone* trying to ssh from a wheezy system to a squeeze system?
I'm not sure which problem you exactly think of.
If you do a dist-upgrade via ssh and loose the connection, your
running apt-get or aptitude will loose its tty (unless running inside
screen or tmux of course) and usually exits unsuccessfully. After you
reconnected via ssh you usually have to run dpkg --configure --pending
first to clean up the mess and then continue with the dist-upgrade.
But in nearly every case this is recoverable remotely -- except if the
new openssh-server version itself was somewhere after being unpacked
but not yet configured. Then you may get something like
"ssh_exchange_identification: Connection closed by remote host".
(Happend to me once so far when I tried to continue a dist-upgrade
inside screen remotely from some other host. Luckily the ssh
connection from the host where I started the dist-upgrade still was
there.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120102132433.gp20...@sym.noone.org
