Bug 567627
| Summary: | broken upgrade paths | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Schmidt <mschmidt> |
| Component: | alsa-lib | Assignee: | Jaroslav Kysela <jkysela> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | genes1122, h1k6zn2m, jkysela |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | alsa-lib-1.0.23-1.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-04-25 13:47:34 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 Schmidt
2010-02-23 13:39:50 UTC
In other words: Why is alsa-lib-1.0.22-hwparams.patch only in F-12 but not in F-13 and Rawhide? Are people upgrading to F-13 going to see a regression? Also notice that yesterday FESCo approved a policy for updates which contains the requirement "Packages must not break upgrade path": http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/fesco.2010-03-16-19.00.html https://fedoraproject.org/wiki/UpdatePolicy%28draft%29#notting.27s_Proposal I've been waiting for this to be resolved for quite a while, now. Think it should be a blocker? Gene (In reply to comment #1) > In other words: Why is alsa-lib-1.0.22-hwparams.patch only in F-12 but not in > F-13 and Rawhide? Are people upgrading to F-13 going to see a regression? I took a look at the patch to find out what it's for. This is my understanding: - Fedora 12 was released with alsa-lib-1.0.21. - Fedora 12 later received alsa-lib-1.0.22 as an update. The update fixed bugs, but it also introduced a regression (bug 553497). - The regression was caused by a behaviour change listed in the upstream release notes as "PCM - Change the hw_params determination order". Upstream suspected the change might cause trouble for some apps, so they also introduced the possibility to select the old behaviour using the environment variable LIBASOUND_COMPAT. - (Just guessing:) Jaroslav decided that bringing this change within a stable Fedora release was not a good idea. - So he added alsa-lib-1.0.22-hwparams.patch to the F-12 branch. It brings back the old behaviour by default and only allows the new behaviour to be used if the user explicitly asks for it. - (Guessing further:) Jaroslav did not add this patch to F-13 intentionally, because the new behaviour is good in general and apps should be just fixed to work with it. So the guideline https://fedoraproject.org/wiki/Packaging/NamingGuidelines#Minor_release_bumps_for_old_branches should have been followed in the F-12 branch. alsa-lib-1.0.22-hwparams.patch should NOT be forward ported to F-13. Instead, alsa-lib should be rebuilt in F-13 with a release tag increased (to at least "3") and no other changes. This will fix the upgrade path. Jaroslav, I can do minor fixes like this if you approve my ("michich") commit access in Fedora pkgdb: https://admin.fedoraproject.org/pkgdb/acls/name/alsa-lib alsa-lib-1.0.23-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc12 alsa-lib-1.0.23-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc11 alsa-lib-1.0.23-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc13 I'm sorry that it took too long to solve this issue, but I though that alsa-lib 1.0.23 release will be available more quickly :-) This problem was minor in my eyes, because the alsa-lib configuration is similar for F11-F13 (except the hwparams patch which affects applications in very specific cases). Michal, you have ACL rights for alsa-lib now for future. Thanks. alsa-lib-1.0.23-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update alsa-lib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc12 alsa-lib-1.0.23-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update alsa-lib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc13 alsa-lib-1.0.23-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update alsa-lib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/alsa-lib-1.0.23-1.fc11 alsa-lib-1.0.23-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. alsa-lib-1.0.23-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. alsa-lib-1.0.23-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |