Your message dated Sat, 3 Oct 2026 21:33:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#1107523: release.debian.org: Can i386-only bugs be 
release-critical?
has caused the Debian Bug report #1107523,
regarding release.debian.org: Can i386-only bugs be release-critical?
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.)


-- 
1107523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107523
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]

Dear release team,

wine in testing/unstable is currently broken on i386, that is to say,
on i386 systems upgraded from Debian 12, wine doesn’t work. (See
#1104317 for details.) The i386 packages work fine on amd64.

Given that Debian 13 is dropping support for “standalone” i386
systems, and only officially supporting running i386 packages on amd64
systems, are such issues release-critical?

Regards,

Stephen

--- End Message ---
--- Begin Message ---
Hi,

On Mon, 9 Jun 2025 07:08:25 +0200 Paul Gevers <[email protected]> wrote:
On 08-06-2025 17:13, Stephen Kitt wrote:
> wine in testing/unstable is currently broken on i386, that is to say,
> on i386 systems upgraded from Debian 12, wine doesn’t work. (See
> #1104317 for details.) The i386 packages work fine on amd64.


Did you try reproducing it in a i386 chroot? If the issue can't be reproduced on the supported i386 configurations, I agree with the severity important.

The bug got fixed (it also affected other architectures).

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to