Bug 805062 - Rpmdiff failure(s) for build rubygem-nokogiri-1.5.0-0.6.beta4.el6
Summary: Rpmdiff failure(s) for build rubygem-nokogiri-1.5.0-0.6.beta4.el6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Common
Classification: Retired
Component: rubygem-nokogiri
Version: 1.0.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: beta6
Assignee: Steve Linabery
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 14:19 UTC by John Eckersberg
Modified: 2012-05-15 20:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 20:58:26 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0584 0 normal SHIPPED_LIVE new packages: rubygem-rails and Ruby on Rails dependencies 2012-05-15 22:31:40 UTC

Description John Eckersberg 2012-03-20 14:19:46 UTC 
https://errata.devel.redhat.com/rpmdiff/show/57798?result_id=1004902 https://errata.devel.redhat.com/rpmdiff/show/57798?result_id=1004918
Comment 1 Jason E. Rist 2012-03-23 20:42:33 UTC 
https://errata.devel.redhat.com/rpmdiff/show/58597?result_id=1028679

Newer one...
Comment 2 Steve Linabery 2012-03-26 20:50:17 UTC 
Cleared these. Got around the multilib regression error by adding BuildArch: noarch to the doc subpackage, and (importantly) adding a BuildRequires: rubygem-rdoc.
Comment 4 Jeff Weiss 2012-04-17 18:49:57 UTC 
I think this is the latest run: https://errata.devel.redhat.com/rpmdiff/show/58889

Verified
Comment 5 errata-xmlrpc 2012-05-15 20:58:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0584.html
Note You need to log in before you can comment on or make changes to this bug.