Package: node-uglify
Version: 2.8.29-3
Severity: minor

        tglase@tglase-nb:~ $ uglifyjs --version

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?

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages node-uglify depends on:
ii  node-yargs  10.0.3-1
ii  nodejs      6.12.0~dfsg-2

Versions of packages node-uglify recommends:
ii  node-source-map  0.6.1+dfsg-1

Versions of packages node-uglify suggests:
pn  node-acorn                 <none>
pn  node-uglify-to-browserify  <none>

-- no debconf information
Pkg-javascript-devel mailing list

Reply via email to