Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1403300 - New package 'osinfo-db'
New package 'osinfo-db'
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: osinfo-db (Show other bugs)
7.4
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Felipe Borges
Desktop QE
: FutureFeature
: 1426331 (view as bug list)
Depends On: 1430316
Blocks: 1387014
  Show dependency tree / graph
 
Reported: 2016-12-09 10:02 EST by Daniel Berrange
Modified: 2017-08-01 18:54 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 18:54:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2113 normal SHIPPED_LIVE libosinfo, osinfo-db, and osinfo-db-tools bug fix and enhancement update 2017-08-01 15:37:21 EDT

  None (edit)
Description Daniel Berrange 2016-12-09 10:02:11 EST 
Description of problem:
In order to satisfy the rebase of libosinfo to v1.0.0

  https://bugzilla.redhat.com/show_bug.cgi?id=1403296

We need to import the new 'osinfo-db' package from Fedora. The contents of this new RPM used to be part of the 'libosinfo' RPM but were split off to allow them to have an independent release lifecycle

The Fedora review ticket was:

https://bugzilla.redhat.com/show_bug.cgi?id=1361596
Comment 4 Kalev Lember 2017-02-23 23:18:35 EST 
*** Bug 1426331 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2017-08-01 18:54:46 EDT 
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.

https://access.redhat.com/errata/RHBA-2017:2113
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.