ruby-augeas fails to build on ~amd64 Reproducible: Always Steps to Reproduce: 1. Add augeas use flag to puppet 2. Install puppet 3. ruby-augeas fails to build Actual Results: Build failure in attached build log. Expected Results: Successful build.
Created attachment 319150 [details] Build Log
More information from emerge: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER=""
Created attachment 319152 [details] Environment Log
Created attachment 319154 [details] emerge --info =dev-ruby/ruby-augeas-0.4.1
Created attachment 319156 [details] emerge -pqv =dev-ruby/ruby-augeas-0.4.1
*** Bug 430188 has been marked as a duplicate of this bug. ***
As stated in the duplicate bug, it can be fixed by editing : /usr/lib/pkgconfig/augeas.pc and replacing "Requires:" by "Requires: libxml-2.0". Any change of getting this fixed in portage?
Upstream commit with the fix: http://git.fedorahosted.org/cgit/augeas.git/diff/?id=11b00ad. It should probably be applied to app-admin/augeas-0.10.0. It is stable now, so stable dev-ruby/ruby-augeas-0.3.0-r1 fails to compile, too.
Created attachment 324078 [details] Updated ebuild Added epatch statement.
Created attachment 324080 [details, diff] Patch to fix require libxml-2.0
It's still not fixed in portage snapshot 2012-10-10. I fixed it by editing /usr/lib/pkgconfig/augeas.pc as commented before. Any chance to have a clean fix?
I've just fixed this in ruby-augeas-0.4.1 by including an upstream patch for the ruby bindings. With this patch the ruby bindings explicitly check for libxml2 themselves. I agree that it would be better to just fix this in auguas itself, so I'll leave the bug open. ruby-augeas really should not need to know about such implicit dependencies in the augeas include files. I've also filed bug 439732 to stable the ruby-augeas 0.4.1 bindings with this fix included, so we at least have a set of stable packages that work.
Looks like ruby-augeas-0.4.1 is stable and working normal. Should we close this bug as a result?
No, because this is really a bug in augeas itself. ruby-augeas-0.4.1 just works around it. Assigned to current augeas maintainer.
0.4.1 has the fix via the patch and 0.5.0 (just added) doesn't need the patch. So, fixed.