| Summary: | Update mutagen to latest version | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | hannes <johannes.lips> |
| Component: | python-mutagen | Assignee: | Michele Baldessari <michele> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | i, michele, moez.roy, rnovacek, silas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-01 18:39:40 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
hannes
2016-03-25 07:58:02 UTC
I could offer co-maintainership, I think a git merge master for f23 should be enough or are there any downsides? Thanks again. F24 is in alpha already. Why can't we just do it there? I tend to avoid updating packages in a stable release unless there is a concrete bug/issue. I already did it for f24, but given that f23 will be there for at least half a year. I don't want to maintain too many different version, which could lead to the need of backports etc. I don't think there really is an issue, when updating python-mutagen even in a stable release. Thanks. |