Bug#961294: Allow derivatives to define parent project fields
Simon Quigley <tsimonq2@debian.org> writes:
> I recently had a discussion in a Lintian merge request[1] where I
> submitted code solidifying existing behavior in the Ubuntu Desktop and
> Lubuntu teams. As I stated there, it is common practice in those teams
> (and I am sure it exists in others as well) to specify a
> `XS-Debian-Vcs-Browser` and/or `XS-Debian-Vcs-Git` field to point to
> Salsa.
> The rationale for this is to allow packaging changes to flow back
> upstream to Debian when Ubuntu's packaging repository is in a different
> location (when Ubuntu has a permanent downstream delta but continues to
> rebase that delta on top of Debian's changes).
> I would like to solidify this existing practice by modifying Debian
> Policy, amending 5.6.26 to allow usage of <PARENT>-Vcs-Browser and
> <PARENT>-Vcs-<type>.
I'm not sure I understand why you want to make this change to Debian
Policy. Isn't this a matter for Ubuntu policy? The new fields wouldn't
be in the package in Debian (because they wouldn't be meaningful there).
> I would also like to use this as an opportunity to deprecate
> `Original-Maintainer` in favor of `Debian-Maintainer` and allow for
> `Debian-Uploaders` as well.
Similarly this seems to be entirely a question for Ubuntu (and Lintian, of
course).
--
Russ Allbery (rra@debian.org) <https://www.eyrie.org/~eagle/>
Reply to: