Re: Lintian check for d/upstream files (Was: another source of URLs for DUCK: debian/upstream)
- To: Andreas Tille <andreas@an3as.eu>, debian-science@lists.debian.org
- Subject: Re: Lintian check for d/upstream files (Was: another source of URLs for DUCK: debian/upstream)
- From: Simon Kainz <simon@familiekainz.at>
- Date: Mon, 02 Dec 2013 14:45:30 +0100
- Message-id: <[🔎] 529C8EFA.5030704@familiekainz.at>
- In-reply-to: <20131121151532.GG7618@an3as.eu>
- References: <1367285991.11756.46.camel@chianamo> <518CBE9C.3090307@familiekainz.at> <20130511020327.GC15438@falafel.plessy.net> <52173274.3010804@familiekainz.at> <20130823101010.GD11037@an3as.eu> <52174555.2060305@familiekainz.at> <20130823113956.GF11037@an3as.eu> <5218CCB1.4020400@familiekainz.at> <20130829125608.GE27925@an3as.eu> <20131121151532.GG7618@an3as.eu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 2013-11-21 16:15, schrieb Andreas Tille:
> Hi Simon,
Hello!
>
> On Thu, Aug 29, 2013 at 02:56:08PM +0200, Andreas Tille wrote:
>> Hi Simon,
>>
>> On Sat, Aug 24, 2013 at 05:09:37PM +0200, Simon Kainz wrote:
>>> Am 2013-08-23 13:39, schrieb Andreas Tille:
>>>>> Otherwise I'd gladly help working on a lintian module.
>>>> I have never written any lintian check so some kind of
>>>> kickstart would be great.
>>>>
>>> Hi!
>>>
>>> I wrote a _very basic_ lintian check, available here:
>>>
>>> http://familiekainz.at/deb/lintian/metadata.tgz
>>
>> That's very cool! Thanks for your effort!
>
> I have found some issue which is not found by the lintian check.
> Please have a look at
>
> git://git.debian.org/git/debian-med/r-cran-ggplot2.git
Sorry, i didn't find d/upstream in the repo specified. Are your sure
this is the correct repo?
I simple git clone'd the url above.
Bye,
>
> which contains an d/upstream file with the line
>
>
> Cite-as:<a
> href="http://home.imf.au.dk/jensen/software/gfan/gfan.html">Gfan, a
> software system for Gröbner fans and tropical varieties</a>
>
>
> This is wrong YAML syntax since the separator between key and value
> is
>
> ": "
>
> and the space is lacking in the line above. I might add that in
> the beginning the yaml files were parsed using Perl and later I did
> the parsing with Python and when doing so I detected several
> instances of this syntax issue. So I assume that the Perl YAML
> implementation is not as strict as it should be here - which leads
> to the consequence that lintian will not detect it.
>
> I would be very happy if you could inject this check into the
> lintian test.
>
> Kind regards
>
> Andreas.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSnI7nAAoJEBy08PeN7K/pPzwP/3n6fHv5h/+2yq6XxKW7PaXx
Lc7W2RDkOe9Vtf2ifsLxAKXTdFASK4QYOm59jm5qovy6yaf47DNZE3RjW069rhdQ
p8ZSCOZR08GJG+NFEnLdnye+1pjyLhA7j7FkdVYwntVj2Yh3OuN8+RobUCYHpiVx
7RQ+FpAPrZaPWkGTjN6NnuiaCVmr9QC9K1cjesSH3icBTa0jty1b69oFAY54eRVC
JZRX4bct3vxQGqRfnrTUAK8fwMzxZKSUMbnZIUTYkvBbCQ42QKQpxCe7kmtsBPRO
MPaBkkTwLb2il1XCupYwPnO5Uu8caGSZD1iB6qXPlr7C/poZ7I5JOpsYFNoeBWcB
UYh2N1BFVlGSm29A+Dq9s4md9wfmr70+ifKnp3zIjfONPgc/xAdHPxMgjuZShwHJ
gos5ZH7Ur+Q9iHy5voDBqyDIlhtXPefwMC9bdN6KHdFjtRRAM0ViLqtRrbQ5pZ/x
UssfjtIQwUeRqjPzwwaPwCrKlsY7XINsMOMUQ/LNprWBShDQ5FWaLm6coiggzTjv
IxcmrK4rWeFEHYt2HxWejzv1cOH0VrQj+r9Trtx4d5LPD/HiL68fIbnEkdBYAhR2
HavE/1VP+LtKp5Vaw7B7CNXyW9uLQIDiRYYz1zRSWR/ijdJDwJCritn3u72iqZ1T
cymfpNc/rn3L1Ecs01co
=MiCO
-----END PGP SIGNATURE-----
Reply to: