Re: Bug#1104854: binNMUs can cause ma-same violations in eg manpages
On Wed, May 07, 2025 at 02:39:00PM +0100, Ian Jackson wrote:
>...
> It seems anomalous that we (i) schedule binNMUs on each architecture
> separately but (ii) they must all be aligned. This leads to suggest
> another option
> E. Always schedule rebuilds on all arches, so they all
> have identical bdates.
>...
This suggestion is based on assumptions that are not true.
At the wanna-build level you can schedule only a binNMU for one
architecture, higher level tools that schedule rebuilds on all
arches do therefore emit one binNMU command per architecture.
It might be possible to hack together a solution for what you want,
but that would still not solve the other problem of binary-all binNMUs.
As already mentioned, the proper solution for binNMUs would be at the
dak level with a dcut command[1] - then you have a proper new source
package with a new source version and everything will just work
without additional hacks.
> Ian.
cu
Adrian
[1] or some dedicated service, so that the requester of a 1k package
binNMU does not have to download sources for 1k packages and does
not have to sign 1k packages
Reply to: