[Pkg-javascript-devel] Bug#884362: Bug#884362: node-uglify: --version output format changed

[Pirate Praveen]

On 12/14/2017 08:31 PM, Thorsten Glaser wrote:
> Package: node-uglify
> Version: 2.8.29-3
> Severity: minor
> 
> 	tglase at tglase-nb:~ $ uglifyjs --version
> 	2.8.29
> 
> This is after an upgrade. Before, it output:
> 	uglify-js 2.8.29
> 
> There was apparently no change to the node-uglify package itself,
> only to some *other* nodejs packages.
> 
> Please explain how this comes to be. This broke our build, which
> uses the output of “uglifyjs --version 2>/dev/null” to determine
> whether 2.x or 3.x was used, to prevent too-new versions (as some
> coworkers use Canonical’s software museum together with npm, in‐
> stead of getting all dependencies via Debian).
> 
> To me, outputting a version number is a simple WriteLn/echo/print{,f}
> command. Why and how can this change if a dependency changes? Which
> dependency was it, and what else does this change affect?

Possibly, update of node-yargs from 6.4.0 to 10.0.3 did this. Note: all
tests of uglifyjs passed with the new node-yargs.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20171214/72b1b37e/attachment.sig>