Bug 790527

Summary: alsa-utils update breaks dependencies
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: alsa-utilsAssignee: Jaroslav Kysela <jkysela>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: apodtele, collura, ian, jgotts, jkysela, leonid
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: 2012-02-15 07:32:13 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 Michal Jaegermann 2012-02-14 18:49:07 UTC
Description of problem:

alsa-utils-1.0.25-7.fc16, with a signature date "Wed 01 Feb 2012", showed up in updates for Fedora 16.  Unfortunately this requires "alsa-lib >= 0:1.0.25" which is not available.

BTW - x86_64 repositories would need both x86_64 and i686 updates to alsa-lib before all of this will get consistent.

Version-Release number of selected component (if applicable):
alsa-utils-1.0.25-7.fc16

Comment 1 collura 2012-02-14 22:16:27 UTC
the actual transaction error text was 

"alsa-utils-1.0.25-7.fc16.x86_64 requires alsa-lib >= 1.0.25 : Success - empty transaction"

(interestingly if i remember right i had the package install with no problems on a updates-testing enabled machine but fail when tried on a stable machine of similar build.)

Comment 2 Michal Jaegermann 2012-02-14 22:53:34 UTC
(In reply to comment #1)
> 
> (interestingly if i remember right i had the package install with no problems
> on a updates-testing enabled machine but fail when tried on a stable machine of
> similar build.)

My guess would be that updates-testing had all required library packages, and updates to everything which would be affected by a change, but somebody jumped a gun and pushed out only a small piece of that without checking thus breaking dependencies.

Comment 3 Michal Jaegermann 2012-02-14 22:59:20 UTC
(In reply to comment #1)
> the actual transaction error text was 
> 
> "alsa-utils-1.0.25-7.fc16.x86_64 requires alsa-lib >= 1.0.25 : Success - empty
> transaction"

Oh, BTW, on a command line with yum I actually got this:

Error: Package: alsa-utils-1.0.25-7.fc16.x86_64 (updates-local)
           Requires: alsa-lib >= 1.0.25
           Installed: alsa-lib-1.0.24-2.fc15.i686 (@fedora)
               alsa-lib = 1.0.24-2.fc15
 You could try using --skip-broken to work around the problem

I actually have both alsa-lib-1.0.24-2.fc15.x86_64 and alsa-lib-1.0.24-2.fc15.i686 installed; the later needed by something like skype.

Comment 4 Jaroslav Kysela 2012-02-15 07:32:13 UTC
The alsa-lib 1.0.25 package is in the update repository now.

Comment 5 David Juran 2012-02-15 12:09:25 UTC
*** Bug 790718 has been marked as a duplicate of this bug. ***

Comment 6 Alexei Podtelezhnikov 2012-02-15 12:44:02 UTC
next time push them together.
look how KDE team pushes the whole thing coming from multiple SRPMs.
it is possible to join updates and avoid this embarrassment.