Hi! On Tue, 2024-09-24 at 09:47:55 +0200, Patrice Duroux wrote: > Also, the installed package providing the current file that is > conflicting might not be related > to that package (multiarch or not). I mean that it could be another > unrelated package.
No, this message is always only concerned about multi-arch instances, of the same package. There is no support for ref-counting for anything that is not a Multi-Arch:same package. > I wasn't sure if it was a hint message from dpkg that determined the > current proprietary > package of the file (and so it should be another arch) or if it was a > generic message for > all cases. The message is only about a conflict that occurs when installing a multi-arch instance when other instances of the same package are already unpacked, and the new one does not match the digest for the other ones. > So maybe if dpkg can't determine at that time which already installed > package is conflicting > for the file to provide better guidance, the message should be very > simple and avoid any > additional sentences. No? See above, the current instance conflicts with all existing ones (at the same version). It could also print instead all the existing ones, but that would make the message longer, and the information for the current instance is readily available, so I'm not sure what would be the gain with a reversal of the affected packages? (I'm now wondering whether I really understand the source of the confusion for the error message. :) Thanks, Guillem
