when upgrading fron gdbm 1.8.3-r1 to 1.8.3-r2 we get this file: -rw-r--r-- 1 root root 0 Oct 4 11:45 /usr/lib/libgdbm.so.2 during the upgrade we can see a message saying that is normal and revdep-rebuild should resolve the broken software. But revdep-rebuils say that everything is ok even with the 0 byte library... but the package ypserv (an important one) don't work anymore... tigre ~ # ldd /usr/sbin/ypserv /usr/sbin/ypserv: error while loading shared libraries: /usr/lib/libgdbm.so.2: file too short this a problem, isn't it ? thank you. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Re-assign and change summary, gdbm ebuild is *still* broken. <snip> pkg_preinst() { # temp backwards support #32510 if [[ -e ${ROOT}/usr/$(get_libdir)/libgdbm.so.2 ]] ; then touch "${D}"/usr/$(get_libdir)/libgdbm.so.2 fi } </snip> This makes zero sense; if you are *upgrading*, then leave the old lib in there (like readline does, e.g.) and instruct users to run revdep-rebuild and then delete the old version - but *don't* create an empty dummy crap which breaks revdep-rebuild and a bunch of things, like ypserv or apache (for that, see Bug 58242, comment #11). The above "fix" actually breaks things. :/
it makes perfect sense when you realize it's a copy and paste error from code that used to exist in src_install the fact that it's a 0 byte file doesnt make it any less broken than if it didnt exist at all fixed in cvs