Bug 805911 - Review Request: rubygem-xmlparser-0.7.2-1 - Ruby bindings to the Expat XML parsing library
Review Request: rubygem-xmlparser-0.7.2-1 - Ruby bindings to the Expat XML pa...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nobody's working on this, feel free to take it
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-22 08:45 EDT by Ulrich Schwickerath
Modified: 2012-04-02 07:28 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-02 07:28:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ulrich.schwickerath: fedora‑review+


Attachments (Terms of Use)

  None (edit)
Description Ulrich Schwickerath 2012-03-22 08:45:50 EDT
Spec URL: https://uschwick.web.cern.ch/uschwick/software/rubygem-xmlparser.spec
SRPM URL: https://uschwick.web.cern.ch/uschwick/software/rubygem-xmlparser-0.7.2-1.el6.src.rpm
Description: Ruby bindings to the Expat XML parsing library
Comment 1 Ulrich Schwickerath 2012-03-22 08:58:43 EDT
This package is an upstream update of rubygem-xmlparser-0.6.81-1, see review request #719854. This old version 0.6.81-1 fails to build on f17 and newer.Therefore, it has been deprecated on those. 

rubygem-xmlparser-0.7.2-1 is an upstream update which compiles fine on f17 and newer.Attempts to backport it to f16 failed.
Comment 2 Vít Ondruch 2012-04-02 07:28:33 EDT
Hi Ulrich,

I am not sure what was the reason, why you have not accessible the f17 and master brachnes for the gem, but this is definitely not correct way, therefore I am closing this ticket. I believe that you did wrongly the SCM request, which never specified that you like to have also the f17 branch. Please try that again.

Note You need to log in before you can comment on or make changes to this bug.