Your message dated Wed, 27 Oct 2021 21:04:27 +0000
with message-id <e1mfq5z-0002uv...@fasolo.debian.org>
and subject line Bug#995355: fixed in node-public-encrypt 4.0.3-1
has caused the Debian Bug report #995355,
regarding node-public-encrypt: autopkgtest regression: deprecation warning on
stderr
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
995355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: node-public-encrypt
Source-Version: 4.0.3-1
Done: Yadd <y...@debian.org>
We believe that the bug you reported is fixed in the latest version of
node-public-encrypt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd <y...@debian.org> (supplier of updated node-public-encrypt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 27 Oct 2021 22:46:16 +0200
Source: node-public-encrypt
Architecture: source
Version: 4.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 995355
Changes:
node-public-encrypt (4.0.3-1) unstable; urgency=medium
.
* Team upload
* Bump debhelper from old 12 to 13.
* Declare compliance with policy 4.6.0
* Add "Rules-Requires-Root: no"
* Add debian/gbp.conf
* Fix filenamemangle
* Fix GitHub tags regex
* Closes: #995355:
+ Use dh-sequence-nodejs auto test & install (allows stderr)
+ New upstream version 4.0.3 (update Buffer() use to avoid warning)
* Drop unneeded dependency version constraints
* Drop nodejs dependency
Checksums-Sha1:
3630fbd9dcf0e998f509c3ae8d5718c7c0921c48 2270 node-public-encrypt_4.0.3-1.dsc
373b698bb6e279ce08670f4d838e87635a3ade62 13833
node-public-encrypt_4.0.3.orig.tar.gz
762727eb391b00e09315c874b290311e75ecaea5 2856
node-public-encrypt_4.0.3-1.debian.tar.xz
Checksums-Sha256:
1ace1dccbccb5ab9c67b9dbc6c241b028a14afed73ccb627e02a33b1861adea3 2270
node-public-encrypt_4.0.3-1.dsc
3e4566df743e68834fa2b754cfffe98939f7d303d31eafd174f0dfd75d11b092 13833
node-public-encrypt_4.0.3.orig.tar.gz
28427859d9f4c2e5dae1bcbb2017b24f91498e02bc9d446ac4f9050c72937dba 2856
node-public-encrypt_4.0.3-1.debian.tar.xz
Files:
96400edb9ab902d2573f1eec62e95946 2270 javascript optional
node-public-encrypt_4.0.3-1.dsc
6a2659edc1129bd2a112a44dcacd6065 13833 javascript optional
node-public-encrypt_4.0.3.orig.tar.gz
48be0379118c0ee5b35787f436cad614 2856 javascript optional
node-public-encrypt_4.0.3-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmF5utoACgkQ9tdMp8mZ
7ulxMA/8DP60Wq1Pqaf9B0ucxWY/qeEb5BsmDbkRF45qX5oZ0B4FB95d4H06Wc6m
R4Cy2/pTqYEkm3/Fq+mnoH3kMWPLHAIprVuh4HhNkkuEHqdxTXpNd02fz+L6nZYc
1xqFAEDYB2iONlvwgsPv+Xh5hI00kkAxCvoxwEIaKHHS8dLvweEfzkLSMFlDwsuS
XmBiGn6nuXHYgd6l7MpsQod2tyUQOIINshYYGe/pSRjrGrxz3ZYv1XaNx5ZVcHaZ
HivYFOD77diaSYvMYvnj45yjlBbdid1opFb6eiMhQIDLVxv0dms2ubw+8pnSbLie
+c8vFtm9DMQmhRoXpM0n1GdRXEb4e7uVT70A9qC7YxbaYDNLLZTX9ZXmY4431ehy
7Ksxc+3UEv+1xHr8JNBhbLCR1zalKWARTSY9T0t9w1ybylZLrtdqb2G3z6Bo8XMq
KnhokezP+sIja+tFOYh+n1pQb8NX3T4Z/MLIE59xoN7gDVL/vICYCvfwnJDpzjcS
eoPxyKVIG1CbCcr8D7WbSaRkte67kMzChAJxQfPdtErjDUQztL5VwEHtlnhcSFbK
3QT7cJPzqB0mjURj6pSxeDP1preuO+fT9UJESRHM1Iiq5IKwOe0Qt/na1tkRCqgx
rTMuRL829r4h5Ydj+XYxXHO9+wK8wPGiXriNo4mb2uoaT80X3X4=
=TD99
-----END PGP SIGNATURE-----
--- End Message ---
