| Summary: | Leftovers in /usr/lib{,64}/python3.4 after upgrading F23->F25 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vedran Miletić <vedran> |
| Component: | python3 | Assignee: | Charalampos Stratakis <cstratak> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | bkabrda, cstratak, mhroncok, pviktori, rkuska, tomspur, torsava |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-07 11:47:18 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: | |
|
Description
Vedran Miletić
2016-08-23 14:49:09 UTC
Yes, individual bugs would be great -- these aren't caused by Python itself. You can use this as a tracker, though (i.e. set the other bugs as Blocking this one). As Python maintainers we can of course help in fixing this, if requested. The files in __pycache__ should be part in their respective RPMs, so they're not generated on import. Don't know about the other files. If they're available at RPM build time, they should be packaged. I believe the update process should have been F23->F24->F25? Maybe the issue was that. I will try to replicate it. So now I realize it is about various different packages. The bug should be filled for dnf firstly, although I believe upgrading at once through two releases is not supported. (In reply to Petr Viktorin from comment #1) > Yes, individual bugs would be great -- these aren't caused by Python itself. > You can use this as a tracker, though (i.e. set the other bugs as Blocking > this one). > > As Python maintainers we can of course help in fixing this, if requested. > > The files in __pycache__ should be part in their respective RPMs, so they're > not generated on import. > Don't know about the other files. If they're available at RPM build time, > they should be packaged. Will do. (In reply to Charalampos Stratakis from comment #2) > I believe the update process should have been F23->F24->F25? > > Maybe the issue was that. I will try to replicate it. Not anymore. Since F22 we support upgrade n->n+2. |