Bug#813587: lintian: vcs-field-not-canonical should emit something conforming to vcs-field-uses-insecure-uri

[Andreas Beckmann <anbe@debian.org>]

Package: lintian
Version: 2.5.40.2
Severity: important

Hi,

I stomped on vcs-field-uses-insecure-uri in src:papi which had

Vcs-Git: git://anonscm.debian.org/collab-maint/papi.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/papi.git;a=summary

vcs-field-not-canonical was not emitted at all.

So what are the URLs I should use now? It would be great if
vcs-field-not-canonical would be emitted in addition to
vcs-field-uses-insecure-uri and report the state-of-the-art URL (at
least for packages hosted on alioth, which is hopefully a majority).

Transformations I did on the Vcs-Browser URL (now in experimental):
s/gitweb/cgit/
s/?p=//
s/;a=summary//
s/http:/https:/

And then I've seen these URLs in recent piuparts commits:

Vcs-Git: https://anonscm.debian.org/cgit/piuparts/piuparts.git

and one commit later:

Vcs-Browser: https://anonscm.debian.org/git/piuparts/piuparts.git
Vcs-Git: https://anonscm.debian.org/git/piuparts/piuparts.git

I didn't know -Git with /cgit/ and -Browser with just /git/ (and no
more /cgit/) - and they actually work :-)
Somehow I like that (at least for git) both URLs can be the same now.

This may require some updates for debcheckout -a to recognize (and
rewrite) the new paths ...


Andreas