Bug#863729: marked as done (debian-policy: please use the cgit link in Vcs-Browser)
Your message dated Tue, 30 May 2017 18:50:22 +0200
with message-id <878tlee1bl.fsf@lant.ki.iif.hu>
and subject line Re: Bug#863729: debian-policy: please use the cgit link in Vcs-Browser
has caused the Debian Bug report #863729,
regarding debian-policy: please use the cgit link in Vcs-Browser
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.)
--
863729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863729
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Severity: minor
Dear Maintainer,
Your control file specifies
https://anonscm.debian.org/git/dbnpolicy/policy.git
as Vcs-Browser, but the gitweb interface gives "Bad object id:" messages
when clicking into the shortlog section. Please switch to
https://anonscm.debian.org/cgit/dbnpolicy/policy.git
if possible.
--
Thanks,
Feri.
--- End Message ---
--- Begin Message ---
Version: 4.0.0.0
Mattia Rizzolo <mattia@debian.org> writes:
> On Tue, May 30, 2017 at 04:22:06PM +0200, Ferenc Wágner wrote:
>
>> Your control file specifies
>> https://anonscm.debian.org/git/dbnpolicy/policy.git
>> as Vcs-Browser, but the gitweb interface gives "Bad object id:" messages
>> when clicking into the shortlog section.
>
> How is gitweb involved in any way here and where do you see any
> "shortlog" section in
> https://anonscm.debian.org/git/dbnpolicy/policy.git ?
>
> Which link are you clicking on?
The (Browse) link on https://tracker.debian.org/pkg/debian-policy. Now
I notice it isn't the one in the control file. I assumed that was the
result of some redirection, but that's not the case. You indeed fixed
this in the experimental version (commit 670b8419), it's just the
package tracker still carrying the old link from the unstable control
file.
--
Sorry for the noise,
Feri.
--- End Message ---
Reply to: