Bug 1309019 - Error: Package: ostree-2016.1-2.atomic.el7.x86_64 Requires: libgsystem >= 2015.1
Summary: Error: Package: ostree-2016.1-2.atomic.el7.x86_64 Requires: libgsystem >= 2015.1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ostree
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 17:30 UTC by Dennis Kliban
Modified: 2016-02-17 18:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-17 18:10:50 UTC
Target Upstream Version:

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

Description Dennis Kliban 2016-02-16 17:30:26 UTC 
Can't install ostree on RHEL 7 due to dependency resolution problem:

Error: Package: ostree-2016.1-2.atomic.el7.x86_64 (rhel-atomic-host-rpms)
           Requires: libgsystem >= 2015.1
**********************************************************************
yum can be configured to try to resolve such errors by temporarily enabling
disabled repos and searching for missing dependencies.
To enable this functionality please set 'notify_only=0' in \/etc\/yum\/pluginconf.d\/search-disabled-repos.conf
**********************************************************************

 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Comment 2 Colin Walters 2016-02-16 18:48:40 UTC 
I think this needs to be a release engineering ticket.  It seems to be here:

http://cdn.stage.redhat.com/content/dist/rhel/atomic/7/7Server/x86_64/os/Packages/


Is this against the production CDN?
Comment 3 Dennis Kliban 2016-02-16 18:50:23 UTC 
Yes it is  against production.
Comment 5 Dennis Kliban 2016-02-17 18:10:50 UTC 
Looks like we can close this ticket. The CDN has the package metadata available now.
Note You need to log in before you can comment on or make changes to this bug.