Sean Whitton <spwhit...@spwhitton.name> writes:
> This is more than the minimal change required to fix this bug. It seems
> like a good idea on a first look, but we should see if we're going to
> make any packages buggy by introducing a 'should' requirement here.
Agreed. The minimal change is probably this:
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 81b3542..fb2b6e5 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -979,7 +979,8 @@ repository where the Debian source package is developed.
or ``hg clone`` command. If no branch is specified, the packaging
should be on the default branch.
- More than one different VCS may be specified for the same package.
+ More than one ``Vcs-<type>`` field may be specified for the same
+ package, but only if the <type> parameters are all unique.
For both fields, any URLs given should use a scheme that provides
confidentiality (``https``, for example, rather than ``http`` or ``git``)
I think one could argue that the above change is informative, given that
Policy already says "A paragraph must not contain more than one instance
of a particular field name" in Policy 5.1.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
