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

[TAF] templates://screen/{templates}



The screen package introduced new or modified debconf
templates. This is often a good moment for a review to help the
package maintainer following the general suggested writing style and
track down typos and errors in the use of English language.

A bug report has been sent against the package: 677303

If someone wants to pick up this review, please answer to this mail,
in the mailing list, with an [ITR] (Intent To Review) label.

The templates file is attached.

To propose the file you reviewed for peer review, please send a [RFR]
(Request For Review) mail with the reviewed file attached...then a few
days later, when no more contributions come, a summary mail with a
[LCFC] (Last Chance For Comments) label.

These RFR and LCFC mails should CC the opened bug report.

Finally, after no more comments coming to the LCFC mail, you can send
the reviewed templates file in the bug report.

Then, please notify the list with a last mail using a [BTS] label
with the bug number.

Helping the package maintainer to deal with induced translation
updates at that moment will be nice. If you're not comfortable with
that part of the process, please hand it off to a translator.

-- 


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.
 .
 On this system there seems to be at least one GNU Screen session
 running, possibly the one you run this upgrade in.
 .
 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.

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.
 .
 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.
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 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
 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.

Attachment: signature.asc
Description: Digital signature


Reply to: