[From nobody Tue Nov 17 16:21:06 2026
Received: (at submit) by bugs.debian.org; 6 Feb 2026 12:15:01 +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=-105.2 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
 DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
 FUZZY_CPILL,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
 USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 150; neutral, 73; spammy,
 0. spammytokens:
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: &lt;smcv@debian.org&gt;
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:45268)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;smcv@debian.org&gt;) id 1voKjl-00AWI0-2B
 for submit@bugs.debian.org; Fri, 06 Feb 2026 12:15:01 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=CrAbhMBqIaxXfzckNgOr9KbgTbC9VnS8bYySonp71G0=; b=eUpLQFFD48PNqrtzTOOv81MJWw
 X8UFwvb0Qz+Sh/ieCPR3iy3ZONEQjeynlFqCC+Mk/ha+AiH1RwcPh20Cz8mndJe4ztKYR/B8lBztV
 FzYDi+hnNpTGE+fgLjo/krjCsE5f+0ZYLxTObtAzZFIhHFNBRQ7U0+qSg9+uahDj2ycwMbnGiMM/d
 2pr2D7KDx4wTrauwuEJfPwJ/zdx9hm/nks6L2I2sGsoidLiZB8Xghk56sZZdu6BJg+vMUkA9A5HKE
 EaDbs59PO00zQyxQC6O3ylWaHciWh3HyNTnR7MniCAEQABUewrKKyWhsSTfa46UMvBoB3AyL3W+go
 xoTvsEjQ==;
Received: from authenticated user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from &lt;smcv@debian.org&gt;) id 1voKjj-0079TZ-H0
 for submit@bugs.debian.org; Fri, 06 Feb 2026 12:14:59 +0000
Date: Fri, 6 Feb 2026 12:14:58 +0000
From: Simon McVittie &lt;smcv@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: libassuan: autopkgtest regression with wine/10.0~repack-12
Message-ID: &lt;aYXbQrXC_xQnv0B4@remnant.pseudorandom.co.uk&gt;
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debian-User: smcv
Delivered-To: submit@bugs.debian.org

Source: libassuan,wine
Control: found -1 libassuan/3.0.2-2
Control: found -1 wine/10.0~repack-12
Control: block 1121773 by -1
Severity: serious
Tags: forky sid
Justification: https://release.debian.org/testing/rc_policy.txt 6a
User: debian-ci@lists.debian.org
Usertags: breaks needs-update

Since wine was updated to 10.0~repack-12, it no longer provides 
/usr/lib/wine/wine64. Instead, it's now /usr/bin/wine64 or 
/usr/lib/${DEB_HOST_MULTIARCH}/wine/wine. Similarly, the 
wineserver is now /usr/lib/${DEB_HOST_MULTIARCH}/wine/wineserver.

This breaks assumptions made by the autopkgtest in libassuan, causing 
the new wine version to be unable to migrate to testing, which in turn 
results in #1124433 not getting fixed in testing.

If this is an intentional interface change, then 
debian/tests/build-windows in src:libassuan will need updating to use 
more appropriate paths. Perhaps the Wine maintainers could suggest a 
patch?

Even if this was an intentional interface change, it might be a good 
idea to special-case wine:amd64 and wine:i386 to provide enough symlinks 
in /usr/lib/wine/ that the libassuan test will still pass: that would 
allow this bug to be reassigned to src:libassuan at a lower severity, 
and the compatibility symlinks could be removed when libassuan and other 
affected packages (dxvk, libgpg-error) have been updated.

Or, if this was not an intentional interface change, perhaps wine should 
special-case wine:amd64 and wine:i386 to provide those symlinks in the 
longer term?

I've usertagged this as both &quot;breaks&quot; and &quot;needs-update&quot; because it 
isn't obvious to me whether changes are desired in libassuan, in wine, 
or both, but at least one of these two packages will need changes before 
a version of wine with the new paths can migrate.

Thanks,
    smcv
]