Re: unar: diff for NMU version 1.10.1-3
Hi Boyuan,
On Mon, Apr 11, 2022 at 12:32:19PM -0400, Boyuan Yang wrote:
> Control: tags 1008569 + patch
> Control: tags 1008569 + pending
> X-Debbugs-CC: kraai@debian.org asias@debian.org julian@debian.org
>
> Dear maintainer,
>
> I've prepared an NMU for unar (versioned as 1.10.1-3) and
> uploaded it to DELAYED/14. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>
> diff -Nru unar-1.10.1/debian/changelog unar-1.10.1/debian/changelog
> --- unar-1.10.1/debian/changelog 2017-03-23 09:45:08.000000000 -0400
> +++ unar-1.10.1/debian/changelog 2022-04-11 12:27:28.000000000 -0400
> @@ -1,3 +1,12 @@
> +unar (1.10.1-3) unstable; urgency=medium
> +
> + * QA upload.
> + * Orphan the package (take over package maintenance) via
> + ITS process. (Closes: #1008569)
I maybe wrong but I was wondering if this is correct.
Section 5.12 in Debian's Developers Reference [1] clearly says:
Note that the process is only intended for actively taking over
maintainership. Do not start a package salvaging process when you
do not intend to maintain the package for a prolonged time. If you
only want to fix certain things, but not take over the package, you
must use the NMU process, even if the package would be eligible for
salvaging.
And, in this case you salavaged the package with the intention to
orphan it not to maintain it.
[1]. https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
--
Regards
Sudip
Reply to: