Red Hat Bugzilla – Bug 1300459
atomic v1.8.0 makes egg-info a file v/s a directory in v1.6
Last modified: 2016-03-31 19:25:42 EDT
Description of problem:
$ rpm -q atomic
$ ls /usr/lib/python2.7/site-packages/atomic-1.6-py2.7.egg-info/
dependency_links.txt PKG-INFO requires.txt SOURCES.txt top_level.txt
on updating to 1.8.0...
$ rpm -q atomic
$ cat /usr/lib/python2.7/site-packages/atomic-1.8-py2.7.egg-info
Author: Daniel Walsh
Version-Release number of selected component (if applicable): atomic-1.8-4.git958d939.el7.x86_64
This causes the rpmdiff error here: https://errata.devel.redhat.com/rpmdiff/show/137813?result_id=3559740
Brent could you take a look at this?
Lets remove it and leave it in site-library for now. Allowing users to do a
Is not a bad thing.
Here is a patch to remove it after it is installed.
I tried to figure out a way to simply not install it in the first place, but I did not find anything obvious. If any setup.py experts have a way to tell setup not to create the file, that would be a better solution.
The egg-info file has been removed from atomic-1.8-6.
[cloud-user@atomic-00 ~]$ rpm -q atomic
[cloud-user@atomic-00 ~]$ ls /usr/lib/python2.7/site-packages/atomic-1.8-py2.7.egg-info
ls: cannot access /usr/lib/python2.7/site-packages/atomic-1.8-py2.7.egg-info: No such file or directory
(In reply to Alex Jia from comment #12)
> The egg-info file has been removed from atomic-1.8-6.
> [cloud-user@atomic-00 ~]$ rpm -q atomic
> [cloud-user@atomic-00 ~]$ ls
> ls: cannot access
> /usr/lib/python2.7/site-packages/atomic-1.8-py2.7.egg-info: No such file or
yes, that's expected behavior as per the latest commit
(In reply to Lokesh Mandvekar from comment #13)
> > /usr/lib/python2.7/site-packages/atomic-1.8-py2.7.egg-info: No such file or
> > directory
> yes, that's expected behavior as per the latest commit
Yes, I see, is it enough for your? need I to double verify it use rpmdiff/rpmdiff-cli? it seems we only have a rpmdiff for el7sed version w/o single el7 version.
Per comment 12 and comment 13, move the bug to VERIFIED status.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.