Bug#400401: marked as done (xterm upgrade: error in control file: `Format' value not specified at /usr/sbin/install-docs line 699, </usr/share/doc-bae/xterm-faq> line 22.)
Your message dated Sun, 26 Nov 2006 11:48:18 +0000
with message-id <E1GoIUc-0002LX-E9@ries.debian.org>
and subject line Bug#400375: fixed in xterm 222-3
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: xterm
Version: 222-2
When I upgraded xterm using aptitude, I recieved these error messages:
-------------------------------------------------------------------------------
Setting up mozilla-livehttpheaders (0.13.1-2) ...
Setting up mozilla-tabextensions (2.1.2006031301-2) ...
Setting up xserver-xorg-core (1.1.1-11) ...
Setting up xterm (222-2) ...
Installing new version of config file /etc/X11/app-defaults/KOI8RXTerm ...
error in control file: `Format' value not specified at /usr/sbin/install-docs li
ne 699, </usr/share/doc-base/xterm-faq> line 22.
dpkg: error processing xterm (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
xterm
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up xterm (222-2) ...
error in control file: `Format' value not specified at /usr/sbin/install-docs li
ne 699, </usr/share/doc-base/xterm-faq> line 22.
dpkg: error processing xterm (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
xterm
Press return to continue.
-------------------------------------------------------------------------------
(FWIW, this came from:
# dd if=/dev/vcs2 of=/tmp/vcs2 conv=unblock ibs=80 cbs=80)
Xterm seems to be itself working properly.
--- End Message ---
--- Begin Message ---
Source: xterm
Source-Version: 222-3
We believe that the bug you reported is fixed in the latest version of
xterm, which is due to be installed in the Debian FTP archive:
xterm_222-3.diff.gz
to pool/main/x/xterm/xterm_222-3.diff.gz
xterm_222-3.dsc
to pool/main/x/xterm/xterm_222-3.dsc
xterm_222-3_i386.deb
to pool/main/x/xterm/xterm_222-3_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 400375@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Nusinow <dnusinow@debian.org> (supplier of updated xterm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 25 Nov 2006 18:37:22 -0500
Source: xterm
Binary: xterm
Architecture: source i386
Version: 222-3
Distribution: unstable
Urgency: low
Maintainer: David Nusinow <dnusinow@debian.org>
Changed-By: David Nusinow <dnusinow@debian.org>
Description:
xterm - X terminal emulator
Closes: 400375
Changes:
xterm (222-3) unstable; urgency=low
.
[ Julien Cristau ]
* Split xterm.doc-base in xterm.doc-base.faq and xterm.doc-base.ctlseqs, to
make the package installable again, thanks to Ryan Murray
(closes: #400375).
Files:
27120d4155859cc19c5858318dcf4b64 813 x11 optional xterm_222-3.dsc
2e7e45264bdd32752531d37b7e3d3341 61407 x11 optional xterm_222-3.diff.gz
01bef6889a6b2584359a01da17c74d0c 438388 x11 optional xterm_222-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFaNn4yLfpNdY0ad8RAt1RAJ4uOrt9L76Q2YXPeYsdfvISdB07xwCdEnlf
74rlTuC/uc/G9v94EYFyvWw=
=BhuZ
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: