[Pkg-javascript-devel] Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[Paul Gevers]

Source: node-node-sass
Version: 4.14.1-2
Severity: serious
X-Debbugs-CC: debian-ci at lists.debian.org, nodejs at packages.debian.org
Tags: sid bullseye
User: debian-ci at lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs src:node-grunt-sass

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-grunt-sass fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

                       pass            fail
nodejs                 from testing    12.18.0~dfsg-3
node-grunt-sass        from testing    3.1.0-2
all others             from testing    from testing

I copied some of the output at the bottom of this report. Similar to the
issues with node-iconv and node-expat, node-node-sass seems to be
missing a versioned relation with nodejs. Because of the missing
relation, nodejs can be upgraded without the rebuild node-node-sass from
unstable.

Currently this regression is blocking the migration of nodejs to testing
[1]. Of course, nodejs shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in nodejs was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from nodejs should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-grunt-sass/6051450/log.gz

autopkgtest [01:12:40]: test pkg-js-autopkgtest: [-----------------------
Using package.json
Node module name is grunt-sass
# Copy test files
Looking at /usr/lib/nodejs/grunt-sass
Looking at /usr/lib/*/nodejs/grunt-sass
Looking at /usr/share/nodejs/grunt-sass
Found /usr/share/nodejs/grunt-sass
Linking /usr/share/nodejs/grunt-sass/package.json
Linking /usr/share/nodejs/grunt-sass/tasks
Launch debian/tests/pkg-js/test with sh -ex
+ grunt sass nodeunit
Loading "gruntfile.js" tasks...ERROR
>> Error: Missing binding
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
>> Node Sass could not find a binding for your current environment:
Linux 64-bit with Node.js 12.x
>>
>> Found bindings for the following environments:
>>   - Linux 64-bit with Node.js 10.x
>>
>> This usually happens because your environment has changed since
running `npm install`.
>> Run `npm rebuild node-sass` to download the binding for your current
environment.
Warning: Task "sass" not found. Use --force to continue.

Aborted due to warnings.
autopkgtest [01:12:41]: test pkg-js-autopkgtest: -----------------------]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20200626/434ac9da/attachment-0001.sig>