• Bug#1104519: liblemonldap-ng-common-perl: prompts for unmodified conffi

    From Santiago Vila@21:1/5 to All on Thu May 1 16:40:01 2025
    El 1/5/25 a las 15:53, Chris Hofstaedtler escribió:
    Package: liblemonldap-ng-common-perl
    Version: 2.21.0+ds-2
    Severity: serious

    When upgrading a system from Debian bookworm to Debian trixie, with liblemonldap-ng-common-perl installed, the upgrade prompts for a conffile change. However that file was never modified in the first place, so prompting is inappropriate.

    Hi. I wondered how this can happen at all when the package uses dpkg's conffile mechanism.

    The root of the problem seems to be that the file for which the prompting happens
    was not marked as a conffile in bookworm, which was a bug in the bookworm package that we can't fix retroactively in bookworm.

    Is there a good way to fix that?

    It would be strange to remove a package from trixie for a bug like this one precisely when it's trying to fix a bug in bookworm.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Thu May 1 16:50:01 2025
    Is there a good way to fix that?

    Well, this is the only way it comes to mind:

    Before dpkg prompts about the file, calculate md5sum, if upgrading
    from bookworm and the md5sum matches the one in bookworm,
    quietly replace the file by the new one.

    Would this avoid dpkg's prompt?

    For it to work, it would have to be done "soon" in the upgrade path
    (would any of preinst/postinst/prerm/postrm be appropriate?)

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Hofstaedtler@21:1/5 to All on Thu May 1 17:20:02 2025
    * Santiago Vila <sanvila@debian.org> [250501 16:39]:
    Is there a good way to fix that?

    Well, this is the only way it comes to mind:

    Before dpkg prompts about the file, calculate md5sum, if upgrading
    from bookworm and the md5sum matches the one in bookworm,
    quietly replace the file by the new one.

    Would this avoid dpkg's prompt?

    I don't know exactly. I have seen packages that do creative things
    to rectify such situations.

    For it to work, it would have to be done "soon" in the upgrade path
    (would any of preinst/postinst/prerm/postrm be appropriate?)

    I imagine some preinst hacks will be necessary.

    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)