Bug 1403296

Summary:	Rebase to libosinfo release 1.0.0
Product:	Red Hat Enterprise Linux 7	Reporter:	Daniel Berrangé <berrange>
Component:	libosinfo	Assignee:	Felipe Borges <feborges>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.4	CC:	cfergeau, fidencio, klember, mclasen, tpelka, vbudikov
Target Milestone:	rc	Keywords:	Rebase
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libosinfo-1.0.0-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 22:54:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1403298
Bug Blocks:	1383353

Description Daniel Berrangé 2016-12-09 14:54:44 UTC

Description of problem:
Rebase is required to the new libosinfo release 1.0.0 to pull into data for recently released operating systems, to enable VM provisioning of them

This new release has split some parts off into separate RPMs, so this rebase will require review of 2 new RPMs

  - osinfo-db - database of libosinfo operating system info
  - osinfo-db-tools - tools for importing/exporting database archives

The RPM dependancies ensure a clean upgrade path, and the API is backwards compatible.

Comment 2 Daniel Berrangé 2017-03-07 15:33:39 UTC

*** Bug 1387014 has been marked as a duplicate of this bug. ***

Comment 3 Kalev Lember 2017-03-15 23:18:57 UTC

Now that osinfo-db is in, I've kicked off a libosinfo-1.0.0-1.el7 build that mclasen prepared a while back.

Comment 6 errata-xmlrpc 2017-08-01 22:54:46 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.

https://access.redhat.com/errata/RHBA-2017:2113