voxpupuli / voxpupuli/puppet-python
Installing specific version of python
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 196
- Forks
- 372
- Avg merge
- 1d 18m
- Merged PRs (30d)
- 4
Description
Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 6.14
- Ruby: 2.5.1
- Distribution: Puppet Server - Ubuntu 18.04, Puppet Node - Amazon Linux 2
- Module version: 4.0.0
How to reproduce (e.g Puppet code you use)
Simply set the version to a specific yum package in the form name-epoch:ver-rel.arch (3-0:3.7.4-1.amzn2.0.4.x86_64)
What are you seeing
If i check my configured repository if have the following python3 versions available.
repoquery --show-duplicates python3
python3-0:3.7.4-1.amzn2.0.3.i686
python3-0:3.7.4-1.amzn2.0.3.x86_64
python3-0:3.7.4-1.amzn2.0.4.i686
python3-0:3.7.4-1.amzn2.0.4.x86_64
python3-0:3.7.6-1.amzn2.0.1.i686
python3-0:3.7.6-1.amzn2.0.1.x86_64
Locally running "yum install python3-0:3.7.4-1.amzn2.0.4.x86_64" installs the version i specify.
However when using the version parameter of this puppet module it only supports the first number of the version string.
So if configure a version parameter of
3-0:3.7.4-1.amzn2.0.4.x86_64
It simply reads the "3" at the start and ignores everything else.
Therefore the actual package installed by yum is just python3
What behaviour did you expect instead
Ability to support package versions other than default repo latest versions.
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.
Research direction
No source file or test is named. Start by reproducing the version parameter behavior with the shown yum package on Amazon Linux 2, then trace how the Puppet module passes that parameter to yum. Done means a specific package version such as 3-0:3.7.4-1.amzn2.0.4.x86_64 is installed instead of only the package name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ruby
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100