Bug 1007316 - Installation on AWS (CentOS) fails
Summary: Installation on AWS (CentOS) fails
Keywords:
Status: CLOSED DUPLICATE of bug 1007300
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: graphite-web
Version: el6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Steffan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 09:18 UTC by Daniel Scott
Modified: 2013-09-19 23:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 23:28:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Scott 2013-09-12 09:18:18 UTC
Description of problem:
Installation on AWS (CentOS) fails with:

Package python-sqlite2 is obsoleted by python24-sqlite, but obsoleting package does not provide for requirements
Error: Package: graphite-web-0.9.10-7.el6.noarch (epel)
           Requires: python-sqlite2
           Available: 1:python-sqlite2-2.3.5-2.el6.x86_64 (epel)
               python-sqlite2 = 1:2.3.5-2.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


So, it appears that the AWS repos attempt to install python24-sqlite because it apparently provides python-sqlite2. However, I believe that this dependency is not actually required for modern Python (2.6/2.7).

I see that the spec file contains a conditional for Fedora Versions >17 which removes the requirement. Can the file be modified to remove this requirement for CentOS/AWS Linux too?

Also, the python-django package does not exist on CentOS or AWS Linux, I believe that it's called Django14.

Patch attached, which allows me to create an installable RPM for AWS Linux. However, it will likely break Fedora.

Comment 1 Anssi Johansson 2013-09-12 09:25:14 UTC
Duplicate of bug 1007300.

Comment 2 Jonathan Steffan 2013-09-19 23:28:10 UTC
Closing as this is a duplicate. I will continue to address this issue via https://bugzilla.redhat.com/show_bug.cgi?id=1007300.

*** This bug has been marked as a duplicate of bug 1007300 ***


Note You need to log in before you can comment on or make changes to this bug.