After libevent upgraded to 2.0.10: user@box ~ % chromium-bin /opt/chromium.org/chrome: error while loading shared libraries: libevent-1.4.so.2: cannot open shared object file: No such file or directory
The source-based chromium package is less fragile. If you have the hardware for it, I suggest you switch to that.
Just out of curiosity. Would a slotting of the library help in this case? Can't libevent-1.* be installed in parallel to libevent-2.*? If yes, is there a reason why it isn't done? Thanks!
(In reply to comment #1) > The source-based chromium package is less fragile. If you have the hardware for > it, I suggest you switch to that. Same problem with the source-based package -- and revdep-rebuild doesn't find the breakage, which is the real problem. The "chrome" executable is stored in /usr/lib64/chromium-browser where revdep-rebuild doesn't look for executables, just libraries. Maybe this should be a bug against revdep-rebuild?
(In reply to comment #3) > Same problem with the source-based package -- and revdep-rebuild doesn't find > the breakage, which is the real problem. I guess I really meant that the source-based package is fixable by rebuilding it. With the binary, you have to wait until a dev rebuilds it. Not sure on revdep-rebuild. I run portage-2.2 with preserve-libs, and I think that would have caught this.
chromium-bin has been masked for removal.
