On 2022-03-28 11:57:14, Paul Gevers wrote: > Hi Jordan, > > On 28-03-2022 10:20, Jordan Justen wrote: > > nmu libxxf86vm_1:1.1.4-1+b2 . ANY . unstable . -m "riscv64 arch is at > > 1:1.1.4-1 > > while others are at 1:1.1.4-1+b2" > > It may be obvious to you, but, so what? Why is that a problem and how > does rebuilding on all architectures solve that?
I want to install libxxf86vm packages, such as libxxf86vm1:riscv64 on amd64. When I try to install it on amd64, apt wants to remove many amd64 packages. I think the difference of 1:1.1.4-1 vs 1:1.1.4-1+b2 might be the cause, but I will admit that I am not certain. As far as building "all architecures" is concerned, I don't know if this is required. If there was a way to only build riscv64 libxxf86vm 1:1.1.4-1+b2 to match the other architectures, then I think that would work as well. When I mentioned this issue on #debian-riscv, it was recommended that I "could `reportbug release.debian.org`, select binNMU to request a rebuild on all arches to get the issue fixed", which is what lead me to file this bug. The reportbug program only provided a single line comment, so I assumed I should keep the explanation short. I apologize if I didn't file the bug properly. -Jordan
signature.asc
Description: signature
