[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#810000: lintian: False positive source-is-missing for cryptocat/otr.js



On Wed, 2016-01-06 at 14:02 +0100, Ximin Luo wrote:

> Grunt is going to take a while to package, due to the wider JS
> ecosystem being generally stupid, over-bloated and self-important far
> beyond its worth.

I spoke to someone on IRC who was working on it the other day, it
sounded like they were close, just packaging another 1KB JS file.

> (For example, I very much doubt someone is going to maintain a debian
> package for a JS npm package whose only purpose and ability is to
> check if number-is-nan. Also, lol @ the meow -> indent-string ->
> repeating -> meow cyclic dependency.)

Uh, #797455

> Could we just make an exception at this time for this OTR.js embedded
> copy? We can add very loud notices to debian/TODO and debian/rules
> saying that this should be fixed whenever otr.js is packaged
> properly, hopefully once we convince upstream to move away from
> Grunt.

I don't think the DFSG has exceptions :)

> [1] Seriously, WHO THE FUCK WRITES THIS SHIT???

It is a different world from a different age, completely disconnected
with the world of Linux distros. Unfortunately those people are the new
Open Source ecosystem and abhor the distros and how we do things.

> Also, in terms of lintian and this bug report, *it is still a bug in
> lintian*. It would still give a false positive even if otr.js is
> packaged correctly. This is also triggered by some other JS stuff I
> have been packaging.

Agreed, but it is a bit much to expect lintian to be false-positive free.

> I would suggest that lintian be amended, so that if the file is >20-
> 50 lines, and there are only 1-2 of these "long lines", then no
> error/warning is emitted.

IIRC it already has been toned down.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: