egg-info directory is created but not owned by RPM
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
We have 2 different build machines with setuptools 19.7 and 20.0 installed
Both the RPMs created using 'setup.py bdist_rpm' creates the egg-info directories when installed.
But cleanup doesn't delete the egg-info directory for the RPM created using setuptools 20.0
We don't see this issue with RPM created with 19.7
The reason seems to be that the egg-info directory is not owned by RPM when created using 20.0 version
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
Reproduce the issue with setup.py bdist_rpm using setuptools 19.7 and 20.0. Compare the generated RPM contents and installation cleanup, focusing on whether the egg-info directory is owned by the RPM. Done means the setuptools 20.0-built RPM handles the egg-info directory consistently with the 19.7-built RPM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100