[BUG] `OSpackages.sh` script's `-g` Feature Does Not Properly Handle Groups Other Than `core`
Open
Nobody has claimed this yet.
bug
- Dominant language
- Shell
- Stars
- 10
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
If attempting to use a different yum RPM-group to build an other-than-core image, the OSpackages.sh script will fail.
Expected behavior
Custom builds using arbitrary repository-defined RPM-groups other than the @core group should work
Deviance Description
Custom builds using arbitrary repository-defined RPM-groups other than the @core group does not work
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
Start with OSpackages.sh and trace how the -g argument is translated into a yum RPM-group when building a non-core image. Reproduce the failure with a repository-defined group other than @core, then verify that custom builds complete successfully for arbitrary groups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100