If you upgrade libattica-0.3.0 from 0.2.0 and have kdelibs installed, you have that the link in libkdeui.so point to libattica.so.0 , but with version 0.3.0 this link does not exist so you have a broken libkdeui and every package you try to build against libkdeui fail. Reproducible: Always Steps to Reproduce: 1. install libattica-0.2.0 2. build kdelibs 3. upgrade to libattica-0.3.0 4. install somethink linked to libkdeui like skanlite 5. Actual Results: /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libattica.so.0, needed by /usr/lib64/libkdeui.so.5.8.0, not found (try using -rpath or -rpath-link) /usr/lib64/libkdeui.so.5.8.0: undefined reference to `Attica::Person::~Person()' /usr/lib64/libkdeui.so.5.8.0: undefined reference to `Attica::Provider::~Provider()' /usr/lib64/libkdeui.so.5.8.0: undefined reference to `Attica::Person::city() const' Expected Results: no errors everything compile good This bug should block #418749 since it could cause useless pain to Gentoo users. If it's wanted that libattica.so.0 disappear *PLEASE* add a EWARN to inform users that they have to run revdep-rebuild to avoid problems.
Ever heard of revdep-rebuild? :)
No, I'm only using Gentoo since 2003. Instead of closing it, why not adding an ewarn like in app-text/poppler : pkg_postinst() { ewarn "After upgrading app-text/poppler you may need to reinstall packages" ewarn "linking to it. If you're not a portage-2.2_rc user, you're advised" ewarn "to run revdep-rebuild" } 3 lines and you'll get a lot of time saved for the users, a lot of time saved in support in forums/irc and a much better image as a distro that inform users of what is going to happened.
After every update you should run revdep-rebuild.
I ran into the same problem even although I know about revdep-rebuild. It is serious because after a reboot kdm will not start up and you just get a text terminal.
