Hi all, I regulary run 'emerge rsync' and 'emerge --update world'. Today I ran 'emerge clean' to remove old versions of files/library's. After running 'emerge clean' 'emerge rsync' failed with the following error. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ etc # emerge rsync >>> starting rsync with rsync://rsync.gentoo.org/gentoo-portage... /usr/bin/rsync: error while loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After a brief look around google I found that 'emerge popt' should fix this. Which I did and can confirm it does. 'emerge rsync' now works. Regards Danny Hallwood
Not sure how this got assigned to me. Have no idea what caused this. I'm not a portage developer so I'm punting. Sorry.
this happens to me every now and then ... basically what happened is that an older version of a pkg got cleaned while some packages had linked to their shared libraries. if you re-emerge the pkg which is linked to libraries nolonger found, it fixes things by linking to the newer version of the library. in your case, popt had linked to a package which you had d/l-ed a newer version of. then when you `emerge clean`-ed, the older package got punted resulting in popt being unlinked from the package. the problem was probably that popt linked via specific version (libfile.so.x.x.x) rather than the general symlink (libfile.so).
This is the RPM issue; can be solved by having db checks to avoid ebuilds overwriting other ebuilds. (we have another bug for that)
