Re: package-superseded-by-perl
On Wed, Jan 16, 2019 at 11:48:43AM +0100, Cyr Bol wrote:
> I want to clarify that my request in #912682 is not backed by experience.
> I'm pretty new here and don't know yet much about Debian packaging nor
> about the Perl maintainer group's habits.
No worries, it was a completely valid question / request!
> I'm ready to update the group's policy to add a note about that (I think
> I'm not too bad at documenting stuffs). But, I don't know where would be
> the best place:
>
> * The Debian Perl group policy (
> https://perl-team.pages.debian.net/policy.html)?
I think this is the right place as soon as we have agreed on the policy
(as discussed in this thread.)
> * The Debian Perl policy (
> https://www.debian.org/doc/packaging-manuals/perl-policy/)
This one is wider than just the pkg-perl group and mostly lists
requirements for Perl packages in general.
> Nor how to do it.
The sources for the pkg-perl group (aka. perl-team aka. Debian Perl Group)
docs are at https://salsa.debian.org/perl-team/perl-team.pages.debian.net
which we should probably mention on the web site. So I guess merge
requests or just pushing obviously correct changes there is the way to go.
(Gregor will hopefully correct me if I'm giving out wrong advice :)
> Also, I wonder if this kind of bugs shouldn't be marked with the "wontfix"
> tag (and, possibly also the "sid", "stretch-ignore", and "buster-ignore").
> Would you mind if I do that?
The *-ignore tags should only be used by release managers, as documented
at https://www.debian.org/Bugs/Developer#tags .
"wontfix" doesn't feel quite right to me, these will be fixed by uploading
newer upstream releases if those ever materialize.
"sid" alone would mean "this applies just to the sid suite even if the
same package version is also in other suites." It normally goes with
"buster" to indicate that this package version is fine in stretch
but broken in buster and sid. It mainly signals that people concerned
about RC bugs in the stable suite need not be concerned about this.
I think "buster" + "sid" would be appropriate if any of the affected
versions are currently in stretch too.
Hope this makes sense, and thanks for helping out!
--
Niko
Reply to: