Your message dated Fri, 02 Jan 2026 20:42:33 +0000
with message-id <[email protected]>
and subject line Bug#1121624: fixed in nagzilla 2.0-1.2
has caused the Debian Bug report #1121624,
regarding nagzilla: Intand to Orphan: nagzilla
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.)
--
1121624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121624
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nagzilla
Version: 2.0-1.1
Severity: important
X-Debbugs-Cc: [email protected], Rhonda D'Vine <[email protected]>,
Package Salvaging Team <[email protected]>
Hi Rhonda,
This is an attempt to introduce a new procedure, which I propose to call
Intend To Orphan. While we have an established process for making minimal,
fine-grained changes to a package, it does not cover broader
improvements such as migrating to Salsa, updating the Standards-Version,
or adjusting the debhelper compatibility level. However, some packages
could benefit from more extensive changes, and this procedure aims to
provide a structured way to implement them. Unlike the well-established
Package Salvage procedure[1] which requires an active Uploader, the goal
here is to allow collaborative work on a package on Salsa, even if no
active uploader expresses interest in maintaining it.
--> Maintainer set to Debian QA Group <[email protected]>
If you do not agree to large-scale changes to this package, including
maintaining it on Salsa, feel free to close this bug or tag it as
'wontfix' to inform others. There is no obligation to continue reading
if your stance is clear, and that decision will, of course, be
respected.
Otherwise, I will follow the well-established timing of the ITS
procedure, waiting 21 days before performing a QA Upload to delayed=10.
This procedure has not yet reached consensus--I am simply exploring
whether it could be accepted. It was disussed at DebConf25 but some
consensus is pending. Please keep in mind that the goal of this process
is to help ensure that packages remain up to date and well maintained.
If you have suggestions for improving it, your feedback is most welcome.
I'm interested in orphaning the package nagzilla. It meets the
following criteria:
- NMU
- Bugs filed against the package do not have answers from the
maintainer.
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- No maintainer upload in the last 9 years
- Standards-Version < 4
I have set up a repository within Debian/[2]. This team functions
similarly to the former collab-maint on Alioth, allowing any Debian
Developer to make team uploads[3]. I understand that some maintainers
may prefer not to transition to collaborative maintenance, and I want to
emphasize that this is not intended as a hostile action. My goal is to
make the transition to using a Git repository on Salsa smoother and more
convenient for you.
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://salsa.debian.org/debian/FIXME
[3]
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group
[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')
Architecture: amd64 (x86_64)
Kernel: Linux 6.17.8+deb14-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 ---
Source: nagzilla
Source-Version: 2.0-1.2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
nagzilla, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <[email protected]> (supplier of updated nagzilla package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 23 Dec 2025 20:32:23 +0100
Source: nagzilla
Architecture: source
Version: 2.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Rhonda D'Vine <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1039278 1121624
Changes:
nagzilla (2.0-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
Closes: #1121624
* Maintain package in Debian team on Salsa
* Secure URI in Homepage
* Add systemd service files for nagzillac and nagzillad
Closes: #1039278
* Drop quilt from Build-Depends
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/copyright (routine-update)
* Drop fields with obsolete URLs.
* d/rules: dh_installinit --no-enable
* Pre-Depends: ${misc:Pre-Depends}
* Fake watch file since development stopped
* Standards-Version: 4.7.3 (routine-update)
* Remove Priority field to comply with Debian Policy 4.7.3 (routine-
update)
Checksums-Sha1:
0c4ea06356fc492cc581865fed11a2a7df70cd56 1793 nagzilla_2.0-1.2.dsc
708d1862688f784711b97b89d79bb6a3ace5db36 8184 nagzilla_2.0-1.2.debian.tar.xz
bb72b60b7733eccffab3f85fe415fd11953d1da0 5488 nagzilla_2.0-1.2_amd64.buildinfo
Checksums-Sha256:
9b6064e2d64f4cd3e2e11752d96f5c0b754eab5cccb1a0ea0e05a278eaccfae9 1793
nagzilla_2.0-1.2.dsc
ef8e0fe790fc156b8eff927e86c9352fcced7527decae9044802743d63de74d3 8184
nagzilla_2.0-1.2.debian.tar.xz
7658aac9d0a1be93cca19e45f58c072f1853f06ef12883c73a88692499045786 5488
nagzilla_2.0-1.2_amd64.buildinfo
Files:
35d4359616d80b7318b15e0d08130d52 1793 admin optional nagzilla_2.0-1.2.dsc
10773d2defa59f047a62123668df6991 8184 admin optional
nagzilla_2.0-1.2.debian.tar.xz
b6b701a8fd1b26242df7ed1f58ca4030 5488 admin optional
nagzilla_2.0-1.2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlK8mERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE8JxAAlK1EM13nkN6Gz/ak+tvmY9wtis+tA/Z0
ZKUU9hyYGny8IO0NrjrjKWLy5+sTE4f1UY1/FI5NJIkbCIJnoK3CNXYdCst3AkUO
LoURB38v5w2C9RGuJvnyGEeLTvZ3pjtpkZ/dU1hlM5U9aqJJzACl0UGuiVICGzrZ
A28EP1RPc1ZTTGOMc1GgeIzmzPcSRkWBk0dYTKLd6lnNCYPoelBoAcf2HjPPVdJi
IZO30VN0lyvovTVTBBS1XTM/HrNwxI0tc1Bokn1+u/SVBiHgHo0NBSVOUXZ1MYqv
AuX+KPvGwOiCmdsImknVycZQ2/rndKXlyE9rZmYqLWiIOb8Ncpcjb4ZHnf3Tn1Js
dojfpOUvjQa6xZRWYZSVvzTJoxDRddBvJpRXw01HGb9pabnZeJKErMvaq9M7GCFe
Mw52qoegcwAL/ts/wAo6mjQmxZFloOQJEf+e2KObsVHs0mr3RSbkGkfyoJOOC2H7
kvcCdhe+r7usiw1tW85Zojx88awb3+Ifxd7Ecz2fboKASoiLKbAQXJfoVaIQetAD
oY7zjgOSoLeznVIUc752pl8qjHyQ4JDBGW+xBFIWIWRiHbNrHdsJbM4CEhwTm9ko
EL6nEslraRpxu0RVtteDe9HDjnJ0Ojn2fvWmcXnq4RutI4EjFNjowevAE0mn5LQZ
Pd2v6Z/Nf+Q=
=TNKD
-----END PGP SIGNATURE-----
pgpRQQtYXjglm.pgp
Description: PGP signature
--- End Message ---
