Debian Bug report logs - #840170
some modules has package.yaml instead of package.json

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: some modules has package.yaml instead of package.json

Date: Sun, 9 Oct 2016 11:32:47 +0530

[Message part 1 (text/plain, inline)]

package: npm2deb
version: 0.2.5-1
severity: grave
justification: breaks package build

So npm2deb should use the correct file in debian/install

dh_install: Cannot find (any matches for) "package.json" (tried in "."
and "debian/tmp")
dh_install: node-jju missing files: package.json
dh_install: missing files, aborting

[signature.asc (application/pgp-signature, attachment)]

Message #10 received at [email protected] (full text, mbox, reply):

From: Chris Lamb <[email protected]>

To: [email protected]

Cc: Pirate Praveen <[email protected]>

Subject: Re: some modules has package.yaml instead of package.json

Date: Sun, 09 Oct 2016 12:13:10 +0100

Hi,

> some modules has package.yaml instead of package.json

Could you provide an existing package name and/or simple testcase for this?


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      [email protected] / chris-lamb.co.uk
       `-

Message #15 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: Chris Lamb <[email protected]>, [email protected]

Subject: Re: some modules has package.yaml instead of package.json

Date: Sun, 9 Oct 2016 17:39:14 +0530

[Message part 1 (text/plain, inline)]

On ഞായര്‍ 09 ഒക്ടോബര്‍ 2016 04:43 വൈകു, Chris Lamb wrote:
> Hi,
> 
>> some modules has package.yaml instead of package.json
> 
> Could you provide an existing package name and/or simple testcase for this?
> 

node-jju package has package.yaml.

Similarly colors.js does not have a package.json file, but it has
bower.json file.

> Regards,
> 

[signature.asc (application/pgp-signature, attachment)]

Message #20 received at [email protected] (full text, mbox, reply):

From: Chris Lamb <[email protected]>

To: Pirate Praveen <[email protected]>, [email protected]

Subject: Re: some modules has package.yaml instead of package.json

Date: Sun, 09 Oct 2016 13:29:09 +0100

Pirate Praveen wrote:

> node-jju package has package.yaml.

Can't seem to find this package in the archive!


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      [email protected] / chris-lamb.co.uk
       `-

Message #25 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: Chris Lamb <[email protected]>, [email protected]

Subject: Re: some modules has package.yaml instead of package.json

Date: Sun, 9 Oct 2016 18:02:33 +0530

[Message part 1 (text/plain, inline)]

On ഞായര്‍ 09 ഒക്ടോബര്‍ 2016 05:59 വൈകു, Chris Lamb wrote:
> Pirate Praveen wrote:
> 
>> node-jju package has package.yaml.
> 
> Can't seem to find this package in the archive!

This was accepted only a few hours back. See
https://anonscm.debian.org/cgit/pkg-javascript/node-jju.git

[signature.asc (application/pgp-signature, attachment)]

Message #30 received at [email protected] (full text, mbox, reply):

From: [email protected]

To: [email protected]

Subject: Re: some modules has package.yaml instead of package.json

Date: Sat, 29 Oct 2016 13:13:51 +0000

[Message part 1 (text/plain, inline)]

All npm modules should have a package.json.

The issue is npm2deb retrieves module source from git repo instead of npm registry.

This will be fixed with #842465 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842465)

[Message part 2 (text/html, inline)]

Message #35 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: [email protected]

Cc: Shanavas <[email protected]>

Subject: Re: some modules has package.yaml instead of package.json

Date: Sat, 29 Oct 2016 19:58:02 +0530

[Message part 1 (text/plain, inline)]

On Sat, 29 Oct 2016 13:13:51 +0000 [email protected] wrote:
> All npm modules should have a package.json.
> 
> The issue is npm2deb retrieves module source from git repo instead of npm registry.
> 
> This will be fixed with #842465 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842465)

But npm tarballs does not always contains tests. We should run tests to
be able to update its dependencies (See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840213).

So npm dist tarballs should be used only when tags are missing in the
repo and not the default. Usually the upstream authors are very
responsive to requests for updating tags page.

[signature.asc (application/pgp-signature, attachment)]

Message #40 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: [email protected]

Subject: Re: some modules has package.yaml instead of package.json

Date: Mon, 31 Oct 2016 11:16:56 +0530

[Message part 1 (text/plain, inline)]

Control: severity -1 important

On Sun, 9 Oct 2016 11:32:47 +0530 Pirate Praveen <[email protected]> wrote:
> severity: grave
> justification: breaks package build

reducing severity to important, this does not have to block the release
as it happens only in a few packages and which can easily be fixed.

[signature.asc (application/pgp-signature, attachment)]

Message #47 received at [email protected] (full text, mbox, reply):

From: Jonas Smedegaard <[email protected]>

To: Pirate Praveen <[email protected]>, [email protected]

Subject: Re: Bug#840170: some modules has package.yaml instead of package.json

Date: Mon, 31 Oct 2016 10:37:31 +0100

[Message part 1 (text/plain, inline)]

Quoting Pirate Praveen (2016-10-31 06:46:56)
> Control: severity -1 important
> 
> On Sun, 9 Oct 2016 11:32:47 +0530 Pirate Praveen <[email protected]> wrote:
> > severity: grave
> > justification: breaks package build
> 
> reducing severity to important, this does not have to block the release
> as it happens only in a few packages and which can easily be fixed.

The tag is "severity", not "complexity": If the bug cause failure to 
build packages the it is of high severity, no matter how hard or easy it 
will be to fix.

If release happened before this bug was fixed, then it _is_ a blocker!


 - Jonas

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

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

[signature.asc (application/pgp-signature, inline)]

Message #52 received at [email protected] (full text, mbox, reply):

From: Pirate Praveen <[email protected]>

To: Jonas Smedegaard <[email protected]>, [email protected]

Subject: Re: [Pkg-javascript-devel] Bug#840170: some modules has package.yaml instead of package.json

Date: Mon, 31 Oct 2016 15:09:58 +0530

[Message part 1 (text/plain, inline)]

On Monday 31 October 2016 03:07 PM, Jonas Smedegaard wrote:
>> reducing severity to important, this does not have to block the release
>> as it happens only in a few packages and which can easily be fixed.
> 
> The tag is "severity", not "complexity": If the bug cause failure to 
> build packages the it is of high severity, no matter how hard or easy it 
> will be to fix.
> 
> If release happened before this bug was fixed, then it _is_ a blocker!
> 

Fix is to add package.yaml to debian/install. This bug does not make any
current packages to fail. It only affects packages that are newly
created and debian/install is not corrected.

[signature.asc (application/pgp-signature, attachment)]

Message #57 received at [email protected] (full text, mbox, reply):

From: Jonas Smedegaard <[email protected]>

To: Pirate Praveen <[email protected]>, [email protected]

Subject: Re: [Pkg-javascript-devel] Bug#840170: some modules has package.yaml instead of package.json

Date: Mon, 31 Oct 2016 11:16:32 +0100

[Message part 1 (text/plain, inline)]

Quoting Pirate Praveen (2016-10-31 10:39:58)
> On Monday 31 October 2016 03:07 PM, Jonas Smedegaard wrote:
> >> reducing severity to important, this does not have to block the release
> >> as it happens only in a few packages and which can easily be fixed.
> > 
> > The tag is "severity", not "complexity": If the bug cause failure to 
> > build packages the it is of high severity, no matter how hard or easy it 
> > will be to fix.
> > 
> > If release happened before this bug was fixed, then it _is_ a blocker!
> > 
> 
> Fix is to add package.yaml to debian/install. This bug does not make any
> current packages to fail. It only affects packages that are newly
> created and debian/install is not corrected.

Ah - makes sense, then.  I simply misunderstood your previous comment.


 - Jonas

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

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

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.