Hi Andrea, On Tue, Apr 08, 2025 at 09:33:17AM +0200, Andrea Pappacoda wrote: > On Mon, 7 Apr 2025 16:38:40 +0200 Helmut Grohne <hel...@subdivi.de> wrote: > > Package: android-udev-rules > > Version: 0~20250314+ds-2 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: fileconflict > > Control: affects -1 + google-android-platform-tools-installer > > > > android-udev-rules has an undeclared file conflict. This may result in > > an unpack error from dpkg. > > > > The file /usr/lib/udev/rules.d/51-android.rules is contained in the > > packages > > * android-udev-rules/0~20250314+ds-2 as present in trixie|unstable > > * google-android-platform-tools-installer/33.0.3+1675172738 as present in > > bookworm > > Isn't this a duplicate of <https://bugs.debian.org/1101906>? If yes, should > I just close this?
You may consider it a duplicate, yes. Unfortunately, my tooling is unable to reopen existing bugs and files duplicates for ones that have been closed in error. In this case, the offending file has been removed from google-android-platform-tools-installer in trixie and sid and therefore the conflict with trixie and sid is now resolved. However, the conflict with the bookworm version still remains unaddressed. android-udev-rules needs to declare Breaks+Replaces to fix it. That's what this bug report is about and if you compare them, you may now spot the subtle difference of dropping the trixie/sid version. Note that this bug report is filed by the Debian Usr Merge Analysis Tool with the purpose of ensuring correct Replaces such that ineffective Replaces can be identified. As a result of the /usr-move transition some Replaces declarations result in the replaced files being lost in an upgrade. I happened to check google-android-platform-tools-installer in bookworm and indeed that happens to be such a case, so once you add those missing Breaks+Replaces, dumat would file the next RC bug telling you that you now have ineffective Replaces. For details see https://subdivi.de/~helmut/dep17.html section P1. As in the other such bug for android-udev-rules, I think mitigation M7 should be preferred, so you may go straight to declaring Conflicts here. In your debian/changelog, please mention "DEP17 P1 M7" for tracking purposes. Helmut