Bug#912405: vcswatch cannot analyze repositories maintained on a branch

[Christoph Berg <myon@debian.org>]

Control: reassign -1 gcc-8
Control: retitle -1 Use Vcs-Git: -b gcc-8-debian

Re: Matthias Klose 2018-10-31 <[🔎] 9d472e23-3a14-a992-7467-0b9b7c32bb5c@ubuntu.com>
> Package: qa.debian.org
> 
> as seen on
> https://qa.debian.org/cgi-bin/vcswatch?package=gcc-8
> vcswatch cannot analyze repositories maintained on a branch

Hi,

the default branch in the https://salsa.debian.org/toolchain-team/gcc
repository is "master", which has gcc-9. Packages on other branches
need the "-b" syntax in Vcs-Git:

Vcs-Git: https://salsa.debian.org/toolchain-team/gcc.git -b gcc-8-debian

I manually fixed that now for vcswatch, please add that in
debian/control or it will be overwritten with the next upload.


5.6.26. Version Control System (VCS) fields
-------------------------------------------

Debian source packages are increasingly developed using VCSs. The
purpose of the following fields is to indicate a publicly accessible
repository where the Debian source package is developed.

"Vcs-Browser"
   URL of a web interface for browsing the repository.

"Vcs-<type>"
   The field name identifies the VCS. The field’s value uses the
   version control system’s conventional syntax for describing
   repository locations and should be sufficient to locate the
   repository used for packaging. Ideally, it also locates the branch
   used for development of new versions of the Debian package.

   The following values for <type> are supported, with the
   corresponding VCS indicated in parentheses if it isn’t obvious:

   * Arch

   * Bzr (Bazaar)

   * Cvs (CVS)

   * Darcs

   * Git

   * Hg (Mercurial)

   * 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.

   More than one different VCS may be specified for the same package.

For both fields, any URLs given should use a scheme that provides
confidentiality ("https", for example, rather than "http" or "git") if
the VCS repository supports it.


Christoph