[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#920355: marked as done (debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers)



Your message dated Fri, 25 Jan 2019 09:06:07 +0000
with message-id <E1gmxR9-0004rl-Rf@fasolo.debian.org>
and subject line Bug#920355: fixed in lintian 2.5.124
has caused the Debian Bug report #920355,
regarding debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers
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 owner@bugs.debian.org
immediately.)


-- 
920355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920355
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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 <lamby@debian.org>
    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
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-
From 3e66c9e470053fcc77169efa82833252971d211c Mon Sep 17 00:00:00 2001
From: Chris Lamb <lamby@debian.org>
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


--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.124

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920355@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 24 Jan 2019 23:47:53 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.124
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Description:
 lintian    - Debian package checker
Closes: 920184 920228 920355 920376
Changes:
 lintian (2.5.124) unstable; urgency=medium
 .
   * Summary of tag changes:
     + Added:
       - obsolete-crypt-alias
       - obsolete-des-encryption
 .
   [ Chris Lamb ]
   * Locate and process .buildinfo files if mentioned in a .changes file;
     previously it was only examined if explicitly referenced. Thanks to
     James Clarke. (Closes: #920228)
   * If the changelog entry is missing a maintainer (eg. " -- <missing>"),
     don't assume that it's an NMU. (Closes: #920184)
   * Permit "-b" branch specifications in Mercurial Vcs-Hg control fields.
     (Closes: #920355)
   * Really fix summary generation code to match the "WIP" entry in the
     changelog after moving to gbp-dch(1).
   * Add "could break" as a spelling correction.
 .
   [ Felix Lechner ]
   * Allow tests to be freely organised such as by check. (MR: !132, !134)
 .
   [ Zack Weinberg ]
   * Add a check for binaries using obsolete DES encryption.
     (Closes: #920376)
 .
   [ Paul Wise ]
   * Add several spelling corrections.
Checksums-Sha1:
 f20e8638216d72eb54e19b0c941321c1ac4e47b0 3581 lintian_2.5.124.dsc
 9c897af8cfe39a56d08afe0ff10b2206ef7c3e26 1639588 lintian_2.5.124.tar.xz
 d894ab88395b8464780b4e61e02f789b00a3e4ea 1188532 lintian_2.5.124_all.deb
 8d7ec17eeeab43b035df576d727ba19e4a8eb75e 17544 lintian_2.5.124_amd64.buildinfo
Checksums-Sha256:
 748d381c864d8c218753f3044812145cc15f27b3f8bbf8bb21159519e4429da3 3581 lintian_2.5.124.dsc
 66dbc685cf0d4c2c744b9b2cd2c91fb671fdb18355e7caf6d72c595cb698f7f1 1639588 lintian_2.5.124.tar.xz
 441c09561007e21b5b7eaccd3b8966289f314b8cf6d097333f53b0af7e640d4f 1188532 lintian_2.5.124_all.deb
 e94acaf749f4fdf276079a6cb926d5eca4802b687d8ed5d897bf4ac298048e2a 17544 lintian_2.5.124_amd64.buildinfo
Files:
 e8a898dcda353ca236373a71ce9c7f6e 3581 devel optional lintian_2.5.124.dsc
 12b59567d3de49780217feaac5873698 1639588 devel optional lintian_2.5.124.tar.xz
 cf76ae115eb2fe122cccdf1a265c3e69 1188532 devel optional lintian_2.5.124_all.deb
 3e2af73782ad0d7855a82f1c204827dc 17544 devel optional lintian_2.5.124_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlxKy28ACgkQHpU+J9Qx
HliphA/+LRNT/1X/3S4BnZHHlP0zGNhBjpqlR5Ame9tbK6E7PHz2kB550PNSav3i
9D1mD7eD/ksAv6JoZ2T6OpjSm5BHB94qCMnlYeEAI9fttcUr8ezELsgoGuF/8Pvc
0tdKw0gGAag4KAecOcnn8vgViWKOkOK2L8pnENauwvOUqJGjwmrm9kGEyfqCfdca
kPkY9mam5dwGJ5wNkUlb/LDntopZOMfredRY4mWtXEjWHPDL8QJEdYsJMc1wP4Zx
zkfB168C5S0yWbUx428hjRGlsnmSPVif3uklGnWKjIlei7qzuzejri8rNedTUjcb
8wM4cjqgzOeRLXxeD1VXw7+hClzWSOKUa8tp0ezgZJhVL4wICMLgi4kyCqyjBGBx
b+HPOxfThkU/AE+zlHjKkWbU5TBgm/rczsN/Ey7v9duhB077YMpVTux4BHIVbgtc
Ubn8r4uitE3/GXLVc6UvMqph33x/Dgcs1eqQGyEASVP4P7Y161fe73wtV8DnOYU1
d3kyqjTTUktCGnz7OWMrHklZT8IgkDo1NdTil9oNMp/FaQ3r7zUPs2UlfZsgHMO7
Vc3OwKOqf9/cebbuOkDGFfUxQVjdoBCCb0HmRlrio7uM2SFWrPnWbDtk5ngq6xHh
gDfvOUK+SqSUDg/nudrdGFmaqvhOAuaG72P917BLBz9ilxoOoZU=
=vrof
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: