Your message dated Sun, 15 Jan 2012 18:49:01 +0000
with message-id
<CAPQ4b8nOLVFxRq=ep9j8tayfkqw7teyew3gpapvcqizxyc6...@mail.gmail.com>
and subject line aptitude bugs #369767 #365283: closing
has caused the Debian Bug report #369767,
regarding aptitude: segfaults when requesting non-existing changelog
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 ow...@bugs.debian.org
immediately.)
--
369767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aptitude
Version: 0.4.1-1
Severity: normal
When requesting a changelog for a non-existing package, aptitude
segfaults.
$ aptitude changelog artsdoisajdfoijsf
Segmentation fault
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.17
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.3-6-3.1 0.6.44.1 Advanced front-end for dpkg
ii libc6 2.3.6-11 GNU C Library: Shared libraries
ii libgcc1 1:4.1.0-4 GCC support library
ii libncursesw5 5.5-2 Shared libraries for terminal hand
ii libsigc++-2.0-0c2a 2.0.16-3 type-safe Signal Framework for C++
ii libstdc++6 4.1.0-4 The GNU Standard C++ Library v3
Versions of packages aptitude recommends:
pn aptitude-doc-en | aptitude-do <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
Sorry for having the bug(s) unattended for so long, there's now an
ongoing effort to bring the list of bugs of aptitude up to date.
This bug does seem to be related to a problem fixed long ago, I cannot
reproduce it and the submitter of one of the bug reports claims to
have been fixed a 4+ years ago in version series 0.4.* already:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=365283
Thus closing the bug report now. Thanks for reporting and tagging
things appropriately later.
Regards.
--- End Message ---
