Bug 146497

Summary: Ruby 1.8.2 missing xml-parsing library files
Product: [Fedora] Fedora Reporter: Ariel Segall <asegall>
Component: rubyAssignee: Akira TAGOH <tagoh>
Status: CLOSED DUPLICATE QA Contact: Bill Huang <bhuang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:08:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ariel Segall 2005-01-28 21:06:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8

Description of problem:
The ruby package downloading using "yum install ruby" was missing
several files. I discovered this when trying to run instiki. Ruby
produced errors of "XML parser module not found". The xsd/xmlparser
file relied upon one of xml/parser (does not exist), xmlscan/scanner
(does not exist), or rexml. Rexml was installed, but was missing
seemingly random files that caused the library to break;
rexml/namespace, in particular, was expected but did not exist,
although rexml/validation, rexml/parent, rexml/cdata,
rexml/parseexception, and rexml/xpath did.
(All references are to the default install directory /usr/lib/ruby/1.8/)

It appears that the default ruby install's rexml library is broken.

Version-Release number of selected component (if applicable):
ruby-1.8.2-1.FC3.0

How reproducible:
Always

Steps to Reproduce:
1.From blank Fedora install, yum install ruby
2.Download instiki (instiki.org)
3.ruby instiki
4. Follow error message trail
    

Additional info:

Comment 1 Ariel Segall 2005-01-28 21:09:30 UTC

*** This bug has been marked as a duplicate of 146387 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:08:05 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.