Re: Bug#677303: [RFR] templates://screen/{templates}
Axel Beckert wrote:
>>> -_Description: Previous screen binary has been copied to /tmp/screen-4.0.3
>>> +_Description: Warning: upgrading screen with an active session
>
> I dislike this version as it reads as this is something which is
> generally the case (which it is not). I though like the idea of the
> word "Warning" in it.
>
> My suggestion: "Warning: upgrading to screen 4.1.0 with an active 4.0.3 session"
Good if it'll fit; if not we might need to fall back on
_Description: Warning - upgrading screen to an incompatible version
(No, forget that, yours fits.)
[...]
>> Drop "currently", unless we really expect stable-update versions of
>> Screen 4.1.0 to be backward-compatible.
>
> That's what I expect, yes, and for what I hoped will happen before the
> freeze so I don't have to bother with debconf based workarounds like
> this.
Okay, putting "currently" back in the attached version.
[...]
>> (Last minute thought: does the second error message ever appear
>> without being preceded by the first one?)
>
> Shouldn't. Both, config and preinst have the following code snippet:
>
> if cp -pnT /usr/bin/screen /tmp/screen-4.0.3 ; then
> echo Copied /usr/bin/screen to /tmp/screen-4.0.3
> db_input high screen/410-upgrade || true
> db_go || true
> else
> echo Copying /usr/bin/screen to /tmp/screen-4.0.3 failed
> db_input high screen/403-copy-failed || true
> db_go || true
> fi
(Right, so users should only ever see one or the other, which means
both templates do need to explain what's going on.)
> But another thought: I posted a workaround for the worst case (dpkg
> stuck inside unreachable screen, i.e. you can't run dpkg -i
> screen_4.0.3*deb outside the screen and you don't want to kill it) at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677227#5 -- would it
> make sense to include this URL somehow? Or the workaround itself?
It would make sense to point at a NEWS file with details and/or
pointers; debconf reviews often involve telling maintainers to move as
much as possible into separate docs, but then again I can see how
admins might prefer not to have to try to establish a new session just
to read the README about problems establishing new sessions.
Of course, they'll all have read the Release Notes, right?
[...]
>>> single physical character-based terminal. Each virtual terminal emulates a
>>> DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
>>> can be detached and resumed later on a different terminal.
>>
>> (While I'm here I'm imposing d-l-e "house style" single-spacing.)
>
> I thought double spacing is common for English (but not for German AFAIK).
It's largely an en_US versus en_GB thing (my own habitual en_GB
involves double-spacing), but double spaces get squashed to single
spaces anyway as soon as the description gets re-flowed.
>>> configurable input and output translation, serial port support, configurable
>>> logging, multi-user support, and utf8 charset support.
>>
>> Failing to support UTF-8 by default has been a bug since at least
>> Lenny, so drop that one.
>
> Huh? Works fine for me, I do write all my private mails inside Screen
> including German with umlauts. Just wide-character support (e.g.
> Japanese and Chinese) seems to be incomplete. Or do you mean automatic
> character set detection? (And no, I don't know all screen bug reports
> by mind. :-)
As far as I know screen's UTF-8 support is flawless (჻☽); and it's
also FHS-compliant, Y2k-safe, and libc6-compatible, but these non-bugs
no longer really count as features.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru screen-4.1.0~20120320gitdb59704.pristine/debian/control screen-4.1.0~20120320gitdb59704/debian/control
--- screen-4.1.0~20120320gitdb59704.pristine/debian/control 2012-06-10 03:44:04.000000000 +0100
+++ screen-4.1.0~20120320gitdb59704/debian/control 2012-06-13 19:26:28.411392204 +0100
@@ -14,12 +14,12 @@
Pre-Depends: debconf
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: iselect (>= 1.4.0-1) | screenie | byobu
-Description: terminal multiplexor with VT100/ANSI terminal emulation
- screen is a terminal multiplexor that runs several separate "screens" on a
- single physical character-based terminal. Each virtual terminal emulates a
- DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
+Description: terminal multiplexer with VT100/ANSI terminal emulation
+ GNU Screen is a terminal multiplexer that runs several separate "screens" on
+ a single physical character-based terminal. Each virtual terminal emulates a
+ DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
can be detached and resumed later on a different terminal.
.
- Screen also supports a whole slew of other features. Some of these are:
- configurable input and output translation, serial port support, configurable
- logging, multi-user support, and utf8 charset support.
+ Screen also supports a whole slew of other features, including configurable
+ input and output translation, serial port support, configurable logging,
+ and multi-user support.
diff -ru screen-4.1.0~20120320gitdb59704.pristine/debian/templates screen-4.1.0~20120320gitdb59704/debian/templates
--- screen-4.1.0~20120320gitdb59704.pristine/debian/templates 2012-06-10 15:38:02.000000000 +0100
+++ screen-4.1.0~20120320gitdb59704/debian/templates 2012-06-13 21:08:04.587392302 +0100
@@ -1,35 +1,26 @@
Template: screen/410-upgrade
Type: error
-_Description: Previous screen binary has been copied to /tmp/screen-4.0.3
- GNU Screen 4.1.0 currently can't speak with GNU Screen sessions
- started by GNU Screen 4.0.3.
+_Description: Warning: upgrading to screen 4.1.0 with an active 4.0.3 session
+ There seems to be at least one GNU Screen session running on this system;
+ possibly the one you are running this upgrade in. However, GNU Screen 4.1.0
+ currently can't communicate with sessions started by Screen 4.0.3.
.
- On this system there seems to be at least one GNU Screen session
- running, possibly the one you run this upgrade in.
+ To reconnect to a running GNU Screen session after the new version has been
+ unpacked, you'll need to call the old screen binary instead of the new one,
+ so a copy has been made which can be invoked as "/tmp/screen-4.0.3 -rd".
.
- To be able to reconnect to your running GNU Screen session after the
- new screen package has been unpacked, you'll need to call the old
- screen binary instead of the new one. For that purpose, the old
- screen binary has been copied to /tmp/screen-4.0.3. You can call it
- like this: "/tmp/screen-4.0.3 -rd"
- .
- In case your /tmp/ is a separate mount point and mounted with the
- nosuid or noexec options, you may need to copy it to some other place
- beforehand, e.g. to /root/, before calling it. It's permissions
- should be 2755 (-rwxr-sr-x) and it should belong to the user root and
- group utmp.
+ If your /tmp/ is a separate mount point mounted with the nosuid or noexec
+ options, you may need to copy it to somewhere else (such as /root) before
+ calling it. Its permissions should be 2755 (-rwxr-sr-x) and it should belong
+ to the user root and group utmp.
Template: screen/403-copy-failed
Type: error
-_Description: Copying current screen binary to /tmp/screen-4.0.3 failed.
- GNU Screen 4.1.0 currently can't speak with GNU Screen sessions
- started by GNU Screen 4.0.3.
- .
- On this system there seems to be at least one GNU Screen session
- running, possibly the one you run this upgrade in.
+_Description: Failed copy of screen binary to /tmp/screen-4.0.3
+ There seems to be at least one GNU Screen session running on this system;
+ possibly the one you are running this upgrade in. However, GNU Screen 4.1.0
+ currently can't communicate with sessions started by Screen 4.0.3.
.
- To be able to reconnect to your running GNU Screen session after the
- new screen package has been unpacked, you'll need to call the old
- screen binary instead of the new one. For that purpose, it has been
- tried to copy the old screen binary to /tmp/screen-4.0.3, but
- unfortunately this failed.
+ To reconnect to a running GNU Screen session after the new version has been
+ unpacked, you'll need to call the old screen binary instead of the new one.
+ However, the attempt to copy it to /tmp/screen-4.0.3 has failed.
Source: screen
Section: misc
Priority: optional
Maintainer: Axel Beckert <abe@debian.org>
Uploaders: Jan Christoph Nordholz <hesso@pool.math.tu-berlin.de>
Standards-Version: 3.9.3
Build-Depends: libncursesw5-dev, texinfo, libpam0g-dev, debhelper (>> 7), dh-autoreconf, dpkg-dev (>= 1.16.1~)
Homepage: http://savannah.gnu.org/projects/screen
Vcs-Git: git://anonscm.debian.org/collab-maint/screen.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/screen.git
Package: screen
Architecture: any
Pre-Depends: debconf
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: iselect (>= 1.4.0-1) | screenie | byobu
Description: terminal multiplexer with VT100/ANSI terminal emulation
GNU Screen is a terminal multiplexer that runs several separate "screens" on
a single physical character-based terminal. Each virtual terminal emulates a
DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
can be detached and resumed later on a different terminal.
.
Screen also supports a whole slew of other features, including configurable
input and output translation, serial port support, configurable logging,
and multi-user support.
diff -ru screen-4.1.0~20120320gitdb59704.pristine/debian/control screen-4.1.0~20120320gitdb59704/debian/control
--- screen-4.1.0~20120320gitdb59704.pristine/debian/control 2012-06-10 03:44:04.000000000 +0100
+++ screen-4.1.0~20120320gitdb59704/debian/control 2012-06-13 19:26:28.411392204 +0100
@@ -14,12 +14,12 @@
Pre-Depends: debconf
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: iselect (>= 1.4.0-1) | screenie | byobu
-Description: terminal multiplexor with VT100/ANSI terminal emulation
- screen is a terminal multiplexor that runs several separate "screens" on a
- single physical character-based terminal. Each virtual terminal emulates a
- DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
+Description: terminal multiplexer with VT100/ANSI terminal emulation
+ GNU Screen is a terminal multiplexer that runs several separate "screens" on
+ a single physical character-based terminal. Each virtual terminal emulates a
+ DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
can be detached and resumed later on a different terminal.
.
- Screen also supports a whole slew of other features. Some of these are:
- configurable input and output translation, serial port support, configurable
- logging, multi-user support, and utf8 charset support.
+ Screen also supports a whole slew of other features, including configurable
+ input and output translation, serial port support, configurable logging,
+ and multi-user support.
diff -ru screen-4.1.0~20120320gitdb59704.pristine/debian/templates screen-4.1.0~20120320gitdb59704/debian/templates
--- screen-4.1.0~20120320gitdb59704.pristine/debian/templates 2012-06-10 15:38:02.000000000 +0100
+++ screen-4.1.0~20120320gitdb59704/debian/templates 2012-06-13 21:08:04.587392302 +0100
@@ -1,35 +1,26 @@
Template: screen/410-upgrade
Type: error
-_Description: Previous screen binary has been copied to /tmp/screen-4.0.3
- GNU Screen 4.1.0 currently can't speak with GNU Screen sessions
- started by GNU Screen 4.0.3.
+_Description: Warning: upgrading to screen 4.1.0 with an active 4.0.3 session
+ There seems to be at least one GNU Screen session running on this system;
+ possibly the one you are running this upgrade in. However, GNU Screen 4.1.0
+ currently can't communicate with sessions started by Screen 4.0.3.
.
- On this system there seems to be at least one GNU Screen session
- running, possibly the one you run this upgrade in.
+ To reconnect to a running GNU Screen session after the new version has been
+ unpacked, you'll need to call the old screen binary instead of the new one,
+ so a copy has been made which can be invoked as "/tmp/screen-4.0.3 -rd".
.
- To be able to reconnect to your running GNU Screen session after the
- new screen package has been unpacked, you'll need to call the old
- screen binary instead of the new one. For that purpose, the old
- screen binary has been copied to /tmp/screen-4.0.3. You can call it
- like this: "/tmp/screen-4.0.3 -rd"
- .
- In case your /tmp/ is a separate mount point and mounted with the
- nosuid or noexec options, you may need to copy it to some other place
- beforehand, e.g. to /root/, before calling it. It's permissions
- should be 2755 (-rwxr-sr-x) and it should belong to the user root and
- group utmp.
+ If your /tmp/ is a separate mount point mounted with the nosuid or noexec
+ options, you may need to copy it to somewhere else (such as /root) before
+ calling it. Its permissions should be 2755 (-rwxr-sr-x) and it should belong
+ to the user root and group utmp.
Template: screen/403-copy-failed
Type: error
-_Description: Copying current screen binary to /tmp/screen-4.0.3 failed.
- GNU Screen 4.1.0 currently can't speak with GNU Screen sessions
- started by GNU Screen 4.0.3.
- .
- On this system there seems to be at least one GNU Screen session
- running, possibly the one you run this upgrade in.
+_Description: Failed copy of screen binary to /tmp/screen-4.0.3
+ There seems to be at least one GNU Screen session running on this system;
+ possibly the one you are running this upgrade in. However, GNU Screen 4.1.0
+ currently can't communicate with sessions started by Screen 4.0.3.
.
- To be able to reconnect to your running GNU Screen session after the
- new screen package has been unpacked, you'll need to call the old
- screen binary instead of the new one. For that purpose, it has been
- tried to copy the old screen binary to /tmp/screen-4.0.3, but
- unfortunately this failed.
+ To reconnect to a running GNU Screen session after the new version has been
+ unpacked, you'll need to call the old screen binary instead of the new one.
+ However, the attempt to copy it to /tmp/screen-4.0.3 has failed.
Reply to: