Running ldconfig after the RPM transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi list,

it has been recently proposed to switch openSUSE to run ldconfig via a
%transfiletriggerin/-un scriptlet instead of manually in %post & %postun
the same way as Fedora does it at the moment.

However, an interesting issue has been raised: what happens if package A
gets upgraded in the same transaction as package B, but B needs A during
the upgrade. A will install a new shared library, but ldconfig will run
after B has already tried to upgrade.

Do we have some mechanism to prevent this? Or does this essentially
never happen in practice?

The only "workaround" that came up was to use ordinary file triggers,
but that is not a great idea either these would fire way too frequently
(as mentioned by Florian Weimer on this list in 2018: [1]).


Cheers,

Dan

Footnotes:
[1]  https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/DVBZI2UJRHI5GVMJXIQNLHK4TUFS5ZM2/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux