[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1123577: marked as done (nmu: mesa_25.2.8-2: +b3 on !amd64)

Your message dated Thu, 18 Dec 2025 14:21:44 +0100
with message-id <f023a080-5a69-44a4-a45c-6d3140ec47a7@debian.org>
and subject line Re: Bug#1123577: nmu: mesa_25.2.8-2: +b3 on !amd64
has caused the Debian Bug report #1123577,
regarding nmu: mesa_25.2.8-2: +b3 on !amd64
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 owner@bugs.debian.org
immediately.)


-- 
1123577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123577
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: mesa@packages.debian.org, debian-arm@lists.debian.org, debian-powerpc@lists.debian.org, debian-riscv@lists.debian.org, debian-s390@lists.debian.org, debian-ports@lists.debian.org
Control: affects -1 + src:mesa
User: debian-arm@lists.debian.org
Usertags: arm64 armhf
User: debian-qa@lists.debian.org
Usertags: i386
User: debian-powerpc@lists.debian.org
Usertags: ppc64el
User: debian-riscv@lists.debian.org
Usertags: riscv64
User: debian-s390@lists.debian.org
Usertags: s390x
User: release.debian.org@packages.debian.org
Usertags: binnmu

mesa was binNMU'd as +b3 on amd64 but +b2 on all the other release 
architectures, resulting in multiarch skew that makes packages like Wine 
and Steam uninstallable. Anyone doing cross-compiling will probably want 
the non-x86 architectures to be co-installable, too. I think this is 
right:

nmu mesa_25.2.8-2 . ANY -amd64 . unstable . -m "Rebuild to sync binNMU versions"

but if there's a syntax for explicitly requesting +b3, that would be 
safer.

-ports, if someone can trigger a +b3 build on the ports that are keeping 
up, that would probably also be helpful:

hppa loong64 m68k powerpc sh4 sparc64 x32

(alpha and hurd-* are BD-Uninstallable, and ppc64 FTBFS, so not much 
point for those)

    smcv

--- End Message ---
--- Begin Message --- 
On 18/12/2025 12:17, Simon McVittie wrote:

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: mesa@packages.debian.org, debian-arm@lists.debian.org, debian-powerpc@lists.debian.org, debian-riscv@lists.debian.org, debian-s390@lists.debian.org, debian-ports@lists.debian.org
Control: affects -1 + src:mesa
User: debian-arm@lists.debian.org
Usertags: arm64 armhf
User: debian-qa@lists.debian.org
Usertags: i386
User: debian-powerpc@lists.debian.org
Usertags: ppc64el
User: debian-riscv@lists.debian.org
Usertags: riscv64
User: debian-s390@lists.debian.org
Usertags: s390x
User: release.debian.org@packages.debian.org
Usertags: binnmu

mesa was binNMU'd as +b3 on amd64 but +b2 on all the other release
architectures, resulting in multiarch skew that makes packages like Wine
and Steam uninstallable. Anyone doing cross-compiling will probably want
the non-x86 architectures to be co-installable, too. I think this is
right:

nmu mesa_25.2.8-2 . ANY -amd64 . unstable . -m "Rebuild to sync binNMU versions"

but if there's a syntax for explicitly requesting +b3, that would be
safer.


There is: nmu 3 mesa . ANY ...

Scheduled.

Cheers,
Emilio

--- End Message ---
Reply to: