Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Jonas Smedegaard]

[re-adding bugreport]]

Quoting Pirate Praveen (2016-11-29 06:56:23)
> On 2016, നവംബർ 29 10:05:58 AM IST, Jonas Smedegaard  wrote:
>>Cannot build the new uglifyjs until bug#846076 is resolved.
> 
> This is now fixed.

How? Please elaborate!

Checking now with freshly updated unstable+incoming archives and it 
still fails to satisfy dependencies.


 - Jonas

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

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

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Pirate Praveen]

On 2016, നവംബർ 29 10:05:58 AM IST, Jonas Smedegaard  wrote:

>Cannot build the new uglifyjs until bug#846076 is resolved.

This is now fixed.

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2016-11-29 05:26:39)
> Seems to me that a simple chmod command is the right thing to use.  I 
> do that now, and try release the package - but you are quite welcome 
> to suggest other approaches, or adapt the package yourself.

Cannot build the new uglifyjs until bug#846076 is resolved.

 - Jonas

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

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

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Jonas Smedegaard]

Quoting Pirate Praveen (2016-11-28 11:32:00)
> Control: block -1 by 846076
> 
> On Sun, 27 Nov 2016 14:08:15 +0530 Pirate Praveen 
> wrote:
> > yargs is in NEW and we can upload a new version once it is accepted.
> > 
> Hi Jonas,
> 
> I have prepared the package in git and it is almost ready for upload.
> Can you review and fix these two warnings and upload it?
> 
> W: node-uglify: manpage-has-useless-whatis-entry
> usr/share/man/man1/uglifyjs.1.gz
> W: node-uglify: script-not-executable
> usr/lib/nodejs/uglify-js/bin/extract-props.js
> 
> I'm not too familiar with cdbs, on plain debhelper I could use dh_fixperms

CDBS runs dh_fixperms.  This line in dbian/rules instructs dh_fixparms 
to skip nodejs library path, if that is what you wanted to do:

DEB_FIXPERMS_EXCLUDE_node-uglify = usr/lib/nodejs

I don't follow how dh_fixperms is relevant here, however: I believe 
dh_fixperms can only be told to _skip_ fixing some permissions, not be 
educated to e.g. treat /usr/lib/* same as /usr/bin.

Seems to me that a simple chmod command is the right thing to use.  I do 
that now, and try release the package - but you are quite welcome to 
suggest other approaches, or adapt the package yourself.

Thanks for all your great work!


 - Jonas

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

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

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Pirate Praveen]

Control: block -1 by 846076

On Sun, 27 Nov 2016 14:08:15 +0530 Pirate Praveen 
wrote:
> yargs is in NEW and we can upload a new version once it is accepted.
> 
Hi Jonas,

I have prepared the package in git and it is almost ready for upload.
Can you review and fix these two warnings and upload it?

W: node-uglify: manpage-has-useless-whatis-entry
usr/share/man/man1/uglifyjs.1.gz
W: node-uglify: script-not-executable
usr/lib/nodejs/uglify-js/bin/extract-props.js

I'm not too familiar with cdbs, on plain debhelper I could use dh_fixperms

Thanks
Praveen



signature.asc
Description: OpenPGP digital signature

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Pirate Praveen]

Control: tags -1 pending

On Wed, 23 Nov 2016 09:24:44 +0100 Jonas Smedegaard  wrote:
> I can understand how might have seen the clues as being "right around 
> the corner".

yargs is in NEW and we can upload a new version once it is accepted.



signature.asc
Description: OpenPGP digital signature

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Jonas Smedegaard]

Quoting Pirate Praveen (2016-11-23 08:37:39)
> On Tuesday 22 November 2016 10:53 PM, Jonas Smedegaard wrote:
>> Ah, I understand you now: You present breakage when using code not in 
>> Debian.  Quite confusing - please *always* mention explicitly in 
>> bugports when using non-Debian packages!
>
> Sorry, that was mostly meant a self note (I should have explicitly 
> mentioned it).
>
> I ran uscan, imported the new upstream release, built the package and
> got the error when running it.

Makes sense (now that I what sense to make of it) :-)


>> I only asked whether or not it was related - I did not imply it was 
>> not.
>>
>> I was genuinely confused by your terse writing style.
>>
>> Another point of confusion was that a different topic was used in the 
>> email than in original bugreport topic.  I was unaware (until digging 
>> into archive, when in above latest post you still didn't elaborate 
>> much) that was a wishlist bug, so assumed that your presenting code 
>> failing was to be treated seriously.
>>
>>
>> With the best of intentions,
>
> Sorry about doubting your intentions, but that came as a result of so 
> much comments on -devel about packaging so many tiny node modules. 
> Since you already commented before to start with packaging yargs I 
> thought it would be enough.

I can understand how might have seen the clues as being "right around 
the corner".

Keepup the good work,

 - Jonas

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

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

Bug#836722: [Pkg-javascript-devel] Bug#836722: Bug#836722: needs yargs as a dependency

[Pirate Praveen]

On Tuesday 22 November 2016 10:53 PM, Jonas Smedegaard wrote:
> Ah, I understand you now: You present breakage when using code not in 
> Debian.  Quite confusing - please *always* mention explicitly in 
> bugports when using non-Debian packages!

Sorry, that was mostly meant a self note (I should have explicitly
mentioned it).

I ran uscan, imported the new upstream release, built the package and
got the error when running it.

> I only asked whether or not it was related - I did not imply it was not.
> 
> I was genuinely confused by your terse writing style.
> 
> Another point of confusion was that a different topic was used in the 
> email than in original bugreport topic.  I was unaware (until digging 
> into archive, when in above latest post you still didn't elaborate much) 
> that was a wishlist bug, so assumed that your presenting code failing 
> was to be treated seriously.
> 
> 
> With the best of intentions,

Sorry about doubting your intentions, but that came as a result of so
much comments on -devel about packaging so many tiny node modules. Since
you already commented before to start with packaging yargs I thought it
would be enough.




signature.asc
Description: OpenPGP digital signature