Your message dated Mon, 6 Jul 2026 07:21:06 +0100 with message-id <[email protected]> and subject line [Git][release-team/release.debian.org][master] Document specifying binNMU versions in wanna-build.md has caused the Debian Bug report #1123588, regarding release.debian.org: please document how to request binNMUs with a specific number 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.) -- 1123588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123588 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: release.debian.org Severity: wishlist According to Emilio on #1123577, there is a syntax I could have used when asking for mesa to be binNMU'd as +b3 to bring !amd64 architectures back into sync with +b3 on amd64: nmu 3 mesa . ANY ... which would likely be safer than the one I asked for: nmu mesa_25.2.8-2 . ANY -amd64 . unstable . -m "Rebuild to sync binNMU versions" Could this be described in <https://release.debian.org/wanna-build.txt>? Thanks, smcv
--- End Message ---
--- Begin Message ---Commits: 3a687577 by Jonathan Wiltshire at 2026-07-06T07:14:39+01:00 Document specifying binNMU versions in wanna-build.md - - - - - 1 changed file: - www/wanna-build.md Changes: ===================================== www/wanna-build.md ===================================== @@ -107,6 +107,14 @@ Notes * gb and dw are for failed builds only. Once a package has been built and added to the archive, use a binNMU to rebuild it. + * A particular binNMU number can be appended to the nmu command, which can + be useful for aligning out-of-sync versions on different architectures: + + `nmu 3 foo . [...]` + + The resulting version must not have been seen in the archve before. This + is an alias for the `--binNMU` argument. + Full example (binNMU) --------------------- @@ -155,10 +163,11 @@ Full example (binNMU complex) against it DT_NEED libfrog1 instead of libfrob1. Only foo and bar seem affected. New libfrob is not built everywhere yet, some dep-waits are needed. Also, libfrob's build-dependencies are - installable on mips now. + installable on mips now. bar's version can be brought into alignment + across architectures. nmu foo_4.3-3 . ANY -i386 . -m 'Rebuild against fixed libfrob, see #111.' - nmu bar_2:1.0-7 . ANY . -m 'Rebuild against fixed libfrob, see #111.' + nmu 3 bar_2:1.0-7 . ANY . -m 'Rebuild against fixed libfrob, see #111.' dw foo_4.3-3 bar_2:1.0-7 . amd64 s390x . -m 'libfrob1 (>= 2.1-4)' gb libfrob_2.1-4 . mips View it on GitLab: https://salsa.debian.org/release-team/release.debian.org/-/commit/3a6875774b079bee9d5676d291a01a10bd4a5ec3 -- View it on GitLab: https://salsa.debian.org/release-team/release.debian.org/-/commit/3a6875774b079bee9d5676d291a01a10bd4a5ec3 You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help
--- End Message ---
