Bug 789777

Summary: Please update python-alsa along to match others alsa components
Product: [Fedora] Fedora Reporter: Nicolas Chauvet (kwizart) <kwizart>
Component: python-alsaAssignee: Gwyn Ciesla <gwync>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gwync, jkysela
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-alsa-1.0.25-1.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-22 01:59:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nicolas Chauvet (kwizart) 2012-02-12 22:33:26 UTC
Description of problem:
a New version of alsa-* was updated by perex, but not python-alsa.

  
Actual results:
python-alsa-1.0.24 is in F-16 and later despite alsa-lib-1.0.25 will hit the f16 stable repo soon.

Expected results:
update python-alsa to 1.0.25 for f16 and later.

Additional info:

Comment 1 Gwyn Ciesla 2012-02-13 13:17:10 UTC
I wasn't aware 25 was going to go to f16, but thanks for the heads up.  I can't build python-alsa 25 until alsa hits stable.  If there's a way to do this while it's in updates-testing that I've forgotten please let me know.

Comment 2 Nicolas Chauvet (kwizart) 2012-02-13 14:23:41 UTC
You can request a buildroot overrides:
http://fedoraproject.org/wiki/Bodhi/BuildRootOverrides

Perex might help if there is a special ACL needed to tag alsa-lib in overrides.

Comment 3 Gwyn Ciesla 2012-02-13 14:39:39 UTC
Which build do I specify?  The old alsa-lib, the new alsa-lib?  Neither works.

Comment 4 Jaroslav Kysela 2012-02-13 14:47:44 UTC
The alsa-lib-1.0.25 build is in expired ones (second page). You need to enter new expiration date there to re-activate it.

Comment 5 Gwyn Ciesla 2012-02-13 15:00:59 UTC
I extended it to 2/14, but the build still failed, is there a delay?

Comment 6 Jaroslav Kysela 2012-02-13 15:07:33 UTC
Yes, I think 30 minutes.

Comment 7 Gwyn Ciesla 2012-02-13 15:49:34 UTC
That worked, thanks!

Comment 8 Fedora Update System 2012-02-13 15:52:03 UTC
python-alsa-1.0.25-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/python-alsa-1.0.25-1.fc16

Comment 9 Fedora Update System 2012-02-14 09:10:47 UTC
Package python-alsa-1.0.25-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-alsa-1.0.25-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1639/python-alsa-1.0.25-1.fc16
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2012-02-22 01:59:03 UTC
python-alsa-1.0.25-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.