Your message dated Mon, 23 Feb 2026 09:57:50 +0000
with message-id <[email protected]>
and subject line Bug#1128337: Removed package(s) from unstable
has caused the Debian Bug report #1128337,
regarding RM: pyroman -- ROM; Largely obsolete by now, few users, no further
development.
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.)
--
1128337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128337
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:pyroman
User: [email protected]
Usertags: remove
In my opinion (as the author of pyroman) the package is largely obsolete by
now.
Development of pyroman is pretty much dead, also because my primary use
case (a
custom firewall that would manage several zones, DMZ, VPN etc.) is no longer
under my administration for a few years already.
The linux kernel routing has evolved beyond iptables (i.e., nftables),
and in
many cases I would now recommend to directly write such tables without a
meta
tool like pyroman. In fact, I recently moved to handle my own firewalls this
way entirely.
As a transition solution, pyroman can export the rules to iptables,
which can
be imported by iptables-load (which is used by pyroman internally anyway).
Popcon only lists 12 installations:
https://qa.debian.org/popcon.php?package=pyroman
Regards,
Erich
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
pyroman | 0.6.2-1.2 | source, all
------------------- Reason -------------------
ROM; Largely obsolete by now, few users, no further development.
----------------------------------------------
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/1128337
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 ---
