Your message dated Mon, 11 Aug 2025 07:19:38 +0000
with message-id <[email protected]>
and subject line Bug#1102296: fixed in judy 1.0.5-5.2
has caused the Debian Bug report #1102296,
regarding ITN: judy
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.)
--
1102296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102296
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: judy
Version: 1.0.5-5.1
Severity: important
X-Debbugs-Cc: Troy Heber <[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 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
the first upload will be to `experimental` and once Trixi is released an
upload to `unstable` will follow.
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 judy. It meets the following
criteria for the ITN procedure
- 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
- Not uploaded by you in the last 10 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/judy
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: trixie/sid
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.17-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: judy
Source-Version: 1.0.5-5.2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
judy, 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 judy 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: Mon, 07 Apr 2025 09:03:05 +0200
Source: judy
Architecture: source
Version: 1.0.5-5.2
Distribution: unstable
Urgency: medium
Maintainer: Troy Heber <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1070101 1102296
Changes:
judy (1.0.5-5.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Maintain package in Debian team on Salsa
Closes: #1070101, #1102296
* Add Homepage
* d/watch:
- version=4
- Secure URI
* d/README.source: Remove since redundant
* 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.
* Drop no longer supported add-log-mailing-address setting from d/changelog.
* debian/control: Remove empty control field Uploaders.
* Replace XC-Package-Type with Package-Type.
* Remove unnecessary XS-Testsuite field in debian/control.
* Remove field Section on binary package libjudydebian1 that duplicates
source.
* Do not build parallel since this breaks manpage creation
* Make sure default dh_missing --fail-missing will not fail
* Permit failure of blhc in Salsa CI
Checksums-Sha1:
d852226d474482ff1ed2afc9a1186f692091252f 1890 judy_1.0.5-5.2.dsc
477d6dc135f43fbb9cb53cb97d8eb1f1c00c3d87 7408 judy_1.0.5-5.2.debian.tar.xz
bcf4cd66661411cdefdfb8012bb4cd2e2b9d1292 6449 judy_1.0.5-5.2_amd64.buildinfo
Checksums-Sha256:
080ff0658e9de80b3d5933d94df8f3ecaeed9f78bb94a2599a94b2b5603fb231 1890
judy_1.0.5-5.2.dsc
8e82cda8a7b02104f80a059aba2c03543ac7fb205de5772f4f0c57d1bf4d9288 7408
judy_1.0.5-5.2.debian.tar.xz
4bfb06c71592ce7bcdf376c30e994d64ca1f253bd71f19043f6fb4cb5aff9129 6449
judy_1.0.5-5.2_amd64.buildinfo
Files:
e35c3948bf478a7e60ba6a60532e73f8 1890 libs optional judy_1.0.5-5.2.dsc
5bfa6571cefe64c8bbe595bf7d661339 7408 libs optional
judy_1.0.5-5.2.debian.tar.xz
186ca9553ddb07f715e0c551e139b25c 6449 libs optional
judy_1.0.5-5.2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmiFxn8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFutw/8CrXNPHNJVP6nMABd/C4Xxu8yV0GVif0Z
WL9dVnxcf66EBECH93ljn7kdl2eSpuQew3JRvI+g0CPYpPuhPAq8Hh0KOmybTWzA
m+kkkMvihvlZByxO6NExGf3mborAk7M/3QSJfR7cD5d5PsO5ULxz0g61trfjyFDA
XVdECKexvGFzp+AL3yFE3qEmgLNDf28g/zPSP/lznawP9BMh1FS4K1kOYNyuH7j8
pm8v/wwelpRPZLcU/g+oWXKoZiUDZMwD5mJjsgFUU8hzNuz9bPmfg3C9zroVJsrv
6jLXhrtE4sJ882ohDXcnWhmM6qArnSkTki+QU/2LvxvNLl717jCtDiNW8WlUhXwq
FaVG+rq1tmJHlJLgjuDDkNmTdyUYwXpTnNvNU21C4Ffe9aEIGsr4jFyJDjqQMVEO
Zv8ph+ST76rFOb521SZZqKwB95uxLAM9EGRS6GJtVq1cb4t8iXxTNI876RmuEtxy
wzwywuLS5DAVNMzMDtm1MFrPzA/K26RPRp9A6yUXC/dXuFoXxpGjKJgN6+ECNA4D
zHKCpLcy8fA4SoImMYySGvZnE7wVW9Ki6yk6DoiivrMC0+BsME0Gn9tmF85UIB4B
/8otCj/LSZXinEk5enTX+nxMK4+tTOB7DElenOse7b/9pSxeA7W6KvORATOd0tBF
YqBU8HNBF/w=
=/cbP
-----END PGP SIGNATURE-----
pgp648MvA0kvv.pgp
Description: PGP signature
--- End Message ---
