After upgrading from net-misc/curl-7.16.3 to 7.16.4, darcs (1.0.9) can't push changesets because it can't find libcurl.so.3 Reproducible: Always Steps to Reproduce: 1. run "darcs push" 2. select the patches I want to push Actual Results: darcs exits with "darcs: error while loading shared libraries: libcurl.so.3: cannot open shared object file: No such file or directory" Expected Results: Changesets are successfully pushed. I was originally using the Haskell overlay, but I disabled it and re-emerged all of darcs' Haskell dependencies when the problem occurred. No change. I masked curl-7.16.4 and downgraded to the version I was using before. I attempted to push before re-emerging darcs and got the message: "darcs: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory" immediately (ie. it didn't even get as far as asking me what patches I want to push). Re-emerging darcs returns me to the original error. This is on an AMD64 system, using Paludis.
You need to run revdep-rebuild after upgrading curl, at the ebuild told you.
(In reply to comment #1) > You need to run revdep-rebuild after upgrading curl, at the ebuild told you. I've done that.
(In reply to comment #2) > I've done that. Well no, you didn't. You did some half-complete attempt on manually fixing things because revdep-rebuild doesn't work with paludis. So, go figure out a replacement for it with paludis folks if the script they provide doesn't work. Not a darcs bug. http://paludis.pioto.org/faq.html#revdep_rebuild
(In reply to comment #3) > Well no, you didn't. You did some half-complete attempt on manually fixing > things because revdep-rebuild doesn't work with paludis. The part of revdep-rebuild that checks linking consistency and determines the list of packages that needs to be rebuilt works fine with paludis. Reemerging everything on that list is the first thing that I tried, and it fixed all the other packages that depend on curl.
Oops. It looks like it was the copy of darcs *on the system that I was pushing to* was the problem, rather than the one on my system. Sorry, Jakub.
