Source: judy
Version: 1.0.5-5.1
Severity: important
X-Debbugs-Cc: Troy Heber <troyh@debian.org>, 1070101@bugs.debian.org, Package Salvaging Team <team+salvage@tracker.debian.org>

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 04/07/25 14:36, Andreas Tille wrote:

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.

It appears there are only two options to the proposed ITN process,
either active rejection or passive acceptance. Perhaps there should be
a third option for active acceptance without the need for the 21 day
delay?

I am happy to more forward with the ITN process for this package. I
will note that the upstream project for Judy is dead, as the last
upstream release was 2009. I had considered removing it however there
are still a few packages that depend on it. In any case feel free to
push the NMU.

Troy

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEPdPUPs0+tNeF/HYE23wDYLLLZZcFAmf39goACgkQ23wDYLLL ZZd1lQ//aZWmXGIBss+473g2UH0OKgkNnnAG0wx2qs//k13Zo1Lzeb2KiMw5h+9F IhbHkpGm1d0vk4owKvz2RM9Prf+7M3u1X7JNBW36v1K0PiKN+ENnPsPMpByOrPJQ jSX9z/ho7k19ZuYDmwSOYUbeRydYmBnsLX/GBe4iiDr5+/ovN9FOAXDcuXIUu+Un Bbciv3FH86otYlgxb4d/m03cgiECZn8APMYdR1HpZ2dfc1sNp65WYI6vMR8wpTWj mbKHjPuN1nu4FezV2kjavpgA27mpuCE0l73bmBZXddt/y3YPGVUcVWK54m2Q57gC IMyd1RDghwleZPshofy6kQ/RPS0Uf6gqxNz4sWuItawT5ojde5liyusJ3eOn83vh 4mtsLZD878kRldVFnGFZO0FxIjT4X1CFwZzdY4FCQq/3OINkGmLE4qvffdR+xX4w VBAxMM4gPDdo/3G8EdS33KKtBVmwt4G+igXoKiFWQW6vUrFBGHqneIcVyl23jdjG NztFtmEZnHm2AcFqJT05/BUYCi9Ew6d7HIwUowEOHZmbAwrZvI1oJcCPoMU/zfpa m+aJfTKZSlPHet2EeSzSvots4O/jtfXnFuwKQ+La1EC02Ju2xoaYU1+kSZFg88Y+ BNBdVjDkvmaKOucuXQukFpd4FzNWO9N9+zsYZJJ76ZVJyqAan8k=
=t6aj
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Troy,

Am Thu, Apr 10, 2025 at 10:47:22AM -0600 schrieb Troy Heber:

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.

It appears there are only two options to the proposed ITN process,
either active rejection or passive acceptance. Perhaps there should be
a third option for active acceptance without the need for the 21 day
delay?

Good hint. This is for sure a misunderstanding. You are the maintainer
of the package in any case and you can perfectly do the upload yourself.
This is actually the most prefered case and I'd happily leave the final
upload to you. It was a pleasure for me to prepare the repository[1].
If you sign the upload and make it a maintainer upload by doing so this
would be great. Just let me know if you want to do so (I've just pushed
a "Closes:" for this ITN bug as well since it makes no sense to keep it
open for any upload)

I am happy to more forward with the ITN process for this package.

... only that if you upload its no NMU. ;-)

I will note that the upstream project for Judy is dead, as the last
upstream release was 2009. I had considered removing it however there
are still a few packages that depend on it. In any case feel free to
push the NMU.

Just let me know what you prefer. In any case we should act soon to not
create any conflict with the freeze. While its not a transition since
the code base is the very same it might not be the best idea to upload
non-leaf packages later than today.

Kind regards and sorry if the process is a bit unclear
Andreas.

[1] https://salsa.debian.org/debian/judy

--
https://fam-tille.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)