Your message dated Thu, 4 Jan 2018 11:54:23 -0500
with message-id <20180104165423.y6r7orikuutd5...@zeta.ryanak.ca>
and subject line Re: Bug#886334: vcswatch: use the debian-branch specified in
gbp.conf for Git
has caused the Debian Bug report #886334,
regarding vcswatch: use the debian-branch specified in gbp.conf for Git
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 ow...@bugs.debian.org
immediately.)
--
886334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
For git repositories, vcswatch should check the configuration file
debian/gbp.conf (if it exists) in the source package to determine what branch to
use as its packaging branch. For example, vcswatch reports
Error: changelog package prerex does not match source vprerex
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.
By checking a specific branch instead of HEAD, I suspect this would also fix
bug #784907 [2].
[0] https://qa.debian.org/cgi-bin/vcswatch?package=vprerex
[1]
https://anonscm.debian.org/cgit/collab-maint/prerex.git/tree/debian/gbp.conf?h=vprerex
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784907
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
|_)|_/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F
| \| \ https://ryanak.ca/ | BD95 8F7B F8FC 4A11 C97A
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Mattia,
On Thu, Jan 04, 2018 at 05:36:42PM +0100, Mattia Rizzolo wrote:
> You should instead follow the Policy¹ and specify the correct branch if HEAD
> is not what should be used.
Aha, I missed that paragraph of policy. Thanks for pointing it out to me!
> Does this cover your bug?
Yes it does, I'll close it seeing that the Vcs-Git field already provides a
suitable alternative to checking debian-branch in debian/gbp.conf. Sorry for the
noise!
Best wishes,
Ryan
--
|_)|_/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F
| \| \ https://ryanak.ca/ | BD95 8F7B F8FC 4A11 C97A
signature.asc
Description: PGP signature
--- End Message ---
