When I emerged the first time paludis-0.28.0 and tried to run ruby scripts using paludis' ruby bindings, I got an error, because /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/Paludis.so is linked against the previous version of paludis instead of the newly emerged one. A second emerging of paludis solved the problem. There is also an upstream bug: http://trac.pioto.org/paludis/ticket/616. Reproducible: Always Steps to Reproduce: 1. upgrade from <paludis-0.28.0 to paludis-0.28.0 2. irb 3. require 'Paludis' Actual Results: /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/Paludis.so: libpaludisnoconfigenvironment.so.26: cannot open shared object file: No such file or directory - /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/Paludis.so (LoadError) from /usr/share/paludis/ruby/demos/find_unused_distfiles.rb:4 Expected Results: Loading of of the paludis module for ruby
Created attachment 160368 [details] emerge --info Actually I used gcc-4.3.1-r1 for the emerge, because compilation fails with gcc-3.4.6, my standard compiler
Paludis bug.