Your message dated Thu, 27 Feb 2025 17:44:05 +0000
with message-id <[email protected]>
and subject line Bug#1098452: Removed package(s) from unstable
has caused the Debian Bug report #1098452,
regarding RM: empire-lafe -- RoM; fails to build with gcc-15, unused, possibly
not working
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.)
--
1098452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098452
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: empire-lafe
Version: 1.1-1.2
Severity: serious
Justification: grab attention of maintainer
X-Debbugs-Cc: [email protected], Drake Diedrich <[email protected]>,
Package Salvaging Team <[email protected]>
Dear maintainer,
I suggest removing empire-lafe from Debian for the following reasons:
* It received a FTBFS bug when using the upcoming gcc version 15
* It was last uploaded by you 15 years ago
* Its a leaf package
* There are only very few votes in popcon
https://qa.debian.org/popcon-graph.php?packages=empire-lafe&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.
In case the package should be kept in unstable, please evaluate bug
#1096581 and fix it most favourably before it becomes RC since gcc-15
will become default. Once you have uploaded a fixed package please
close this bug.
In case the package should be removed from unstable, you may reassign this
bug report:
Control: severity -1 normal
Control: retitle -1 RM: empire-lafe -- RoM; rc-buggy
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:empire-lafe
Alternatively, you may wait a month and have it reassigned.
In case you disagree with the above, please add a wontfix tag to this bug.
Control: tags -1 + wontfix
Doing so will also prevent automatic reassignment.
Your package was highlighted in the Bug of the Day[1] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to familiarize newcomers with a
consistent Git-based workflow.
Kind regards
Andreas.
[1] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5,
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
empire-lafe | 1.1-1.2 | source
empire-lafe | 1.1-1.2+b1 | amd64, arm64, armel, armhf, i386, mips64el, ppc64el,
s390x
empire-lafe | 1.1-1.2+b2 | riscv64
------------------- Reason -------------------
RoM; fails to build with gcc-15, unused, possibly not working
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/1098452
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
