Your message dated Sun, 27 Dec 2020 06:48:26 +0000
with message-id <e1ktpqs-0006nx...@fasolo.debian.org>
and subject line Bug#978373: fixed in node-deep-eql 4.0.0-3
has caused the Debian Bug report #978373,
regarding node-deep-eql: FTBFS: Error: module type-detect in /<<PKGBUILDDIR>>
not found
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.)
--
978373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-deep-eql
Version: 4.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build
> browserify-lite ./index.js --standalone deepEqual --outfile deep-eql.tmp.js
> /usr/share/nodejs/browserify-lite/cli.js:29
> if (err) throw err;
> ^
>
> Error: module type-detect in /<<PKGBUILDDIR>> not found
> at trySearchPath (/usr/share/nodejs/browserify-lite/index.js:269:32)
> at /usr/share/nodejs/browserify-lite/index.js:274:7
> at /usr/share/nodejs/browserify-lite/index.js:294:21
> at FSReqCallback.oncomplete (fs.js:168:21)
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/node-deep-eql_4.0.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-deep-eql
Source-Version: 4.0.0-3
Done: Xavier Guimard <y...@debian.org>
We believe that the bug you reported is fixed in the latest version of
node-deep-eql, 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 978...@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-deep-eql 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: Sun, 27 Dec 2020 07:26:33 +0100
Source: node-deep-eql
Architecture: source
Version: 4.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Xavier Guimard <y...@debian.org>
Closes: 978373
Changes:
node-deep-eql (4.0.0-3) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Update standards version to 4.4.1, no changes needed.
* Set debhelper-compat version in Build-Depends.
* Remove obsolete fields Name, Contact from debian/upstream/metadata.
.
[ Xavier Guimard ]
* Set upstream metadata fields: Bug-Submit.
* Update standards version to 4.5.0, no changes needed.
* Bump debhelper compatibility level to 13
* Declare compliance with policy 4.5.1
* Add "Rules-Requires-Root: no"
* Modernize debian/watch
* Use dh-sequence-nodejs
* Fix build (Closes: #978373)
Checksums-Sha1:
916fa3a1d90fe74b0431744b08a92166e7fad859 2177 node-deep-eql_4.0.0-3.dsc
958057913c50069b884ea34f1ccfc0b30e62ad1d 4508
node-deep-eql_4.0.0-3.debian.tar.xz
Checksums-Sha256:
f353dbc1987e5d290d0f8cf668685601b616f3405d3723e1e691f6f5e7338368 2177
node-deep-eql_4.0.0-3.dsc
59edfe89fc05503339c43f9c4764bf9e34deb6fc91b3a362c6ebad4308e1543c 4508
node-deep-eql_4.0.0-3.debian.tar.xz
Files:
b8c88de78f91f46beb935ae4601777d9 2177 javascript optional
node-deep-eql_4.0.0-3.dsc
436d7879c26bd2e5b6a3ee093e284079 4508 javascript optional
node-deep-eql_4.0.0-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/oKZEACgkQ9tdMp8mZ
7um+MA//cYJlkPrB5d46jnomzb0/OgkDxkaRVWV/8r7wHP9O5QZepZ9ydVPQTiaj
B3uMzd44jYRJKoH9D7McRzK3Vnkud8ftVCNiV04IudSs7dXBOMSBqvyjLS6hcBJO
diQRf1RRx1eC2w1r/tBkzuFRs0b+jcLskBQJXWPJty1i8r0FYjUWZ3aOHeIS7ei6
ypTJKlER9JApprhYQRxOQojH65IQptMJc637+CL/7P5rvgOQWqDi0qfaVZ/0zkEf
cv7z5hkja74Y44BJnRHHUykrs9dvY6P9CNMd0mS3MjVzR8rJXkZm+9CagBOp4s9N
qJ18pNn+RB/O09AWMLD4RXwt+xCIUqAHro1QglUXbgqRoops0+fNGfK0rvDLOEWU
YAVD9493PjjuAYOVZzi8eM5sSJOm9SnD/xk5zxNFIkNzi41MHZhX4BZdkvaFJ2C6
lgKYi/ZouqYlU7RyLVtATzlFo6VQ5Sh2GY5ePYCVuB6wptUdxDDnIt1N6xJO3CsU
kp2ojbif/LR7DXwRDO7Xkp7O4/68lUxARM+unrbFpqeImqIAjJvLIEfW4hq/xfGW
UbAcbR+9RYoKkVpzbQ8niyiKLh0Dxj3GKOZohLrTI0nbu6GxukuMX3VjvZlmkRfx
fEEARo52xLvhpgmug0NKtq1YEYrJ+fhbpz3IPRahDBejxACUd08=
=PG6j
-----END PGP SIGNATURE-----
--- End Message ---
