[From nobody Tue Nov 17 16:21:07 2026
Received: (at submit) by bugs.debian.org; 6 Feb 2026 12:37:39 +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,FVGT_m_MULTI_ODD,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, 8; hammy, 150; neutral, 77; 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]:59508)
 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 1voL5e-00AYWs-2m
 for submit@bugs.debian.org; Fri, 06 Feb 2026 12:37:39 +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=rwNDtIB1uGB8xMxmtslv3gWJorJXHqn+w2UeUtwjlnU=; b=H861VC5q8O1mdSKBx8hn3q2Z+s
 hlOmxB3XMiPRvjTKl76T/BC69gayV23abjs0XPhK36Cv43jDtXdaUNMXpOhDbJ8lYJTSZ6Yj9LhIQ
 4vTVo5atMRAftR0qINcxuZEe4aud3Fq+cV9kvNNwEkLdxOGvdfYa8d44NX1fAZK4y7H7FB73AZx8M
 xNtbdxNjUELK4CujQBI8X6643/YjINyjABbr10Lc6aljnfBPb9+i84wseyo+V3+Ow2K7KpN0425hT
 Dy7Xvey3Hb1b8jQSQwkWsAozBqvhNtKBHzucNIJNcbHzthatrBMLQZA3KvZBgbK4m2AOPVyI8VelG
 tp3WaQRw==;
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 1voL5c-007A8i-KC
 for submit@bugs.debian.org; Fri, 06 Feb 2026 12:37:36 +0000
Date: Fri, 6 Feb 2026 12:37:35 +0000
From: Simon McVittie &lt;smcv@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: gnupg2: autopkgtest regression on i386 with wine/10.0~repack-12
Message-ID: &lt;aYXgjxneaUpbdFEy@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: gnupg2,wine
Control: found -1 gnupg2/2.4.8-5
Control: found -1 wine/10.0~repack-12
Control: block 1124433 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
User: debian-qa@lists.debian.org
Usertags: i386

(This is very similar to corresponding bugs that I opened for 
src:libassuan + src:wine and src:libgpg-error + src:wine)

Since wine was updated to 10.0~repack-12, wine:i386 no longer provides 
/usr/lib/wine/wine. Instead, it's now /usr/bin/wine 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 gpgv-win32 autopkgtest in gnupg2, 
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/gpgv-win32 
in src:gnupg2 will need updating to use more appropriate paths.

Even if this was an intentional interface change, it might be a good 
idea to special-case wine:i386 to provide enough symlinks in 
/usr/lib/wine/ that autopkgtests like this one will still pass: that 
would allow this bug to be reassigned to src:gnupg2 at a lower severity, 
and the compatibility symlinks could be removed when gnupg2 and other 
affected packages (dxvk, libassuan, 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 gnupg2, 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
]