Bug#884870: marked as done (lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree)
Your message dated Wed, 20 Dec 2017 18:26:42 -0500
with message-id <CAAajCMbSx6TRP_eOqt1VsGJ6biO_dSOJAQ8pCokW5mK3M7QJ7g@mail.gmail.com>
and subject line Re: Bug#884870: lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree
has caused the Debian Bug report #884870,
regarding lintian: vcs-field-has-unexpected-spaces and vcswatch don't agree
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.)
--
884870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884870
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: lintian
Version: 2.5.65
I changed webkit2gtk's Vcs-Git field from
Vcs-Git: https://anonscm.debian.org/git/pkg-webkit/webkit.git
to
Vcs-Git: https://anonscm.debian.org/git/pkg-webkit/webkit.git -b wk2/unstable
in order to satisfy
https://qa.debian.org/cgi-bin/vcswatch?package=webkit2gtk
which complained that it couldn't find the current debian/changelog in
HEAD. (Maybe it's time to change HEAD, but this bug is also a problem
for experimental and Stable Update branches.)
Now, I think (lintian's website is recovering from a typo) that this
now causes lintian to emit vcs-field-has-unexpected-spaces
I think the " -b BRANCHNAME" suffix should be considered valid syntax
for Vcs-Git.
Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
On Wed, Dec 20, 2017 at 3:23 PM, Chris Lamb <lamby@debian.org> wrote:
> Something else must be going on as this is indeed supported. Here is the
> code in question:
Never mind. Maybe I had a typo locally since I can't reproduce it now.
Thanks,
Jeremy Bicha
--- End Message ---
Reply to: