Source: node-public-encrypt Version: 4.0.0-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression
Dear maintainer(s),
With a recent upload of node-public-encrypt the autopkgtest of
node-public-encrypt fails in testing when that autopkgtest is run with
the binary packages of node-public-encrypt from unstable. It passes when
run with only packages from testing. In tabular form:
pass fail
node-public-encrypt from testing 4.0.0-3
all others from testing from testing
I copied some of the output at the bottom of this report. The test
itself passes, but it emits a deprecation warning on stderr. Currently
(I'm considering to change that), the default of autopkgtest is to fail
if there's output on stderr, you can opt-out by adding the allow-stderr
restriction. In my opinion (with release team member and ci-team member
hat on) deprecation warnings should *not* fail autopkgtests, so either
disable deprecation warnings (best solution) if you want to keep
autopkgtest failing on output to stderr or use the allow-stderr restriction.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
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=node-public-encrypt
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-public-encrypt/15629015/log.gz
command1 FAIL stderr: (node:4996) [DEP0005]
DeprecationWarning: Buffer() is deprecated due to security and usability
issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or
Buffer.from() methods instead.
OpenPGP_signature
Description: OpenPGP digital signature
