-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 package: lintian version: 2.5.22
Was this fixed in 2.5.22.1? I don't see it mentioned in changelog though. - -------- Original Message -------- Subject: Re: json files in source for ruby-twitter Resent-Date: Fri, 2 May 2014 08:45:43 +0000 (UTC) Resent-From: debian-r...@lists.debian.org Date: Fri, 2 May 2014 10:45:26 +0200 From: Christian Hofstaedtler <z...@debian.org> To: Pirate Praveen <prav...@debian.org> CC: debian-ruby <debian-r...@lists.debian.org> * Pirate Praveen <prav...@debian.org> [140502 10:33]: > There are many json files used for testing and lintian gives following > errors. > > ruby-twitter: source-contains-prebuilt-javascript-object > spec/fixtures/configuration.json means line length is about 1318 characters > ruby-twitter: source-is-missing spec/fixtures/configuration.json > > I have overridden them but I wanted to ask here if it is okay before I > upload. Please also tell the lintian about these; the files are data, not code, and can be easily edited if needed - I can't see how "source-is-missing" can apply to those json files. -ch - -- ,''`. Christian Hofstaedtler <z...@debian.org> : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJTY2pmAAoJEM4fnGdFEsIqpLoP+wS3jgtlBeYRtlCmgbnZFTts bVdB0rfztqY2E9xfS9i3ujQZpBLJqtvX7s1AEjW+B94BkNwikKAMTB2QVcBpq9Yv pTnX2TA71v/hWqZ9guoeGMpZ6hJypA9x2P9Aw3Qj8SpWsCmFCum2TTqrIGUQUzZu borjbLZ6l8INa45OSfok2tXNNeAEtcCuKdRYFOk7qL9ZH1G9GqPgQTZOvZnvbGXN VEJdd86g93GkGTWe56dA/oALQgPvjDGuPH/rAX0AKwFI6IEZOnrI0G3+bbqYaAU3 Flt8Gz7QMZRrbFwU4WGcrEIlCjnLjk29oWOR9bC1SyEA1X772Spqxs+SUNhIgLEG ELY1hxFpW7hTlaMlhO9bDp4W3f6Q2qx3jGynxHc9gPtPT9FODL0JqFdZpT6Uhmj/ rnC4Pu1hqz35ic/K+TqcJcwX64xRKfvQlFEiD9IqStqOHNnioKZa1UOZZLb+q2Gv tAsgY0PNmWx/tF2OYkESuJPL0pAKVG6iu1WOtvDvjxc3uF+4ntqxlpbNXeaEj6P0 HUMwtWX/64jUIZHf358Qf9FKontjq50e7HjterLmch0QbSKRP90BS+v8l1yKezxA 1oUNe2WafcTf+gEAIxYE9aycZSY0ksULJvpBJdUtAF1yJCOWovjoZ2TnrQcnD6eA ud77VG69h3/oCkyz59Tk =rL1h -----END PGP SIGNATURE-----
