pip uses the wrong package
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Inspect the package-name selection behind Class[Python::Install] and Package[pip], then reproduce the shown versioned invocation. Done means pip resolves to the version-matched package, such as python27-pip, when that package exists, without changing unrelated package selections.
Written by the indexing model from the issue text.
Description
when using the default provider and changing the version, pip is still installed as either python-pip or python3-pip. For example, in this invocation to install python from ius:
class { 'python':
ensure => 'present',
version => 'python27',
pip => 'present',
dev => 'present',
virtualenv => 'present',
use_epel => false,
}
you get this debug output:
Debug: Executing: '/bin/rpm -q python27 --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/bin/rpm -q python27 --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Notice: (/Stage[main]/Python::Install/Package[python]/ensure) current_value purged, should be present (noop)
Debug: (/Stage[main]/Python::Install/Package[python]) The container Class[Python::Install] will propagate my refresh event
Debug: Executing: '/bin/rpm -q python27-virtualenv --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/bin/rpm -q python27-virtualenv --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Notice: (/Stage[main]/Python::Install/Package[virtualenv]/ensure) current_value purged, should be present (noop)
Debug: (/Stage[main]/Python::Install/Package[virtualenv]) The container Class[Python::Install] will propagate my refresh event
Debug: Executing: '/bin/rpm -q python-pip --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/bin/rpm -q python-pip --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Notice: (/Stage[main]/Python::Install/Package[pip]/ensure) current_value purged, should be present (noop)
Debug: (/Stage[main]/Python::Install/Package[pip]) The container Class[Python::Install] will propagate my refresh event
Debug: Executing: '/bin/rpm -q python27-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/bin/rpm -q python27-devel --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Notice: (/Stage[main]/Python::Install/Package[python-dev]/ensure) current_value purged, should be present (noop)
Debug: (/Stage[main]/Python::Install/Package[python-dev]) The container Class[Python::Install] will propagate my refresh event
Debug: Executing: '/bin/rpm -q python-gunicorn --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
Debug: Executing: '/bin/rpm -q python-gunicorn --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
Debug: (/Stage[main]/Python::Install/Package[gunicorn]) Nothing to manage: no ensure and the resource doesn't exist
python, devel and virtualenv all have the right package, but pip's is wrong. gunicorn's is also wrong, but there's no python27-gunicorn in ius, so I'm, less worried about that.
- Dominant language
- Ruby
- Stars
- 196
- Forks
- 372
- Avg merge
- 1d 18m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voxpupuli/puppet-python
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
voxpupuli/puppet-python#743 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
voxpupuli/puppet-python#721 · 1 reaction ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
voxpupuli/puppet-python#712 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
voxpupuli/puppet-python#711 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
voxpupuli/puppet-python#673 · 1 comment ·
All issues in voxpupuli/puppet-python
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100