Your message dated Sun, 18 Jan 2026 11:52:38 +0000
with message-id <[email protected]>
and subject line Bug#1118138: Removed package(s) from unstable
has caused the Debian Bug report #1118138,
regarding RM: multex-base -- RoQA; recommended package multex-bin removed 2012, 
low popcon, unmaintained
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.)


-- 
1118138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: multex-base
Version: 1.0-1.2
Severity: important
X-Debbugs-Cc: [email protected], Debian TeX maintainers 
<[email protected]>, TSUCHIYA Masatoshi <[email protected]>, 
Package Salvaging Team <[email protected]>

Hi Masatoshi,

I'm unsure what might be the best course of action with the package
multex-base.  If you consider it worth keeping inside Debian I would be
interested in helping you by following the Package Salvaging procedure
outlined in the Developers Reference[1]. From what I see, the package
seems to meet the criteria for this process.

On the other hand as reported in bug #1116140 it recommends some package
that was removed in 2012 (see bug #672762) and after this removal the
popcon stats are reduced dramatically[2].  So it might mean that this
package is useless inside Debian.  If this is the case I'd rather remove
this package.

So please let me know if you consider this package useful in Debian.  If
yes I believe the package could be maintained the Debian TeX
maintainers, and I took the liberty to create the Salsa repository
here[3].
 
This package was highlighted in the Bug of the Day[4] 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 help newcomers become familiar
with a consistent Git-based workflow.
 
Kind regards
    Andreas.
 
[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://qa.debian.org/popcon.php?package=multex-base
[3] https://salsa.debian.org/tex-team/multex-base
[4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks


-- System Information:
Debian Release: forky/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.38+deb13-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:

multex-base |    1.0-1.3 | source, all

------------------- Reason -------------------
RoQA; recommended package multex-bin removed 2012, low popcon, unmaintained
----------------------------------------------

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/1118138

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.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to