Your message dated Thu, 08 Jan 2026 17:11:44 +0000
with message-id <[email protected]>
and subject line Bug#1118537: Removed package(s) from unstable
has caused the Debian Bug report #1118537,
regarding RM: jargon -- RoM; unmaintained, upstream considers it "phased out"
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.)


-- 
1118537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118537
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jargon
Version: 4.0.0-9
Severity: serious
Justification: grab attention of potential new maintainer
X-Debbugs-Cc: [email protected], Package Salvaging Team 
<[email protected]>

Hi,

I suggest removing jargon from Debian for the following reasons:

 * No maintainer
 * No upstream
   http://www.catb.org/jargon/download.html :

   "Also note that the info version has been phased out; it's an HTML
    world now."

This bug serves as a pre-removal warning.  If no real maintainer might
pick up the task to modernise the package and possibly base it on the
latest jargon database as suggested in bug #914542 it will be reassigned
to ftp.debian.org to actually request removal of the package.

In case there will be no new maintainer in 31 days I will reassign this
bug report:

    Control: severity -1 normal
    Control: retitle -1 RM: jargon -- RoM; unmaintained, unsupported upstream
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:jargon

In case you want to take over maintenance, please add a wontfix tag to
this bug.

    Control: tags -1 + wontfix


This 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 help newcomers become familiar
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: forky/sid
  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)
Kernel taint flags: TAINT_WARN
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:

    jargon |    4.0.0-9 | source, all

------------------- Reason -------------------
RoM; unmaintained, upstream considers it phased
----------------------------------------------

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

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

Reply via email to