Re: Lintian check for d/upstream files (Was: another source of URLs for DUCK: debian/upstream)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 2013-12-03 11:34, schrieb Andreas Tille:
> Hi Simon,
>
> On Tue, Dec 03, 2013 at 11:26:40AM +0100, Simon Kainz wrote:
>> Currently upstream tags are "pedantic", so please use the
>
> Ahhh, this might have been a misunderstanding of my previous mail.
> I wanted to express that a missing debian/upstream file should only
> be a pedantic warning. A *broken* *existing* debian/upstream file
> (like the one from gfan) should be a real warning.
>
ok, i changed that (commit e50821497b485d62285b59384e201dd9c97aa663):
/tmp$ lintian --include-dir=/home/skainz/lintian-upstream-metadata/
- --profile=debian/metadata gfan_0.5+dfsg-4_amd64.changes
W: gfan source: debian-upstream-file-is-invalid
Now it works like this:
No YAML -> pedantic error only
Invalid YAML -> "normal" warning
YAML with invalid field -> "normal" warning
Invalid fields are all which are _not_ listed on
http://wiki.debian.org/UpstreamMetadata, honoring upper/lowercase issues.
BTW, what happend to http://dep.debian.net/deps/dep12 ? It is
mentioned on http://wiki.debian.org/UpstreamMetadata but the link
seems dead.
> Kind regards
>
> Andreas.
>
Regards,
Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSncQcAAoJEBy08PeN7K/parcP/0l3h93avb+9/nnzhTOxEfuJ
psU5axqMiNLzjnHgbA1lidts/M8EPxWz08Qgf/PMcAMycIoQbtlCyx4RXmGoVHN5
sLwIXU1+VBswkODhPlnNmU7vl4jPRGmcPt9XLuJzc5LQ17TLMxrj9wgahEyS7SYv
h2X4Yrdxxw+Uo69GCRR2ZKz45OvRLuX/qlA6W9pUn7wDJsZxqdU4UFqfQiuhnuYl
zxWMAuDp5mmmfp2cEIpTNMwsmhi/FB+3KZm484+UX3yPYv5tD21bwKFMh0cDSiD6
uRSjfEemlqy5SW9MaepIxaLwwLauwK11nlPvQZYrqvjiQCSNqBvDF99NVb5bJKiU
N22gajFbK2aZN/9D23z+rP2+B6ICqd3khZYlaj2ZC5o2NzvB/gvjhhoFfsB3m3Wc
t5P1yjukLRM1xK27lbVBoyyJl3QPgcdPFhrgHAD+WVqNoCTx10LvNtBxf0marE8n
2hnKLAeLuaa+nI4yQTAIKKpWdUmDrFR1DKTz0555iAeM28ReXs6h68wIG91nmN4F
Ly+slhTTOZkL0tUYmnQ9hhP9DcbfEuBVVZfBDQm9mEWPXWWHebfC42OJssa+w6v3
BQotLP35t3nuGlbTR8LR788eNAzuTo+9jgIKXAvppAHEKE/ckMgAMoeqAwsbK8fQ
onFioIYCdyLRs1GInRMV
=TB0j
-----END PGP SIGNATURE-----
Reply to: