Your message dated Wed, 13 Aug 2025 19:19:19 +0000
with message-id <[email protected]>
and subject line Bug#1108732: fixed in cl-xlunit 0.6.3-3
has caused the Debian Bug report #1108732,
regarding cl-xlunit: Intend to Orphan
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.)
--
1108732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: cl-xlunit
Version: 0.6.3-2.2
Severity: important
X-Debbugs-Cc: Kevin M. Rosenberg <[email protected]>, Kevin M. Rosenberg
<[email protected]>, [email protected], Package Salvaging Team
<[email protected]>
Hi,
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 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 QA Upload
(NMU) to delayed=10. Specifically, since we are approaching the freeze
the upload will be delayed until after Trixie is released.
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 orphaning your package cl-xlunit. It meets the
following criteria:
- NMUs (more than one NMU in a row).
- 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
- Not uploaded by you in the last 15 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/cl-xlunit
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: 13.0
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 ---
Source: cl-xlunit
Source-Version: 0.6.3-3
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
cl-xlunit, 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 cl-xlunit 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: Sun, 03 Aug 2025 20:29:35 +0200
Source: cl-xlunit
Architecture: source
Version: 0.6.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1073021 1108732
Changes:
cl-xlunit (0.6.3-3) unstable; urgency=medium
.
* QA upload.
* Move package to QA team
Closes: #1108732
* Migrate packaging to Salsa Debian team
* Source format 3.0 (quilt)
Closes: #1073021
* Fix Homepage
* Upstream repository vanished thus providing fake watch file
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* d/rules: short dh
* d/copyright: DEP5
Checksums-Sha1:
b43e2b6d73111ed3115dd987252be015391b5a96 1881 cl-xlunit_0.6.3-3.dsc
0ba1dc345ed5abce80c74820529707328f9036aa 2632 cl-xlunit_0.6.3-3.debian.tar.xz
29211dabc8bad65ea69fbaee2eea60f25c8f2025 5866 cl-xlunit_0.6.3-3_amd64.buildinfo
Checksums-Sha256:
ff1d79e06e73fc9362badfe2c9b190e0247ad787e3438a8c7c834d521899a930 1881
cl-xlunit_0.6.3-3.dsc
87854fdefea9e02268c7e238555b5f94e3c08c37eeb62f99cef4f6cd8ef9e4da 2632
cl-xlunit_0.6.3-3.debian.tar.xz
fd6791590ae99954b64d4d7b777a0eb394ad127b383e97109db3e6bc18964314 5866
cl-xlunit_0.6.3-3_amd64.buildinfo
Files:
7b8e1da130b3a7a2bcbbb306b40bcee4 1881 lisp optional cl-xlunit_0.6.3-3.dsc
312c94f6f532d48a156bed6f833a3fe1 2632 lisp optional
cl-xlunit_0.6.3-3.debian.tar.xz
5b444608b97c9f520d21b414d51e9cad 5866 lisp optional
cl-xlunit_0.6.3-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiPqtARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGZ9w/+N2uqkmMNYZipVQv8aKtu3AgfJILExDCM
hLzlDgm0ob0ZfbYDp1SEo/ZBfZl4nvhdFNyxS/NxZVpGAvAyiiqtN2eamwCp2sG9
lLPVm5SvhPIGFtFRVDVBPRt3IS1fuQwP0Q9s015P0O0zQghXw6AgQHMIm0BD4Dh0
Jrnh/iZ1La4GKlzRTtIOZiIpRii0ji56Sxv9J8yJHspgRzyBoJsX9XxN70n8Jj7t
FsIDHsKDaYg9Ojxs6uy8Su24OqHZX1TTW3fdSHigyew4+nc4Iq4MplX11GEraXnY
+seQmwMJAIOEyTohxjJIfMRUz/NEAveSirtlw+XPaP4CGHIVPMeQXyNCCY9tNoSI
xpTE/iIfZzzkV4wQnI0jPe/au2z48tjmzl5fGFtUD9bUl0etde1BqiEXIqo0MYAU
6CYhUxQp27DqwenZPr2sGLTLTU3FHErED3mgQVkUej+nEeVImRKic1vraqlBhUbO
LOIUliEUBVDFi+ho7qCMlN8I0TIUUSN8vcRll6dw2iIgtQ8k5DYblihc/7+7wsue
sEe3OO6enqgU75FsOSaENIZ3pOP2JnqW2c6WfzhJz6jgN/eS1FO9nSjSSb0btXsj
qw1+41SIEI76tqPhwXOtfgc6UzH8oeZORj/FBh4JWSfN/2McEuNDGuGaHZKoPfV2
sOj+JhHnBp4=
=SLYq
-----END PGP SIGNATURE-----
pgpxucCqGK17O.pgp
Description: PGP signature
--- End Message ---
