Your message dated Sun, 28 Sep 2025 07:05:13 +0000
with message-id <[email protected]>
and subject line Bug#1104687: fixed in p910nd 0.97-2
has caused the Debian Bug report #1104687,
regarding Intend to Orphan: p910nd
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.)
--
1104687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: p910nd
Version: 0.97-1
Severity: important
X-Debbugs-Cc: [email protected], [email protected], Mario Izquierdo
(mariodebian) <[email protected]>, Package Salvaging Team
<[email protected]>
Hi,
This is an attempt to introduce a new procedure, which I propose to call
Intend To NMU. 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.
If you do not agree to large-scale changes to your package, including
maintaining it on Salsa, you are welcome to close this bug or tag it as
'wont-fix' to inform others. There is no obligation to continue reading
if your stance is clear, and your decision will, of course, be
respected.
Otherwise, I will follow the well-established timing of the ITS
procedure, waiting 21 days before performing a Non-Maintainer Upload
(NMU) to delayed=10. Specifically, since we are approaching the freeze
we will not upload before the Trixi release.
This procedure has not yet reached consensus-I am simply exploring
whether it could be accepted. It remains open for discussion,
particularly at DebConf25. Please keep in mind that the goal of this
process is to assist in keeping your package up to date. If you have
suggestions for improving it, your feedback is most welcome.
I'm interested in NMUing your package p910nd. It meets the following
criteria for the ITN procedure
- 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
The Git repository mentioned in Vcs-Git before did not existed any more
- Not uploaded by you in the last 5 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. 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.
Your package was highlighted in the Bug of the Day[3] 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://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/debian/p910nd
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: trixie/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)
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: p910nd
Source-Version: 0.97-2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
p910nd, 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 p910nd 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: Sat, 13 Sep 2025 07:54:19 +0200
Source: p910nd
Architecture: source
Version: 0.97-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 926497 980514 1039306 1104687
Changes:
p910nd (0.97-2) unstable; urgency=medium
.
* QA upload.
Closes: #1104687
.
[ Andreas Tille ]
* Move packaging Git to Salsa since former repository vanished
* Homepage moved to Github, point watch file to Github
Closes: #980514
* d/copyright: DEP5
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Trim trailing whitespace.
* Add upstream metadata
* Pre-Depends: ${misc:Pre-Depends}
* debian/dirs: removed
* Permit failure of blhc in Salsa CI
.
[ Helmut Grohne ]
* Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #926497)
.
[ наб ]
* debian/[email protected]: add, mask p910nd.service (Closes: #1039306)
* d/README.Debian: describe systemd service setup
* debian/postinst: add to enable p910nd@$P910ND_NUM on upgrade
* Remove generated changelog with d/clean instead
Checksums-Sha1:
8a0a765befc9d522944a3aeff50429e5831e0696 1840 p910nd_0.97-2.dsc
70585fb669c38d22b4298bfc5804c2d6780bf64f 6280 p910nd_0.97-2.debian.tar.xz
00cde28c12b39b2e92653ab16ac04d1684038e17 6034 p910nd_0.97-2_amd64.buildinfo
Checksums-Sha256:
b6e82a67cfb248b464ea670d3ed274828ddbc0ec87def20631f55c0d4382afe6 1840
p910nd_0.97-2.dsc
a9116b5f67dcd7a5978b599729b3db7656e18e02f740e1b53886a518287bae78 6280
p910nd_0.97-2.debian.tar.xz
69e23b0bb691361209ed0ef616e9ba2b4cab689a22cd290d98af4353955b32ec 6034
p910nd_0.97-2_amd64.buildinfo
Files:
38289ee1e651758f9f16a72d9ee165c0 1840 net optional p910nd_0.97-2.dsc
12831a0c6598efa775b11b3fd3a6020e 6280 net optional p910nd_0.97-2.debian.tar.xz
273c2a051fb259c448c4ef9049894c81 6034 net optional
p910nd_0.97-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmjFB2QRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHfFw/7BvLN5fEB1dbGdhlqYZlTI1wQs41oHtx9
ev7vfgqO++GD9sSon2tMNaRM/y3Kzt05MHaF+nnx9Drmyqd/QvlhSvaNcOnK96H/
Xr33xBRTr7igqgLpBMLsCgEiJkFIxOw5ndZkBWLyTuxD0mbOu68iVOUfaOiuww+D
LgGwRHKcjL1NyumE6TJbmilkMT1juCTma64dvS+TA8e3YSv0ciyQj3xNBCD6LGMo
NGxqyi7kgyZLPHtfEiW6gSQz7TxGAn3WYercw/nitHldA7ScPF5kOPIj3vLWqe+T
Vf7S/ANLj3u/enGTfIOULcvKiKi9NFpTzksL+akNe86FHgDamATqUugnSw9vzNAS
LbTJK7+ZcgGl0yxTQ4W+ViXU842o93YU6Dcx2TqeuMNyl2gsatXzG7R0KpaMy2CT
KyKiZMFhxbXy7E35YDTltKSvNPwIfOJJ4qhE35ESQWcs0e1QiUY2ilYeFWGdOs2r
V/OGMyj32bXmMrNBzC1VbQhFuMIIXPuGTyTgdbaDYiwsi11PCfGPxpu6CEh/S/xX
jFftKmtWTwQXPEWQUwytakZSUivIdqEv4Fdn1YJpzo9W3HwJiUZo5xsyYuWF7t+p
eCiH5Co4vZhLUEt4Eq84HCJeMLh+SVGanuJ+9GXI7/lirIv90HxWHR877/k5+ys8
RwbEJ9L7tgo=
=TXBB
-----END PGP SIGNATURE-----
pgpADVsYDPRrE.pgp
Description: PGP signature
--- End Message ---
