Package: npm2deb
Version: 0.2.5-1
Severity: important
Dear Maintainer,
Using git repo url in debian/watch file creates the following issues.
1. Tags in git repo need not match with npm versions, in such cases npm2deb
fails to get exact version that npm registry holds
2. In some packages even
Package: node-should
Version: 4.0.4+dfsg-1
Severity: wishlist
Dear Maintainer,
Please update node-should to latest version packages like micromatch depends on
it
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64
npm2deb doesn't manipulate any source files as of now. All files
preserves its permissions in its repository.
This could be fixed only after #30 is merged in upstream repo.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
Package: node-iconv-lite
Version: 0.4.13-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Directories `encodings` and `generation` are not included in debian package
archive.
npm2deb skips it as those directories are not mentioned in package.json.
-- System
On 11/13/2016 09:30 PM, Pirate Praveen wrote:
On Saturday 12 November 2016 04:31 PM, Pirate Praveen wrote:
Hi,
Using globally installed grunt is not supported upstream (see
https://github.com/gruntjs/grunt-cli/issues/10). With
https://github.com/gruntjs/grunt-cli/pull/55 patch, I was able to
Package: npm2deb
Version: 0.2.6-1
Severity: normal
Dear Maintainer,
If files section is missing in package.json include everything excluding files
ignored by .npmignore and .gitignore
https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package
bugs like #844333 can be avoided
--
