Bug 1300459
Summary: | atomic v1.8.0 makes egg-info a file v/s a directory in v1.6 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Lokesh Mandvekar <lsm5> |
Component: | atomic | Assignee: | Brent Baude <bbaude> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.2 | CC: | ajia, dwalsh, walters |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | atomic-1.8-5.git1bc3814 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-31 23:25:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lokesh Mandvekar
2016-01-20 22:00:35 UTC
Brent could you take a look at this? Lets remove it and leave it in site-library for now. Allowing users to do a import Atomic Is not a bad thing. Here is a patch to remove it after it is installed. https://github.com/projectatomic/atomic/pull/291 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 atomic-1.8-6.git1bc3814.el7.x86_64 [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 > atomic-1.8-6.git1bc3814.el7.x86_64 > [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 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. https://rhn.redhat.com/errata/RHBA-2016-0527.html |