A binpkg was built on a host with sys-libs/db:4.8 only and installed on a host with sys-libs/db:5.3 only. This resulted in a missing runtime dependency and an error at the end of the install: /usr/sbin/postfix: error while loading shared libraries: libdb-4.8.so: cannot open shared object file: No such file or directory /usr/sbin/postfix: error while loading shared libraries: libdb-4.8.so: cannot open shared object file: No such file or directory Reproducible: Always
I will change sys-libs/db-3.2:* dependency to sys-libs/db-3.2:= with the next bump but otherwise working as expected. postfix builds by including <db.h> and linking with -ldb
That won't fix the problem, as it doesn't guarantee the depended-on db is the same as the located db. This is always an issue with slotted software.
This is one of the reasons we want to reduce BDB use in ::gentoo to an absolute minimum. The whole ecosystem around BDB and its dependencies is a travesty and would require a complete rewrite, but given that all the versions we have in-tree are long EOL, I don't think there's any point in trying to salvage BDB. @Eray Aslan would it be possible for you to slowly sunset BDB out of postfix?
(In reply to Sam James from comment #2) > That won't fix the problem no it wont but it is a signal that you cannot change the db libraries underneath postfix (In reply to David Seifert from comment #3) > @Eray Aslan would it be possible for you to slowly sunset BDB out of postfix? sunset no, not really. also berkdb USE flag is default on. I wanted to turn it off for a long time but kept it on for backward compatibility. it is probably time to reconsider
(In reply to Eray Aslan from comment #4) > sunset no, not really a note is probably warranted here: we can of course sunset berkdb in postfix but it will result in some loss (though not much there are alternatives) in functionality and work for end users. As to sunsetting db in ::gentoo, I will definitely not object - on the contrary - but until then keeping it as an option seems to be a better choice. It is the default db implementation upstream. hmm, perhaps we can have that changed
(In reply to Eray Aslan from comment #5) > (In reply to Eray Aslan from comment #4) > > sunset no, not really > > a note is probably warranted here: we can of course sunset berkdb in postfix > but it will result in some loss (though not much there are alternatives) in > functionality and work for end users. > > As to sunsetting db in ::gentoo, I will definitely not object - on the > contrary - but until then keeping it as an option seems to be a better > choice. It is the default db implementation upstream. hmm, perhaps we can > have that changed You should convince them to change it, since people are using ancient versions of BDB in practice, which is riddled with security bugs and is untested in practice. Furthermore, Oracle has genuinely neglected maintenance of BDB, and I would really treat is as a piece of dead software long past its prime.
