Your message dated Mon, 25 Aug 2025 10:52:06 +0000
with message-id <[email protected]>
and subject line Bug#1106688: Removed package(s) from unstable
has caused the Debian Bug report #1106688,
regarding RM: cl-lml2 -- RoM; orphaned upstream, low popcon, leaf package
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.)
--
1106688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106688
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cl-lml2
Version: 1.6.6-4.2
Severity: important
X-Debbugs-Cc: Kevin M. Rosenberg <[email protected]>, Package Salvaging Team
<[email protected]>, Sébastien Villemot <[email protected]>,
Marcos Talau <[email protected]>, [email protected]
Dear maintainer,
I suggest removing cl-lml2 from Debian for the following reasons:
* Upstream seems to have orphaned the package - at least I can't
find the homepage any more
* There are no votes in popcon
https://qa.debian.org/popcon-graph.php?packages=cl-lml2&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
* Besides the two NMUs (NMUers in CC in case they might step in)
there was no upload since > 15 years
* Even the simple bug to use source format 3.0 does not get any
response since nearly one year
* Its a leaf package which is not needed as (Build-)Depends by
any other package
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 tag this bug
`wontfix`. If there are good reasons to keep this package inside Debian
I would happily to Salsa (probably in Common Lisp team) and fix the said
bug.
In case the package should be removed from unstable, you may reassign this
bug report:
Control: severity -1 normal
Control: retitle -1 RM: cl-lml2 -- RoM; orphaned upstream, low popcon, leaf
package
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:cl-lml2
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
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/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: 13.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
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:
cl-lml2 | 1.6.6-4.2 | source, all
------------------- Reason -------------------
RoM; orphaned upstream, low popcon, leaf package
----------------------------------------------
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/1106688
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.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
