Your message dated Sun, 18 Sep 2022 19:55:51 -0700
with message-id <87v8pkqdhk....@hope.eyrie.org>
and subject line Re: Bug#961294: Allow derivatives to define parent project
fields
has caused the Debian Bug report #961294,
regarding Allow derivatives to define parent project fields
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 ow...@bugs.debian.org
immediately.)
--
961294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 4.5.0.2
Severity: normal
Hello,
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>. This would make it easier for derivatives to
clearly specify where packaging changes should be submitted upstream. In
dpkg, this can be enforced by recursively running `dpkg-vendor --query
Parent` and ensuring that <PARENT> matches one of those, or in Lintian
by emitting an error if that is not the case.
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.
Thoughts?
[1] https://salsa.debian.org/lintian/lintian/-/merge_requests/310
--
Simon Quigley
tsimo...@debian.org
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
Russ Allbery <r...@debian.org> writes:
> Simon Quigley <tsimo...@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).
Per my previous reply, I'm (very belatedly) closing this as wontfix since
I don't think it's a matter for Debian Policy and should instead be
documented in Ubuntu Policy (or, should someone ever feel inspired, a
separate guide on to how to be a downstream distribution of Debian).
--
Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
--- End Message ---
