Your message dated Wed, 13 Aug 2025 00:05:34 +0000
with message-id <[email protected]>
and subject line Bug#1107729: fixed in scanssh 2.1.3.1-1
has caused the Debian Bug report #1107729,
regarding scanssh: Intend to Orphan scanssh
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.)
--
1107729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107729
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: scanssh
Version: 2.1.3.1-0.2
Severity: important
Tags: patch
X-Debbugs-Cc: Rene Weber <[email protected]>,
[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 Non-Maintainer 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 scanssh. It meets the following
criteria
- NMUs (more than one NMU in a row since 2005).
- Bugs filed against the package do not have answers from the
maintainer.
- Upstream has released several versions, which were only
available thanks to NMUs
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- Not uploaded by you in the last 20 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/scanssh
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: 13.0
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5,
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.27-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: scanssh
Source-Version: 2.1.3.1-1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
scanssh, 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 scanssh 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: Fri, 13 Jun 2025 07:24:04 +0200
Source: scanssh
Architecture: source
Version: 2.1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1097851 1105604 1107729
Changes:
scanssh (2.1.3.1-1) unstable; urgency=medium
.
* QA upload.
* Orphan package
Closes: #1107729
* Add Homepage
* Point Vcs fields to Debian team on Salsa
* Modern prototype syntax to build with gcc-15
Closes: #1097851
* d/rules: short dh
Closes: #1105604
* d/copyright: review
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
Checksums-Sha1:
692c64db2f66d27450dbd25b6b75cfbedf88ed6c 1899 scanssh_2.1.3.1-1.dsc
ac17778b795a78752feb7bd25b2952e84e9e033f 4952 scanssh_2.1.3.1-1.debian.tar.xz
e4739729463a449217c1c517a629451c8bf53ac1 6777 scanssh_2.1.3.1-1_amd64.buildinfo
Checksums-Sha256:
1402dfde20764f0bb2c99a4749b1f8dabd2bc502985ae99ab834d52f18ce81c4 1899
scanssh_2.1.3.1-1.dsc
e015451225f441f404cf6d3e0b2fe7ce6d5f5e45b7554a882d06ce7bac479aa4 4952
scanssh_2.1.3.1-1.debian.tar.xz
9d19f424f48fc54dafc750873947e0f507ff3ca1405575645f8533f68c73400d 6777
scanssh_2.1.3.1-1_amd64.buildinfo
Files:
29187d3205d7ec90c7414fc6425bc0de 1899 net optional scanssh_2.1.3.1-1.dsc
ce6578370c884dd1f44cec0968a73df8 4952 net optional
scanssh_2.1.3.1-1.debian.tar.xz
e73f30970d472fea144cf04cde1fc993 6777 net optional
scanssh_2.1.3.1-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiLyvURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEAdBAAjcOMKnY9P6biSjiKsNSoYUa5YWu9gLgb
HE6NB5hCKLSjFqSybDfaAEj/sryG7YIdY+QAhbhMZ7UAulkD0SVj0YF9c99wKQ4R
XBYoS16hU7jxaWQFEBI7R/ucLkeIwjRt8VbGTAG8UwAHuNLprlDLOmoS9EyBuwNP
UAMH8m1RWDtAt+VymneP7WOjZepPxnnhtpVV51ArxlE95FIAiqYnT4D2suiLlR36
1t3Qxw/RlLUF9fRgl88pqK7GwcdO9WlOYZC9dF/e3a7YswqN50822eyJXVOtJmuy
qq6wqMutREx+SecnfIP1QFPIZKAr9+JgumbLRowfDxnzURJkat6M/Y0BIJMBvEHK
FpBwsrHUKFN/UF67vRE2tmEi64cL6G/O/n6b3z1vi9nNYwfur7oOd+v5zfzL5ZS9
Q4ONowlSafkhHt/XqQ14IUThFGHnWCPFkkrCoBnJ8vbjiimWRZkbD5KSmAxwmlaW
x23nZMjJdtXLUPBj9IQcCMIhckwm6tqpCuLlknjrw5+p6pVOgMuhWeq1m39TUmxo
4cK3NJrHnQgFRSrlhVsuCpJbnpBYJTyCDHEM1f3uraGTKNw3Avubtrf1sQEsHdWp
luu4Ge47WPIGiC6wugtzLJ+DoRYl2ILsZnI7DxpPg0DtWacvA295fwi9cktTmmUJ
2YInJQ4rErU=
=tTOJ
-----END PGP SIGNATURE-----
pgpPkIK6VcRIc.pgp
Description: PGP signature
--- End Message ---
