[From nobody Thu Jul  9 16:07:05 2026
Received: (at submit) by bugs.debian.org; 9 Jul 2026 11:55:16 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-25.2 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_CONTROL_AFFECTS,BODY_INCLUDES_PACKAGE,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,SPF_HELO_NONE,
 SPF_NONE autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 129; neutral, 23; spammy,
 0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--forky,
 0.000-+--grohne, 0.000-+--Grohne, 0.000-+--H*F:U*helmut
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:33778)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <helmut@subdivi.de>) id 1whnLY-00GdfE-0X
 for submit@bugs.debian.org; Thu, 09 Jul 2026 11:55:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=subdivi.de;
 s=k30.isilmar-4; t=1783598113;
 bh=4ZsmlV0h8tVJUx/FC8lTqbQ0TZVjFZ7e1R9s76r3TKQ=;
 h=Date:From:To:Subject:From;
 b=poVw1rMfeSSnlqkp1kMPTDfwQaXafKtI4tRZDIWfaTQRQB+zncO66LTcqb7IMq9Zg
 8S8MD9OyKf/K29sotqzXjnE1isNDMjoW2i9Lvf9reN0eQY8cYsSEwAX8MlhSMfaS1T
 s0O590wUoFQRnQ/GJbn8xsaTf93wBRvMCUJNjB7B6RrcHHxCPALfR3ZdckXbVf6VIs
 HcV27FxHt9Jwq7tqrl7bwQif7X+pjH2NIa8Uevnj5c/CABpMSphOtU8rpphKXYsLba
 SdVUO1qYmtvrTUOkd2WN7BVAPgTgdD9Dugq1dmXFce2ExHVReoDKFLhFt0FbNTsowR
 xWGnZ391TeI+w==
Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1])
 by isilmar-4.linta.de (Postfix) with ESMTP id 4D5B72005BE
 for <submit@bugs.debian.org>; Thu,  9 Jul 2026 11:55:13 +0000 (UTC)
Date: Thu, 9 Jul 2026 13:50:59 +0200
From: Helmut Grohne <helmut@subdivi.de>
To: submit@bugs.debian.org
Subject: inwasm has an undeclared file conflict
Message-ID: <20260709115059.GA1463414@subdivi.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Delivered-To: submit@bugs.debian.org

Package: inwasm
Version: 0.1.2+dfsg-2
Severity: serious
User: debian-qa@lists.debian.org
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-2 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
]