Bug 805058 - Rpmdiff failure(s) for build rubygem-eventmachine-0.12.10-6.el6
Summary: Rpmdiff failure(s) for build rubygem-eventmachine-0.12.10-6.el6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Common
Classification: Retired
Component: rubygem-eventmachine
Version: 1.0.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
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:56 UTC (History)
1 user (show)

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

Attachments (Terms of Use)


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:26 UTC 
https://errata.devel.redhat.com/rpmdiff/show/57755?result_id=1003520 https://errata.devel.redhat.com/rpmdiff/show/57755?result_id=1003517
Comment 1 Steve Linabery 2012-03-22 22:17:29 UTC 
https://errata.devel.redhat.com/rpmdiff/show/57755?result_id=1003520 built new package

https://errata.devel.redhat.com/rpmdiff/show/57755?result_id=1003517 waived
Comment 3 Jeff Weiss 2012-04-17 19:09:11 UTC 
Waiver says we won't support IPv6, that is not true.  rejected
Comment 4 Jeff Weiss 2012-04-17 19:59:10 UTC 
Ok, apparently we aren't supporting ipv6 after all, basically because we lack the resources to test it, not because there should be any work to develop it.
Comment 5 errata-xmlrpc 2012-05-15 20:56:55 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.