Your message dated Fri, 6 Jul 2012 16:43:19 +0100
with message-id 
<capq4b8n+5zkqc3qpkrfpwhggxuuc9a5az1kgwy54unk0jq3...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (emacs21 with tag fixed-upstream)
has caused the Debian Bug report #136828,
regarding emacs21: fakemail gets SIGSEGV if run with wrong args.
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 [email protected]
immediately.)


-- 
136828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=136828
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21
Version: 21.1-7
Severity: wishlist

The emacs helper binary segfaults if run with no args and no input.
The only reason I ran it like that is that it has no manpage and I
wondered how it was used.  Ideally, this should have a manpage
referring the user to he Texinfo documentation on fakemail (if any)
and in any case fakemail should emit some kind of failure message
rather than just segfaulting.

However, since nobody needs to just run fakemail, this is a feature
request rather than a bug report. 

Example :-

bash-2.05a$ man fakemail
No manual entry for fakemail
bash-2.05a$ gdb /usr/lib/emacs/21.1/i386-debian-linux-gnu/fakemail  
GNU gdb 5.1.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)...
(gdb) r < /dev/null
Starting program: /usr/lib/emacs/21.1/i386-debian-linux-gnu/fakemail < 
/dev/null(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x08049310 in strcpy ()
(gdb) where
#0  0x08049310 in strcpy ()
#1  0x0000000d in ?? ()
#2  0x080493d2 in strcpy ()
#3  0x400446cf in __libc_start_main () from /lib/libc.so.6
(gdb) c
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) q


-- System Information
Debian Release: 3.0
Kernel Version: Linux periwinkle 2.4.13-k6 #2 Sun Oct 28 12:00:28 EST 2001 i586 
unknown

Versions of the packages emacs21 depends on:
ii  dpkg           1.9.19         Package maintenance system for Debian
ii  emacsen-common 1.4.15         Common facilities for all emacsen.
ii  libc6          2.2.5-3        GNU C Library: Shared libraries and Timezone
ii  libjpeg62      6b-5           The Independent JPEG Group's JPEG runtime li
ii  liblockfile1   1.03           NFS-safe locking library, includes dotlockfi
ii  libncurses5    5.2.20020112a- Shared libraries for terminal handling
ii  libpng2        1.0.12-3       PNG library - runtime
ii  libtiff3g      3.5.5-6        Tag Image File Format library
ii  xaw3dg         1.5-11         Xaw3d widget set
ii  xlibs          4.1.0-14       X Window System client libraries
ii  zlib1g         1.1.3-19       compression library - runtime


--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved or closed in due time.

emacs21 packages have been removed from testing in 2009 [1], not
present even in the current stable.  Consequently, these bugs are now
orphan (without maintainer assigned) so they probably will not be
attended/noticed further.

[1] http://packages.qa.debian.org/e/emacs21.html

The bugs deemed valid are going to be verified and reassigned, but the
current bugs that I'm closing now are very ancient (more than 10 years
sometimes) and marked as fixed-upstream years ago, with no recent
input, and are supposed to be fixed in emacs22 at the latest.

Please comment if you want think that some of the raised questions are
still pending and need to be addressed differently (e.g., reassigned
to other packages, etc.).

Cheers.


--- End Message ---

Reply via email to