Your message dated Thu, 19 Apr 2007 22:02:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311919: fixed in apt-listchanges 2.73.2
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: apt-get
Version: 0.5.4
Severity: minor
(Notice: it could also be apt-listchanges 2.18, that depends on where
you guys decide to fix the issue.)
I'm using a script in /etc/cron.daily that says
#! /bin/sh
apt-get -qq update && apt-get -qq -y upgrade
to automatically install updates (security patches in particular).
apt-get is configured to send reports to [EMAIL PROTECTED], and I get these
reports just fine.
However, whenever 'apt-get -qq -y upgrade' actually finds something to
upgrade, it invokes 'apt-listchanges', which in turn tries to access
/dev/tty (probably to output a confirmation message). This makes for
nasty-looking error messages at the end of the report, and makes me
moderately concerned that the upgrades are really installed correctly.
(Actually the messages are triggered by a missing /dev/tty. I know
that's a nonstandard setup, but it does give me a handle on those
programs that try to do console I/O despite living on a machine that
doesn't have a console - it's a root server that can be accessed through
ssh exclusively.)
It seems that 'apt-get -y' should call apt-listchanges in a way that
apt-listchanges doesn't ask for confirmation (probably via using
different command-line options, either by leaving out -c, or by adding
-y and extending apt-listchanges to accept a -y flag).
Background information:
Here's the content of one of the more recent mail reports I got from
apt-get (the part that looks unusual to me is in the last paragraph,
between and including the lines starting with "Traceback" and "IOError"):
--- snip ---
/etc/cron.daily/debian-update:
Reading changelogs...
mailutils (20020409-1woody2) stable-security; urgency=high
* Non-maintainer upload by the Security Team
* Second try
* Applied upstream patch to fix buffer overflow [mailbox/header.c,
CAN-2005-1520]
* Applied upstream patch to fix heap overflow [imap4d/fetch.c,
imap4d/util.c, CAN-2005-1521]
* Applied upstream patch to fix denial of service [imap4d/fetch.c,
CAN-2005-1522]
* Applied upstream patch to fix format string vulnerability
[imap4d/util.c, CAN-2005-1523]
-- Martin Schulze <[EMAIL PROTECTED]> Fri, 27 May 2005 08:09:39 +0200
mailutils (20020409-1woody1) unstable; urgency=low
* Non-maintainer upload by the Security Team
* Applied upstream patch to fix buffer overflow [mailbox/header.c,
CAN-2005-1520]
* Applied upstream patch to fix heap overflow [imap4d/fetch.c,
CAN-2005-1521]
* Applied upstream patch to fix denial of service [imap4d/fetch.c,
CAN-2005-1522]
* Applied upstream patch to fix format string vulnerability
[imap4d/util.c, CAN-2005-1523]
-- Martin Schulze <[EMAIL PROTECTED]> Thu, 26 May 2005 20:13:19 +0200
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 162, in ?
if not frontend.confirm():
File "/usr/lib/site-python/apt_listchanges.py", line 268, in confirm
tty = open('/dev/tty', 'r+')
IOError: [Errno 6] No such device or address: '/dev/tty'
(Reading database ... 20385 files and directories currently installed.)
Preparing to replace libmailutils0 20020409-1 (using
.../libmailutils0_20020409-1woody2_i386.deb) ...
Unpacking replacement libmailutils0 ...
Setting up libmailutils0 (20020409-1woody2) ...
--- snip ---
Regards,
Jo
--- End Message ---
--- Begin Message ---
Source: apt-listchanges
Source-Version: 2.73.2
We believe that the bug you reported is fixed in the latest version of
apt-listchanges, which is due to be installed in the Debian FTP archive:
apt-listchanges_2.73.2.dsc
to pool/main/a/apt-listchanges/apt-listchanges_2.73.2.dsc
apt-listchanges_2.73.2.tar.gz
to pool/main/a/apt-listchanges/apt-listchanges_2.73.2.tar.gz
apt-listchanges_2.73.2_all.deb
to pool/main/a/apt-listchanges/apt-listchanges_2.73.2_all.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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre Habouzit <[EMAIL PROTECTED]> (supplier of updated apt-listchanges
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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 19 Apr 2007 23:42:19 +0200
Source: apt-listchanges
Binary: apt-listchanges
Architecture: source all
Version: 2.73.2
Distribution: unstable
Urgency: low
Maintainer: Pierre Habouzit <[EMAIL PROTECTED]>
Changed-By: Pierre Habouzit <[EMAIL PROTECTED]>
Description:
apt-listchanges - Display change history from .deb archives
Closes: 311919
Changes:
apt-listchanges (2.73.2) unstable; urgency=low
.
* Only open /dev/tty if present (Closes: 311919), properly this time.
Files:
1be9d1d4934223116bfa8abe090af345 656 utils optional apt-listchanges_2.73.2.dsc
06b692daae0c651b9ae9fce86dcead69 930256 utils optional
apt-listchanges_2.73.2.tar.gz
4bad292f3def9baddbe7eba302cc6290 66190 utils optional
apt-listchanges_2.73.2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGJ+JyvGr7W6HudhwRAk0+AJ9ztkJLzWFXsCDZ2g8c0y37ZX6zpACdHmm2
OUFQwoHSnquewy6DVBtkALI=
=JDig
-----END PGP SIGNATURE-----
--- End Message ---
