Looks like a multilib goof on your box.  Why is only the x86_64 version trying
to update and not i386?

Don't know.  My installation is vanilla and I only install from the Fedora and
Livna repositories.

I went ahead and uninstalled amarok and re-installed.  That cleared the problem.

Created attachment 297296 [details]
Yum transaction

Yum transaction for yum update and yum update amarok.
Yum update will not update amarok.i386, which causes the transaction check
error.

As the 32-bit package is available and yum is not trying to update it, there
must be some multilib bug in yum.

nod, saw someone else mention this on fedora list reopening

multilib joy.

what command were you running. Please report the output of the command.

also run:

yum list updates

and

yum list installed

thanks

Created attachment 297305 [details]
Yum list updates

Created attachment 297306 [details]
Yum list installed

Created attachment 297307 [details]
Yum update

Running
  # yum update
results in crash as stated before (64-bit amarok-konqueror seems to replace
32-bit amarok), but
  # yum update amarok
succesfully updates both 32- and 64-bit versions of amarok; after this yum
update is run succesfully.

This is the output of yum update amarok:

Loading "downloadonly" plugin
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package amarok.i386 0:1.4.8-4.fc8 set to be updated
---> Package amarok.x86_64 0:1.4.8-4.fc8 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Updating:
 amarok                  i386       1.4.8-4.fc8      updates            13 M
 amarok                  x86_64     1.4.8-4.fc8      updates            13 M

Transaction Summary
=============================================================================
Install      0 Package(s)         
Update       2 Package(s)         
Remove       0 Package(s)         

Total download size: 27 M
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Updating  : amarok                       ######################### [1/4] 
  Updating  : amarok                       ######################### [2/4] 
  Cleanup   : amarok                       ######################### [3/4] 
  Cleanup   : amarok                       ######################### [4/4] 

Updated: amarok.i386 0:1.4.8-4.fc8 amarok.x86_64 0:1.4.8-4.fc8
Complete!

sigh. So you've already changed your system? There's no way to ask for more
debugging information to see if we can solve this problem?

then I'll close this cantfix as I need to see more information.

amarok recently grew an amarok-konqueror subpkg, and in a naive attempt to ease
upgrade-path issues, we included in amarok-konqueror:
Obsoletes: amarok < 1.4.8-4
which is what I'd bet is contributing to the issue here.

A couple of more questions:

What are these packages? What do they provide or do?

yum-dribble.noarch                       1-1_tfo                installed       
yum-ftl.noarch                           2-4_fc_ftl             installed       

obsoletes are processed before updates.

so the x86_64 pkg was obsoleted and yum thought so was the i386, most likely,
the amarok-konqueror package pulled in the new amarok.x86_64 but not the
amarok.i386.

So then the transaction ran, rpm only pulled out the x86_64 amarok and we're
left with the file conflict.

I'm not sure that this is an obsolete problem.

Beyond being hit by the Amarok problem (that was solved by removing the
offending packages and reinstalling them), I saw the same (?) multi-lib problem
(hours later) when I tried to install fontconfig-devel.i386 and
libxslt-devel.i386. (64bit were already installed; needed the 32bit ones to
build wine)

$ yum install fontconfig-devel.i386 libxslt-devel.i386
... And got file conflicts on more-or-less all the files in both packages.
(Didn't save the output, a mistake, I know, sorry)

Only when I executed the following:
$ rpm -e fontconfig-devel libxslt-devel --nodeps
$ yum -y install fontconfig-devel libxslt-devel
fontconfig-devel - 2.4.2-5.fc8.x86_64
fontconfig-devel - 2.4.2-5.fc8.i386
libxslt-devel - 1.1.22-1.fc8.i386
libxslt-devel - 1.1.22-1.fc8.x86_64

... Everything returned to normal.

- Gilboa

"""
$ yum install fontconfig-devel.i386 libxslt-devel.i386
... And got file conflicts on more-or-less all the files in both packages.
(Didn't save the output, a mistake, I know, sorry)
"""

 This is a known (different) rpm feature, we can't fix it in yum. If you have
file conflicts rpm will handle it in a special way if you install them both at once.

(In reply to comment #16)
> A couple of more questions:
> 
> What are these packages? What do they provide or do?
> 
> yum-dribble.noarch                       1-1_tfo                installed       
> yum-ftl.noarch                           2-4_fc_ftl             installed       

Those are just local repo packages, they only contain some binary software used
at our site.

As Rex said the "Obsoletes: amarok" tag in amarok-konqueror is behind this
problem. The right way to solve this would probably be to remove the Obsoletes
tag from amarok-konqueror and add an "Requires: amarok-konqueror" tag to amarok.

Jussi

> add an "Requires: amarok-konqueror"

No, that's the whole point of having the pkg split, to avoid the konq dependency
that pulls in all of kdebase.

I'll consider omitting the Obsoletes tag, but I'll wait to hear what Seth (or
any other yum guru) has to say on the matter.

Wait, this got closed, multilib transation errors are considered NOTABUG?

it got closed notabug b/c it isn't a yum bug, afaict.

OK, then we can't use the Obsoletes in amarok to provide a preferred upgrade path.

Reassigning -> amarok

amarok-1.4.8-5.fc8 has been submitted as an update for Fedora 8

amarok-1.4.8-5.fc8 has been pushed to the Fedora 8 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 amarok'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-2410

(In reply to comment #24)
> OK, then we can't use the Obsoletes in amarok to provide a preferred upgrade 
path.

Then, what is the correct solution, so that a package split does not remove 
some part of the initial package?

Re: comment #28
Unfortunately, I'm not aware of any correct solution to the problem(*).


(*) Besides using Obsoletes, which landed us here with multilib transaction
errors, which is apparently not fixable (ie, not a yum bug per comment #23).

amarok-1.4.8-5.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.