-
-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python-pip requires EPEL on Redhat/CentOs 6 and 7 #196
Comments
|
Some details about this
|
|
@gene1wood You can submit the PR for this :) |
gene1wood
added a commit
to gene1wood/puppet-python
that referenced
this issue
Jun 13, 2015
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, apologies for opening this issue. There's an existing issue #115 which begins to describe this bug. I'm opening this issue because conversation on #115 has been restricted to contributors by @shivapoudel (which is of course totally fine).
@shivapoudel would it be possible to add a comment to that issue to indicate the status of any efforts to fix that bug or what people should do who use RHEL/CentOS? From the comments in that issue I wasn't able to determine why the conversation had been restricted (there may be background to this issue I'm unaware of).
To clarify the problem (which isn't very specific in #115), under RHEL/CentOS 7, attempting to install python-pip with a stanza like this
will fail because the system package that this puppet module calls for isn't part of the base RHEL/CentOS packages, but instead part of EPEL.
A solution to this problem (which I'll try to PR) would be to include the stahnma-epel puppet module as a dependency in the metadata.json. The nice thing about the
stahnma-epelpuppet module is that it only takes effect on RHEL derivatives and does nothing on other operating systems.The text was updated successfully, but these errors were encountered: