perfsonar / perfsonar/perl-shared
RPM build process improvement
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In the psrpm_build_perl script, when the build machine has been already used to build previous versions of RPM, only the very first src.rpm is picked up by psrpm_mock /home/vagrant/rpmbuild/SRPMS/${PACKAGE}*.src.rpm at line 85. That any other newly build src.rpm present, but listed after the first one will never get build.
We should either clean all the /home/vagrant/rpmbuild/SRPMS/ directory before building the new src.rpm or call psrpm_mock with the exact src.rpm we just built before.
Contributor guide
No contributing guide indexed for this repository
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
Inspect the psrpm_build_perl script around line 85 and first reproduce the build with older files in /home/vagrant/rpmbuild/SRPMS/. Done means the newly built src.rpm is the one passed to psrpm_mock, or stale files are removed before the build; verify that every newly built src.rpm is processed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100