Quoting Paolo Greppi (2018-01-10 10:04:57)
> Il 09/01/2018 13:33, Jérémy Lal ha scritto:
>> 2018-01-09 12:53 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com 
>> <mailto:paolo.gre...@libpf.com>>:
>>> Hi, the package node-node-uuid seems broken, this fails: nodejs -e 
>>> "require('uuid');"
>>> Also it triggers lintian error 
>>> node-package-install-in-nodejs-rootdir because it installs 
>>> /usr/lib/nodejs/node-uuid.js.
>>> Next 1.4.0 is quite old and v. 3.1.0. is required for node-yarnpkg.
>>> Finally I have some doubts on the the naming,
> From here:
> https://www.npmjs.com/package/node-uuid
> it says "node-uuid DEPRECATED: Use the uuid package instead."
> It appears node-uuid was a fork, then it got merged back.
> There are two github projects both confusingly called "node-uuid":
> - current: https://github.com/kelektiv/node-uuid is at 3.1.0
> - deprecated: https://github.com/brrofs/node-uuid is at 3.0.0
> The debian node-uuid source package upstream is the "deprecated" fork.
> That's why the tracker says "a new upstream version is available: 
> 3.0.0" and not 3.1.0
> In the light of these facts I am even more convinced that it should be 
> renamed.
> Additionally its upstream should be set to 
> https://github.com/kelektiv/node-uuid

Thanks for the investigations, Paolo and Jérémy.

Yes, node-node-uuid is quite confusing and I am happy that upstream haas 
cleaned up that mess, so we can do so as well (our package was wrongly 
named and partially corrected in release 1.2.0~20110510-2 to at least 
get the binary package correct).

I will look into updating the package, including checking that its 
reverse dependencies work with the newer+renamed node-uuid.

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

Pkg-javascript-devel mailing list

Reply via email to