Your message dated Fri, 05 Sep 2025 07:19:04 +0000
with message-id <[email protected]>
and subject line Bug#1109933: fixed in ddate 0.2.2-2
has caused the Debian Bug report #1109933,
regarding ddate: 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.)
--
1109933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109933
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ddate
Version: 0.2.2-1.1
Severity: important
X-Debbugs-Cc: Package Salvaging Team <[email protected]>,
Sebastian Schmidt <[email protected]>, наб <[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 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.
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 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 ddate. It meets the following
criteria:
- NMUs
- 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 X 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.
This 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 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/ddate
[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: ddate
Source-Version: 0.2.2-2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ddate, 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 ddate 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: Wed, 26 Mar 2025 09:13:15 +0100
Source: ddate
Architecture: source
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1109933
Changes:
ddate (0.2.2-2) unstable; urgency=medium
.
[ Andreas Tille ]
* QA upload.
Closes: #1109933
* Update renamed lintian tag names in lintian overrides.
* New homepage
* Point Vcs fields to Salsa
.
[ наб ]
* Update d/gbp.conf for new version
* E: ddate: alien-tag no-upstream-changelog
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Secure URI in copyright format (routine-update)
* watch file standard 4 (routine-update)
Checksums-Sha1:
affc083932883e7c1f42cd7962c80d7cd3b12927 1817 ddate_0.2.2-2.dsc
c8fbfa88aada80782eb9fee3dec8c4ffc7e80e6c 2616 ddate_0.2.2-2.debian.tar.xz
687d990317069a09aa2286c3c5cdb3b8cd40a29a 7055 ddate_0.2.2-2_amd64.buildinfo
Checksums-Sha256:
b81eaa1b993ef906e6179e028de77ed36799e973656ee347b4974e5fc38bb51c 1817
ddate_0.2.2-2.dsc
1ab1a3006ae7f824c70a1ad30e6aceeff28dbae7516aa5b30a1ea33dbf49faf8 2616
ddate_0.2.2-2.debian.tar.xz
1f2c93096820f2cb8a0b12d6a3550cd0842f51c141c745a05f6b58c699425de4 7055
ddate_0.2.2-2_amd64.buildinfo
Files:
5e721235972fa8cd8504b1cb340eb8ae 1817 utils optional ddate_0.2.2-2.dsc
331485ceab7fd254f81af58d07547ffc 2616 utils optional
ddate_0.2.2-2.debian.tar.xz
f20813f6ba14806a32e60cf0f47bf5d1 7055 utils optional
ddate_0.2.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmitVVsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE7Hg//XMLog+r/cD/uYRObuVcOi2wPg9mH5Gia
6oLEAzIeC/XpyKrLe+tSJHrZ7bbCz4KHxiECFhRX7IVAhcBV1XpoK9jxY9TZUPSC
J+3OC1l3SEQxGQM1SUBaqd89jGFvgu/4vKIoELyJOiSeyC0wQeQoUvd/SriNtnvK
8b/AQxrRnQz9TcbmcvPK53EteN85F1u5a56XTEl4+iF5aypVDjLC8O25Jzpoz2rg
ntr5PkoO2dxT3SdKBD/80Aa9dTsRR6dKoNA+VvxobwQH7LhSd7vFTgvRLvhPoNfD
l+wjtkIdFA7cAY5Hl/IRz3Un0UpSC60TOVvRkQnF6bd+dC/HKosv2nIssltZfXMn
WhaAKVdLjr8jQrs251M66pHLJs3O+mIKictq8yiDNPs6xoSslSL9qIhuU6fTzofw
gsW6ScTFiVcLN51/exFqlY8vTMueDWZEt9iiflMEnra8+rhIBzp4SAv/d6SXqsDZ
hWCrUHJsSku5e3O8GqUnHDmwy6uYTSW/vcfRSAOxmB173KKCk6t3DQe1XEKRK/PU
XPuaswNI+4G0g5UiZnicZtONtS2AVDXXcouyfCnOgpmDD5FnsD3/qXRNPKPZTkL5
nsPqAvDoLsHAj7zMuigtBodv8mfU2Q4F/xFHB2qGr8lzGU4g3GM1d2ENnJLp9v60
kJFVyLan+v0=
=TZcz
-----END PGP SIGNATURE-----
pgpgnO5KysUgo.pgp
Description: PGP signature
--- End Message ---
