Your message dated Fri, 4 May 2012 23:15:36 +0100
with message-id
<CAPQ4b8=7PU12EnbGNScPOYOfcA74FiTcA65=uHWYa=sti=a...@mail.gmail.com>
and subject line Closing orphan bugs of the obsolete emacs21 packages
has caused the Debian Bug report #120786,
regarding emacs21-el: keyword highlighting bug in cperl-mode.el
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.)
--
120786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=120786
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21-el
Version: 21.1-2woody
Severity: normal
subroutine names which contain built in keywords/function-names
delimited by _ characters get highlighted incorrectly:
For example, in emacs20-el:
sub foo_print_desc ()
{
}
'foo_print_desc' gets highlighted in font-lock-function-name-face
whereas under emacs21-el the 'print' part gets highlighted in
cperl-nonoverridable-face and the foo_ and _desc parts don't get
any highlighting at all. (This may be a bug in emacs21, of course)
The emacs package is one I compiled from source on woody, but I didn't
make any changes to the source - the sid system here is down at the moment,
but it should be easy to check that the bug exists there too...
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux nessus 2.4.13 #2 SMP Sat Nov 3 15:40:48 GMT 2001 i686
+unknown
Versions of the packages emacs21-el depends on:
ii emacs21 21.1-2woody The GNU Emacs editor.
--- End Message ---
--- Begin Message ---
Hello,
All of these bugs are assigned to emacs21 which has been removed from
current versions of Debian several years ago, and thus the bugs are
orphan and nobody is paying attention to them anymore. I'm just doing
some cleanup with the intent to reassign valids bug later to current
Emacs packages, but I am not involved in the maintenance of the Emacs
package.
I am closing all of these bugs who are marked as unreproducible or
fixed-upstream or similar, sometimes for many many years and without
any input since then; and also others that don't seem relevant anymore
(e.g. failing to install). I'm trying to verify that they're indeed
properly tagged and addressed when possible.
If you feel that some issue related or included in the bug report is
not properly addressed, please reopen, reassign or report a new bug
against Emacs packages currently present in the archives.
Cheers.
--- End Message ---
