Bug 474956
Summary: | yum gets deprecation complaints after a Python update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | yum | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | ffesti, james.antill, jonstanley, katzj, pmatilai, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-07 18:35:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2008-12-06 01:50:11 UTC
I can fix the first two as soon as I know how to. The next two are already fixed, and will go into rawhide "soon". As you say the last isn't yum. triaged > As you say the last isn't yum.
So do I have to file another one for python-iniparse or I should not bother?
I would just so they know about it, I was about ready to file one for you (I didn't see one against python-iniparse) The sqlitesack ones are now fixed in upstream: 2310e48492bca17a9439d0ea834d9e0dd9caf049 |