Re: Lintian check for d/upstream files (Was: another source of URLs for DUCK: debian/upstream)
- To: debian-science@lists.debian.org
- Cc: Simon Kainz <simon@familiekainz.at>
- Subject: Re: Lintian check for d/upstream files (Was: another source of URLs for DUCK: debian/upstream)
- From: Andreas Tille <andreas@an3as.eu>
- Date: Thu, 21 Nov 2013 16:15:32 +0100
- Message-id: <[🔎] 20131121151532.GG7618@an3as.eu>
- In-reply-to: <20130829125608.GE27925@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>
Hi Simon,
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
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.
--
http://fam-tille.de
Reply to: