On Wed, Jun 12, 2024 at 05:16:27PM -0700, Ryan Tandy wrote:
Hello Athos,
On Wed, Jun 12, 2024 at 10:53:37AM -0300, Athos Ribeiro wrote:
Installing packages which depend on libldap2 with
--no-install-recommends will not install the libldap-common package.
This may result in unexpected behaviors when libldap2 code paths are
triggered due to a missing reference to the trusted CAs certificates,
which is defined by the configuration file shipped in libldap-common.
Yes. It's not a great user experience, and while I believe Recommends
is technically Policy-compliant, I agree Depends would be preferable.
Since the dak bug affects several other packages, this should, ideally,
be fixed in dak.
I am marking this bug as blocked by the dak bug for visibility. Due to
the severe consequences when the issue occurs (many packages become
BD-Uninstallable due to transitive build-dependencies on libldap,
requiring a manual bootstrap upload of openldap to resolve), I cannot
accept the patch until _after_ dak has been fixed.
Thanks for the quick reply here, Ryan!
I understand the pain there. How often did the issue occur back then
when the libldap-common was in Depends?
--
Athos Ribeiro
