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

Bug#886334: vcswatch: use the debian-branch specified in gbp.conf for Git



Control: tag -1 moreinfo

On Thu, Jan 04, 2018 at 11:11:30AM -0500, Ryan Kavanagh wrote:
> on vprerex[0] because the HEAD of the git repository specified in Vcs-Git points
> to the prerex packaging instead of the vprerex packaging. However, the file
> debian/gbp.conf[1] in the vprerex sources specifies that the debian-branch is
> vprerex, and this is the branch vcswatch should be checking.

This would require unpacking the source package, something that clearly
is very expensive to do for all packages in the archive, whereas Vcs-*
fields are available in the package index.  Therefore, I'd consider
doing this a very very bad idea.


You should instead follow the Policy¹ and specify the correct branch if
HEAD is not what should be used.  In particular, you should turn your
Vcs-Git field to
    Vcs-Git: https://anonscm.debian.org/git/collab-maint/prerex.git -b vprerex

I've now overrode vcswatch information so this error should go away, but
the next package upload is going to drop the override and take the value
of Vcs-Git again.


Does this cover your bug?


¹ https://www.debian.org/doc/debian-policy/#version-control-system-vcs-fields
| 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.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


Reply to: