On Mon, 22 Apr 2024 21:01:22 +0200 Helmut Grohne <hel...@subdivi.de> wrote: > Package: librust-bitflags-1-dev > Version: 1.3.2-5+b1 > Severity: serious > Justification: causes an installation failure > > Hi, > > Attempting to install librust-bitflags-1-dev for multiple architectures > fails, because apt and dpkg disagree about how breaks and provides work. > apt thinks that self-breaks can be ignored, but dpkg thinks that since > librust-bitflags-1-dev breaks+provides librust-bitflags-1.3.2-dev it > cannot be coinstalled and gives up. You cannot combine such > breaks+provides with m-a:same. The simplest workaround here is dropping > m-a:same as it cannot be exercised anyway. > > Helmut
This is the same situation as in #1040477. This is an issue wrt how we generate the semvers. I image rust-proc-macro-crate-1 would pose the same problem. Quoting you from 1040477:
A very simple workaround from my pov would be temporarily removing Multi-Arch: same. Of course that would make the package unavailable to cross compilation, but on the flip side, it already is. After dropping Multi-Arch: same, dose would no longer consider solutions involving coinstallations of it and archive testing could continue. Failing that, the only way I see is blacklisting the package in crossqa, but then I'd probably forget about it and it would also be surprising in the diagnostics as crossqa would always tell that this package does not exist. I prefer having you work around the issue. A simple upload dropping M-A:same removes the worst of pain and gives us time to work on a generic solution. Do you agree?
Is the only workaround dropping Ma:same here ? Unfortunately we need the semvers (but try to keep them to a minimum). CC'd Fabian since he is a bit more knowledgable than me here. best, -- Matthias Geiger <werdahias> Debian Maintainer
