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

Bug#649240: marked as done (Upcoming upgrade issues with GNU Screen for Wheezy)

Your message dated Sat, 6 Apr 2013 02:59:10 +0200
with message-id <20130406005910.GZ16254@beskar.mdcc.cx>
and subject line Re: Bug#649240: release-notes: Upcoming upgrade issues with GNU Screen for Wheezy
has caused the Debian Bug report #649240,
regarding Upcoming upgrade issues with GNU Screen for Wheezy
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
649240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649240
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Tags: wheezy

On Sat, Nov 19, 2011 at 04:03:30 +0100, Axel Beckert wrote:

> Hi Release-Team,
> 
> I wanted to make you aware of an issue with screen which will very
> likely be present when dist-upgrading from Squeeze to Wheezy inside a
> Screen session:
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644788
> 
> If upstream doesn't add some option to let a screen 4.1.0 client
> communicate with a screen 4.0.3 server, it won't be possible to
> reattach to a running 4.0.3 screen session if screen has been upgraded
> to 4.1.0 already.
> 
> I still have some hope, but if there's really no chance, this is IMHO
> definitely something which should go into the release notes.
> 
> Possible suggestions for the release notes: Use tmux instead of screen
> for the dist-upgrade. Not really a laudable note for screen, but I
> have currently no better idea.
> 
> And even if upstream adds some backward compatibility command-line
> option, this option should be mentioned in the Release Notes anyway
> 
> Anyway, I'll let you know when I uploaded a screen 4.1.0 package to
> unstable and which options we have then.
>

--- End Message ---
--- Begin Message --- 
applied:

Envoi          en/upgrading.dbk
Transmission des données .
Révision 9697 propagée.

Thanks Axel!

Bye,

Joost



On Wed, Mar 20, 2013 at 11:53:06PM +0100, Axel Beckert wrote:
> Control: tag -1 +patch
> 
> Hi,
> 
> Joost van Baal-Ilić wrote:
> > For the record: Julien Cristau's patch is incorporated in screen in wheezy.
> > Axel told me "thanks for the reminder" when I told him about this bugreport.
> > He'll likely work on the release notes.
> 
> Here's a patch against revision 9641 of the release notes which covers
> screen's upgrade issues:
> 
> Index: upgrading.dbk
> ===================================================================
> --- upgrading.dbk       (revision 9641)
> +++ upgrading.dbk       (working copy)
> @@ -1281,7 +1281,41 @@
>  hand.
>  </para>
>  </section>
> +<section id="issues-screen">
> +<title>Screen</title>
> +<para>
> +The GNU Screen versions in Squeeze and Wheezy don't use the same
> +communication protocol between the <command>screen</command> client
> +and the <command>SCREEN</command> server. Wheezy's <systemitem
> +role="package">screen</systemitem> package has been patched so that
> +the most important functionality is present even if the versions of
> +<command>screen</command> client and server don't match.
> +</para>
> +<para>
> +The most prominent functionality which does not work properly when
> +connecting to a Screen session started with Squeeze's version of
> +<systemitem role="package">screen</systemitem> with Wheezy's version
> +of <systemitem role="package">screen</systemitem> as client is
> +terminal resizing (<literal>WINCH</literal> signal). The workaround is
> +to detach and reattach again to get the size of the terminals inside
> +the screen session adjusted propely.
> +</para>
> +<para>
> +Another (harmless) symptom of such an inter-version connection is
> +<command>screen</command> issuing messages like "Message 40 of 12376
> +bytes too small".
> +</para>
> +<para>
> +All those issues vanish as soon as the Screen sessions started with
> +Squeeze's version of <systemitem role="package">screen</systemitem>
> +exited.
> +</para>
> +<para>
> +See also <filename>/usr/share/doc/screen/NEWS.Debian.gz</filename> of
> +Wheezy's <systemitem role="package">screen</systemitem> package.
> +</para>
>  </section>
> +</section>
>  <!-- End of 'trouble' section -->
>  </section>
>  
> 
> HTH.
> 
> 		Regards, Axel
> -- 
>  ,''`.  |  Axel Beckert <abe@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-doc-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/20130320225305.GH28221@sym.noone.org
>

--- End Message ---
Reply to: