Your message dated Wed, 16 Apr 2025 13:03:14 +0100
with message-id <a871a3f3-7a3e-4d0f-a0ce-14a4736d5...@sirena.org.uk>
and subject line Re: Bug#1103291: RM: xemacs21 -- RoQA; not in trixie; severely
outdated
has caused the Debian Bug report #1103291,
regarding RM: xemacs21 -- RoQA; not in trixie; severely outdated
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.)
--
1103291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xemacs21
Version: 21.4.24-12
Severity: wishlist
Hi Mark,
xemacs21 has not made it to trixie. I suggest to remove it from Debian.
It has gained two RC bugs and is hindering autoconf2.13 from being
removed.
Thanks for considering,
Bastian
--- End Message ---
--- Begin Message ---
On Wed, Apr 16, 2025 at 09:55:07AM +0200, Bastian Germann wrote:
> xemacs21 has not made it to trixie. I suggest to remove it from Debian.
> It has gained two RC bugs and is hindering autoconf2.13 from being
> removed.
No, I use the package every day. The underlying issue here is that GCC
introduced some as far as I've been able to tell mandatory warnings
which break the ability to configure the package, that's very unhelpful
and prevents a change to stop rebuilding the autoconf stuff (which I
don't think is actually required). There's nothing fundamentally
changed about the program here, it's just churn like all the debhelper
stuff.
signature.asc
Description: PGP signature
--- End Message ---
