Presence of libnokogiri-ruby1.8 breaks many gems - symptom "Nokogiri was built against LibXML version 2.6.32, but has dynamically loaded 2.7.5"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libgems-ruby (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: rubygems1.8
Summary:
Quite a few gems depend on the nokogiri gem. The nokogiri gem does not work when package libnokogiri-ruby1.8 is also installed on the system. So I suggest that rubygems1.8 should have, in its deb dependency information, a conflict with libnokogiri-
Details:
The nokogiri gem seems to install fine, and does provide some functionality. But is broken when libnokogiri-ruby1.8 is also installed. See http://
The underlying problem: Nokogiri has two parts, a library nokogiri.so and ruby code. Now libnokogiri-ruby1.8 provides a second, older version of nokogiri.so. When libnokogiri-ruby1.8 is installed, the gem's new ruby code gets mixed up with the older libnokogiri-ruby1.8 library. This causes bugs.
Quite a few gems depend on the nokogiri gem as a prerequisite. So the presence of libnokogiri-ruby1.8 breaks a substantial part of the gem system as a whole. Therefore I suggest a conflict between rubygems1.8 and libnokogiri-ruby1.8 should be introduced in the rubygems1.8 .deb dependency information.
The same problem may also be present for ruby 1.9 as well. This I did not investigate.
Best regards, and thank you for providing and maintaining fine software,
Andreas
ProblemType: Bug
Architecture: i386
Date: Fri Feb 12 11:15:11 2010
DistroRelease: Ubuntu 9.10
Package: rubygems1.8 1.3.5-1ubuntu2
PackageArchitec
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: libgems-ruby
Uname: Linux 2.6.31-19-generic i686