Your message dated Fri, 27 May 2022 21:36:43 +0000
with message-id <e1nuhdt-0002lj...@fasolo.debian.org>
and subject line Bug#1011885: fixed in node-define-lazy-prop 3.0.0-5
has caused the Debian Bug report #1011885,
regarding node-define-lazy-prop: FTBFS: ReferenceError: require is not defined
in ES module scope, you can use import instead
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.)
--
1011885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-define-lazy-prop
Version: 3.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mjs2cjs -a
> Not found
> xo not found in nodejs directories
> Not found
> tsd not found in nodejs directories
> Not found
> ava not found in nodejs directories
> [36m
> [1m./index.js[22m → [1m./dhnodejsBundle.cjs[22m...[39m
> [1m[33m(!) Entry module "index.js" is implicitly using "default" export
> mode, which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "index.js" to use named exports
> only.[39m[22m
> [90mhttps://rollupjs.org/guide/en/#outputexports[39m
> [1mindex.js[22m
> [32mcreated [1m./dhnodejsBundle.cjs[22m in [1m20ms[22m[39m
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/define-lazy-prop
> /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> file:///<<PKGBUILDDIR>>/test.js:1
> const test = require('tape');
> ^
>
> ReferenceError: require is not defined in ES module scope, you can use import
> instead
> This file is being treated as an ES module because it has a '.js' file
> extension and '/<<PKGBUILDDIR>>/package.json' contains "type": "module". To
> treat it as a CommonJS script, rename it to use the '.cjs' file extension.
> at file:///<<PKGBUILDDIR>>/test.js:1:14
> at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
> at async Promise.all (index 0)
> at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
> at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/node-define-lazy-prop_3.0.0-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-define-lazy-prop
Source-Version: 3.0.0-5
Done: Yadd <y...@debian.org>
We believe that the bug you reported is fixed in the latest version of
node-define-lazy-prop, 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 1011...@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-define-lazy-prop 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: Fri, 27 May 2022 23:15:23 +0200
Source: node-define-lazy-prop
Built-For-Profiles: nocheck
Architecture: source
Version: 3.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 1011885
Changes:
node-define-lazy-prop (3.0.0-5) unstable; urgency=medium
.
* Team upload
* Declare compliance with policy 4.6.1
* Drop patch, switch test to ava (Closes: #1011885)
Checksums-Sha1:
55e6408d575bf912edd0c1cfe2d2344f5d308578 2198 node-define-lazy-prop_3.0.0-5.dsc
f556b38d48945328093bfd77821fe2ace98e5e18 2592
node-define-lazy-prop_3.0.0-5.debian.tar.xz
Checksums-Sha256:
4491b77daee2405e5f3dc81570968c839b2dbe8d4d3b48c8bf68a71c700e4b50 2198
node-define-lazy-prop_3.0.0-5.dsc
38903fd3e51c5f08809f1b266878ca5184c99c053d56e9c3e62805c77bff3518 2592
node-define-lazy-prop_3.0.0-5.debian.tar.xz
Files:
e59ead06f040845dbba25dbfc5c16759 2198 javascript optional
node-define-lazy-prop_3.0.0-5.dsc
7136d170db767ce71c56db64cad0fc58 2592 javascript optional
node-define-lazy-prop_3.0.0-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKRQDQACgkQ9tdMp8mZ
7ul3LA/9HtSlRR37UDYtiipFp2tZf5MmN6uiqt5TbfRR68N6ZYbbq8hXuqR2fl8b
PmEUp5feamH2hHRsd1K9VgEBhDYxwvX9WkSRRQaEuOh7XUZJED6C3eM3zXEUi7Ph
OyJDmmMjHsBCtrKPrBPt7ovN1ukoKD+dMPqAyHWzv/ikwz88/Ic4K54yCcGs66PM
pQMlGHvud7t+eP2ve1xX0+cIi5jiW1BtL+YMaGXBturWIxX5PDjuwlh74JzlY/7O
7mzFyS9Z8/7ysR+j59y3X01hOF9Apd9hdYvOF2cQXMDTToSSFhDuwWm87ckQHqJN
/Jm+1mI4nJ4IERM3UZjnodKc0vTQNgkwbt9zeEQUpwgvQRpMK3vjcL6bwDo6j0bk
hcMBecqAh+KLqxF0WHaUvUZhD1Bsw7g90e7sKKsdpQnPe83z2GybA1AwL6VLfV3k
TGLhcL81BSFoU32WVcPFDRfqSKVy5vRr0Q1PX1hyxg4XFg7gtPHAf2LFvmGvjy5e
U91725d4RbwPkTxWkWXnQMmjJQYocd1k51Pkdwz5HahTYKwgqow8AhygGx+abuOg
uKf8l6QWbmFlwhJMx/TBftZ4Ha6QKpD408Yr+PiFb6HDjGbeTo3rWsVu1wIZf6Oz
5rfW2W1GGljY1uRly7kiZjHTnddRroubJBJIEOsSEdYuG67EEqE=
=edG/
-----END PGP SIGNATURE-----
--- End Message ---
