Re: Please use Git repository layout as described in Debian Science policy
Dear Andreas
When I run the lintian command with a -I to get informational messages
and on both the binary and source changes files, I still miss a
significant subset of the messages and more precisely these ones:
>> I: toulbar2 source: vcs-field-uses-insecure-uri vcs-git git://anonscm.debian.org/debian-science/packages/toulbar2.git
>> I: toulbar2 source: vcs-field-uses-insecure-uri vcs-browser http://anonscm.debian.org/gitweb/?p=debian-science/packages/toulbar2.git
>> W: toulbar2-dbgsym: debug-file-with-no-debug-symbols usr/lib/debug/.build-id/63/769cbd8ba978f09766bcd677a4c0036429d701.debug
>> I: toulbar2: hardening-no-fortify-functions usr/bin/toulbar2
I feel "naive" again, how can I get these ?
Do informational messages really need to be solved ?
Thomas
Le 04/04/2016 17:21, Andreas Tille a écrit :
> Hi Thomas,
>
> $ lintian toulbar2_0.9.8-1_amd64.changes
> I: toulbar2 source: vcs-field-uses-insecure-uri vcs-git git://anonscm.debian.org/debian-science/packages/toulbar2.git
> I: toulbar2 source: vcs-field-uses-insecure-uri vcs-browser http://anonscm.debian.org/gitweb/?p=debian-science/packages/toulbar2.git
> I: toulbar2 source: quilt-patch-missing-description 010-inhibit-version-generation
> I: toulbar2 source: debian-watch-file-is-missing
> W: toulbar2-dbgsym: debug-file-with-no-debug-symbols usr/lib/debug/.build-id/63/769cbd8ba978f09766bcd677a4c0036429d701.debug
> I: toulbar2: spelling-error-in-binary usr/bin/toulbar2 egde edge
> I: toulbar2: hardening-no-fortify-functions usr/bin/toulbar2
> W: toulbar2: debian-changelog-has-wrong-weekday 2015-03-25 is a Wednesday
> W: toulbar2: new-package-should-close-itp-bug
> E: toulbar2: possible-missing-colon-in-closes Closes Bug#780516
> W: toulbar2: debian-changelog-line-too-long line 4
> W: toulbar2: description-synopsis-starts-with-article
> I: toulbar2: description-synopsis-might-not-be-phrased-properly
> W: toulbar2: binary-without-manpage usr/bin/toulbar2
> I: toulbar2: possible-documentation-but-no-doc-base-registration
>
>
> Could you please fix those lintian issues. For more detailed
> explanation use '-i' option of lintian.
>
Reply to: