On 23/10/15 13:21, Emilio Pozuelo Monfort wrote: > On 23/10/15 13:02, Thorsten Glaser wrote: >> On Fri, 23 Oct 2015, Adam D. Barratt wrote: >> >>> wanna-build does, yes, but at least the Release Team tend to use the "wb" >>> wrapper tool which automatically works out the next free number on each >>> architecture. >> >> Ah, cool – so we have only to patch this tool to automatically >> use the highest number per batch on all affected architectures >> (or even to use the highest number if all architectures would >> be touched, but that’s probably an unreasonable amount of code >> change). > > Sorry, aren't you saying the same thing in both cases? If not, can you > rephrase > or expand that? > >> Where’s the source code to that tool? > > https://anonscm.debian.org/cgit/mirror/release-tools.git/tree/scripts/wb > > Please open a bug report against release.debian.org when submitting a patch.
OTOH, I'm not sure this fix is appropriate. It just feels like a workaround for a dpkg bug, which would be better fixed in dpkg itself. This won't help when we have to schedule a binNMU on one or two architectures and not all of them. Emilio
