severity 635667 minor
thanks
p...@debian.org wrote:
> While compiling toplevel forms in file
> /usr/share/emacs21/site-lisp/emacs-goodies-el/pod-mode.el:
> !! error (("Invalid escape character syntax"))
>
> Looks like I'll have to skip pod-mode.el for emacs21.
Or potentially conflicting with emacs21. That seems harsh. But one
that most people wouldn't notice at all so maybe a reasonable way to
go. In my case it would cause a removal of emacs21 and I would be
fine since 'emacs' is pointing to the newest and so everything would
be transparent. But I would guess that someone else will care.
> You know that emacs21 is a few versions behind, right? It's in
> 'oldstable' but not supported. emacs23 is current and emacs24 is about
> to be released... ;-)
Yes. :-) But most of these machines have been getting upgraded and
upgraded and upgraded. It is one of the best things about Debian!
After upgrading I have a checklist that I follow for additional
cleanup such as removing /etc/network/options and turning on B-trees
for directories with tune2fs -O dir_index /dev/hda5 and updating grub
and so forth. I believe that upgraded machines can be just as up to
date as newly installed machines and so far I believe to have
accomplished that with some extra cleanup actions. At one time most
of these machines were originally installed as Debian Woody.
Up until this point emacs21 hadn't been causing any problems and so
far nothing had bubbled up to putting it on my list of things to
remove after an upgrade. And so for some of the machines emacs21,
emacs22, and so forth I agree with you are lint that should be cleaned
up but have not been. But until you diagnosed this problem to emacs21
I hadn't realized that was the problem. Realizing this I have
downgraded the severity to minor.
I am pretty happy to remove emacs21 before doing any more upgrades
from Lenny to Squeeze. That is fine. I will add it to my cleanup
list now that I realize it. But still it was an upgrade failure and
needed extra action to get through and so it would be nice to have it
work without the failure or somehow direct the admin that emacs21 will
be a problem. Certainly if you can mark files as only certain
versions or newer that would seem to be a reasonable solution.
I am sure that whatever you decide will be fine.
Thanks!
Bob
P.S. I still think that Emacs 18 was the best of the versions so far. :-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
