Your message dated Wed, 08 May 2019 10:33:18 +0000
with message-id <e1hojt0-0006fp...@fasolo.debian.org>
and subject line Bug#928645: fixed in node-lockfile 1.0.4-2
has caused the Debian Bug report #928645,
regarding RFI: replacement of touch module with fs
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.)
--
928645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-lockfile
Version: 1.0.4
Severity: normal
Hi,
This is mostly about trying to determine the reason for the change.
I noticed that in patch `remove-touch.patch`, the requirement for `touch`
module is worked around by the `fs` module.
Is it because by the minor change you were able to avoid an additional
package dependency? Or is there any other reason, like `touch` being
buggy/unmaintained ?
I have a build failure with test `staleness-sync-test` in
tests/basic.js, which I'm encountering only on slow arm32 hardware.
Your change in the above patch looks good enough to me (and my test
failure is something I think to do with the slowness of the hardware),
but I still wanted to check if there is any known reason otherwise, for
you to go this route and deviate from upstream ?
Thanks,
Ritesh
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: node-lockfile
Source-Version: 1.0.4-2
We believe that the bug you reported is fixed in the latest version of
node-lockfile, 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 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard <y...@debian.org> (supplier of updated node-lockfile 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, 08 May 2019 11:41:01 +0200
Source: node-lockfile
Architecture: source
Version: 1.0.4-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Xavier Guimard <y...@debian.org>
Closes: 928645
Changes:
node-lockfile (1.0.4-2) experimental; urgency=medium
.
* Team upload
* Switch tests to pkg-js-tools and embed "touch" for tests (Closes: #928645)
* Declare compliance with policy 4.3.0
* Add upstream/metadata
Checksums-Sha1:
57258a1a86574aeb001729e91ce36a90697cd82e 2073 node-lockfile_1.0.4-2.dsc
9a1563b4804214696558a128e14ce699463cbea6 4992
node-lockfile_1.0.4-2.debian.tar.xz
Checksums-Sha256:
041739039d1a4b6362ac892c5caf7dc0bf1992f756c008b7905285310d0dc19a 2073
node-lockfile_1.0.4-2.dsc
cb42c309154f686aa3198aaa0b9413ccfc2f25572dffcfe0d6d6eaeca9348ae3 4992
node-lockfile_1.0.4-2.debian.tar.xz
Files:
6efdf7b93d0a4f899063cd009d3fb136 2073 javascript optional
node-lockfile_1.0.4-2.dsc
0b5b7693cc37135b55a79d2dd38bc420 4992 javascript optional
node-lockfile_1.0.4-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlzSpS0ACgkQ9tdMp8mZ
7ulXIQ//S5mpI2cY7+tGri+wF1vaj1/y1D9pLYsXRs+GtMP9SWiXwKkFviBEkfO8
RDfoOYN/DsXFo+Wym/UHEZdOOxC9LWZsqnNs6ufcMJq3E21s0ChhzqOno3ZTGnQ1
bgCOikWPEVR+83wvoSJIk53mLudc0C3KDI0+DH3IRZfnTjUeJHHfm9LlpFMeQoUb
S6g1PtEgjqhKdKjnRrc2R/q+lZvrOy/vEwZBqQifsMwEJkD9rtNqa3zQY6wKH91S
rp8Q4Cz4CxiAv69ce/DmrYEcalK85s52Ov6kVXmRHBe3+VeTroc25Sl7+IKQ4uYv
n0hWCjJ4hBt2Ig10X66LQfpD1LqjN3Y9t7PWaPxi0eWyo1gwwWyDN2jotWS0vpmG
x6fI42dWmWTYB+jXmPkzPdPH+FldTVivVG1fu8hhAbstTpUaDFkjdhO568F1HsTC
rZoYUm9X4/dlnL8QqylLwJjzON5vloVlvbtw1+Wv56bGYE7BXFHjs0Y7pAaqJByw
quWVGX0ff7h57gcIWGPQnBpmorr+DsCAaWi91MwDAAtB/3mdRYwhFxfSt/YjcImm
hiOZSl+VYfkCaMLL7zCgioCFQvom0RLCWw2SL/v+fz4sWa4Pg3186oY7Sw0zfoZP
SDaDBO6Hv+vvbFNi3wOXyXRqvzAaum/66HQUU5mMP5G9LPwd9JM=
=INZW
-----END PGP SIGNATURE-----
--- End Message ---
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
