Your message dated Fri, 10 Jul 2026 09:05:13 +0000
with message-id <[email protected]>
and subject line Bug#1141774: fixed in node-inwasm 0.1.2+dfsg-4
has caused the Debian Bug report #1141774,
regarding inwasm has an undeclared file conflict
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 [email protected]
immediately.)


-- 
1141774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141774
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: inwasm
Version: 0.1.2+dfsg-3
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + node-inwasm-runtime

inwasm has an undeclared file conflict.  This may result in an unpack
error from dpkg.

The files
 * /usr/share/nodejs/inwasm/lib/index.d.ts
 * /usr/share/nodejs/inwasm/lib/index.js
 * /usr/share/nodejs/inwasm/lib/index.js.map
 * /usr/share/nodejs/inwasm/package.json
 * /usr/share/nodejs/inwasm/pkgjs-lock.json
are contained in the packages
 * inwasm/0.1.2+dfsg-3 as present in unstable
 * node-inwasm-runtime
   * 0.0.13~git20230419+dfsg-3 as present in trixie
   * 0.0.13~git20230419+dfsg-4 as present in forky

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation.  Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

Helmut Grohne

--- End Message ---
--- Begin Message ---
Source: node-inwasm
Source-Version: 0.1.2+dfsg-4
Done: Xavier Guimard <[email protected]>

We believe that the bug you reported is fixed in the latest version of
node-inwasm, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard <[email protected]> (supplier of updated node-inwasm 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 10 Jul 2026 09:59:45 +0200
Source: node-inwasm
Architecture: source
Version: 0.1.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 1141774
Changes:
 node-inwasm (0.1.2+dfsg-4) unstable; urgency=medium
 .
   * Team upload
   * Really fix file conflicts (Closes: #1141774)
Checksums-Sha1: 
 ed6367b5ce9f68388f03f9c8b71d9a55ad807192 2435 node-inwasm_0.1.2+dfsg-4.dsc
 a44b0c88b13f58121d49572c5afff6051eddc726 7880 
node-inwasm_0.1.2+dfsg-4.debian.tar.xz
Checksums-Sha256: 
 27b0c9de22f40ad6a6dded9bdab3e382aa83dc7ddc5c8b02f186ef24a211c8aa 2435 
node-inwasm_0.1.2+dfsg-4.dsc
 7bef728387854275a3d0c2af29287aa4287bfaaa560c3ccbc66965141da7d1fa 7880 
node-inwasm_0.1.2+dfsg-4.debian.tar.xz
Files: 
 55f7d04295c41ccf9b90fd86e11bd972 2435 javascript optional 
node-inwasm_0.1.2+dfsg-4.dsc
 48f7566eabd4381fd04b55ffe56a6cd6 7880 javascript optional 
node-inwasm_0.1.2+dfsg-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmpQslsACgkQ9tdMp8mZ
7ulcaA//RUZqckYvPhM0+lT27uPt0+SPlW11Y5JoYOYHnxtYLQU+IGV80lXaMaNM
UAf5Rq+zN/QNnI3V0nINnAPPdrtawjzYbhs9itZ3DrwPBzTmbaC7HUKvlimMEhER
Rx26OdddWV+N6Qlu/r+jkNnmOABTBWSB/OsvYYFhgbv1qkLmVceRxrgScEm2+ycW
NYNPEidM6KY9kMHtL7jNFFym3GRQfdCnTMBYDOfx8DRqPFnS+nqFfpnw/mgk6tlk
6UjCmhMC2GkTucYLdEor7d4Xb3DVxylJQxzUmX8F9p8eD52vibscOs2XrCWzoxUd
TTzSKBZW74rSw2D1Xvk+LkQDeYOXNbxF6ke3euxRrOtE2CZT6OttMpZJFpIYvEZF
EfF+MhehGb/x6XCZHOXN3gqY8KJTXnzVBrDD1Cu9BF92fv4PGoS6HsJX4bQ0gf0n
ZN2NBdUesMlXnJS1jUYMALQdARAOV1Lg/IIzjhDtzPo21zK8M5hnWm7B/hFLhELF
nEl+PmOSEie6r0qlWzSaqlo9MkwLYdMZ/PqYXpTTS24i48tHJOmHr4aAEvF6BAtc
9MnpPq9Fghgsbq/Yh6RfMYkXZV/uFeL6xFEeh/x/zrIrGiXjs3WVnPcUdS4TFbdV
ukvWFAs0h+WinLYLAhUYSAHt41enAxA51VRXOSwRz+8ujP3TmsM=
=MS8p
-----END PGP SIGNATURE-----

Attachment: pgpYXowLRd8Z9.pgp
Description: PGP signature


--- End Message ---

Reply via email to