Bug#920355: debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers
control: tag -1 +pending Hello, On Thu 24 Jan 2019 at 05:05PM +01, Chris Lamb wrote: > diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst > index 44080c9..013aae4 100644 > --- a/policy/ch-controlfields.rst > +++ b/policy/ch-controlfields.rst > @@ -973,10 +973,11 @@ repository where the Debian source package is > developed. >- Mtn (Monotone) >- Svn (Subversion) > > -In the case of Git, the value consists of a URL, optionally followed > -by the word ``-b`` and the name of a branch in the indicated > -repository, following the syntax of the ``git clone`` command. If no > -branch is specified, the packaging should be on the default branch. > +In the case of Git and Mercurial, the value consists of a URL, > +optionally followed by the word ``-b`` and the name of a branch in > +the indicated repository, following the syntax of the ``git clone`` > +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. Seconded and committed, thanks. -- Sean Whitton signature.asc Description: PGP signature
Bug#897217: Bug#920355: debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers
On Thu, Jan 24, 2019 at 05:05:07PM +0100, Chris Lamb wrote:
> Policy §5.6.26 permits "-b" only in the case of Vcs-Git:
[...]
> However, Mercurial (ie. "Vcs-Hg") supports this too in its
> equivalent "hg clone" command. This change was triggered via
> #920314 in Lintian.
>
> A simple patch (also attached) might be:
>
> commit 3e66c9e470053fcc77169efa82833252971d211c
> Author: Chris Lamb
> Date: Thu Jan 24 16:55:21 2019 +0100
>
> Permit branch specifications ("-b") in Mercurial Vcs-Hg headers too,
> not just Vcs-Git. (Closes: #-1)
>
> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> index 44080c9..013aae4 100644
> --- a/policy/ch-controlfields.rst
> +++ b/policy/ch-controlfields.rst
> @@ -973,10 +973,11 @@ repository where the Debian source package is
> developed.
>- Mtn (Monotone)
>- Svn (Subversion)
>
> -In the case of Git, the value consists of a URL, optionally followed
> -by the word ``-b`` and the name of a branch in the indicated
> -repository, following the syntax of the ``git clone`` command. If no
> -branch is specified, the packaging should be on the default branch.
> +In the case of Git and Mercurial, the value consists of a URL,
> +optionally followed by the word ``-b`` and the name of a branch in
> +the indicated repository, following the syntax of the ``git clone``
> +or ``hg clone`` command. If no branch is specified, the packaging
> +should be on the default branch.
seconded.
> Thank you for maintaining Policy.
seconded too! :)
--
tschüß,
Holger
---
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
signature.asc
Description: PGP signature
Bug#920355: debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers
Package: debian-policy
Version: 4.3.0.1
Severity: minor
Hi,
Policy §5.6.26 permits "-b" only in the case of Vcs-Git:
In the case of Git, the value consists of a URL, optionally
followed by the word -b and the name of a branch in the
indicated repository.
However, Mercurial (ie. "Vcs-Hg") supports this too in its
equivalent "hg clone" command. This change was triggered via
#920314 in Lintian.
A simple patch (also attached) might be:
commit 3e66c9e470053fcc77169efa82833252971d211c
Author: Chris Lamb
Date: Thu Jan 24 16:55:21 2019 +0100
Permit branch specifications ("-b") in Mercurial Vcs-Hg headers too,
not just Vcs-Git. (Closes: #-1)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is
developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+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.
Thank you for maintaining Policy.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org chris-lamb.co.uk
`-
From 3e66c9e470053fcc77169efa82833252971d211c Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Thu, 24 Jan 2019 16:55:21 +0100
Subject: [PATCH] Permit branch specifications ("-b") in Mercurial Vcs-Hg
headers too, not just Vcs-Git. (Closes: #-1)
---
policy/ch-controlfields.rst | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+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.
--
2.20.1
