• Bug#1102321: android-udev-rules has an undeclared file conflict on /usr

    From Helmut Grohne@21:1/5 to All on Mon Apr 7 17:20:02 2025
    Package: android-udev-rules
    Version: 0~20250314+ds-2
    Severity: serious
    User: [email protected]
    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

    These packages can be unpacked concurrently, because there is no
    relevant Replaces or Conflicts relation. Attempting to unpack these
    packages concurrently results in an unpack error from dpkg, because none
    of the packages installs a diversion for the affected file.

    Kind regards

    The Debian Usr Merge Analysis Tool

    This bug report has been automatically filed with no human intervention.
    The source code is available at https://salsa.debian.org/helmutg/dumat.
    If the filing is unclear or in error, don't hesitate to contact [email protected] for assistance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrea Pappacoda@21:1/5 to [email protected] on Tue Apr 8 09:40:01 2025
    --c7d3b4a7c0626fa39077d8fff18979136ef4e6a4fa289a33e2129d42d65c Content-Transfer-Encoding: quoted-printable
    Content-Type: text/plain; charset=UTF-8; format=Flowed

    Hi Helmut,

    On Mon, 7 Apr 2025 16:38:40 +0200 Helmut Grohne <[email protected]> wrote:
    Package: android-udev-rules
    Version: 0~20250314+ds-2
    Severity: serious
    User: [email protected]
    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?

    Bye!

    --c7d3b4a7c0626fa39077d8fff18979136ef4e6a4fa289a33e2129d42d65c
    Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iIcEABYIAC8WIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZ/TRPhEcdGFjaGlAZGVi aWFuLm9yZwAKCRBKkgiiRVB3p8BBAP96Xs18kt8e7r2zQsL98U1fAxPDc8nh45sP rYFOvAgvUwD/f+81G0dZqQ7xlwOyfMhdsMkqPmG1GEnZnVNd54603Q4=Xka7
    -----END PGP SIGNATURE-----

    --c7d3b4a7c0626fa39077d8fff18979136ef4e6a4fa289a33e2129d42d65c--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Apr 8 11:10:01 2025
    This is a multi-part message in MIME format...

    Your message dated Tue, 08 Apr 2025 09:03:49 +0000
    with message-id <[email protected]>
    and subject line Bug#1102321: fixed in android-udev-rules 0~20250314+ds-3
    has caused the Debian Bug report #1102321,
    regarding android-udev-rules has an undeclared file conflict on /usr/lib/udev/rules.d/51-android.rules
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected]
    immediately.)


    --
    1102321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102321
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 7 Apr 2025 15:09:20 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-25.2 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_CONTROL_AFFECTS,BODY_INCLUDES_PACKAGE,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,SPF_HELO_NONE,
    SPF_NONE autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 9; hammy, 145; neutral, 37; spammy, 0.
    spammytokens: hammytokens:0.000-+--trixie, 0.000-+--bookworm,
    0.000-+--H*F:U*helmut, 0.000-+--H*F:D*subdivi.de,
    0.000-+--H*RU:sk:helmut@
    Return-path: <[email protected]>
    Received: from isilmar-4.linta.de ([136.243.71.142]:59308)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AE
  • From Helmut Grohne@21:1/5 to Andrea Pappacoda on Wed Apr 9 09:00:02 2025
    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 <[email protected]> wrote:
    Package: android-udev-rules
    Version: 0~20250314+ds-2
    Severity: serious
    User: [email protected]
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Wed Apr 9 13:30:01 2025
    This is a multi-part message in MIME format...

    Your message dated Wed, 09 Apr 2025 11:18:59 +0000
    with message-id <[email protected]>
    and subject line Bug#1102321: fixed in android-udev-rules 0~20250314+ds-4
    has caused the Debian Bug report #1102321,
    regarding android-udev-rules has an undeclared file conflict on /usr/lib/udev/rules.d/51-android.rules
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected]
    immediately.)


    --
    1102321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102321
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 7 Apr 2025 15:09:20 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-25.2 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_CONTROL_AFFECTS,BODY_INCLUDES_PACKAGE,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,SPF_HELO_NONE,
    SPF_NONE autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 9; hammy, 145; neutral, 37; spammy, 0.
    spammytokens: hammytokens:0.000-+--trixie, 0.000-+--bookworm,
    0.000-+--H*F:U*helmut, 0.000-+--H*F:D*subdivi.de,
    0.000-+--H*RU:sk:helmut@
    Return-path: <[email protected]>
    Received: from isilmar-4.linta.de ([136.243.71.142]:59308)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AE