Amarok update path on kde-redhat

[Mary Ellen Foster]

I'm running Fedora 11 (preview/rawhide/whatever) on x86_64, with all
kde-redhat repositories enabled -- including the i386 ones because of
multilib issues. I've done all of the other (non-amarok) updates
today, and amarok is still being annoying ...

Right now, I get the following if I attempt to "yum update" (edited to
show the relevant bits):

================================================================================
 Package              Arch     Version              Repository             Size
================================================================================
Installing:
 amarok-utils         i586     2.0.96-1.fc11        kde-i386-unstable     148 k
     replacing  amarok-utilities.x86_64 2.0.90-2.fc11

Installing for dependencies:
 [ ... ]
 amarok-utilities     i586     2.0.90-2.fc11        kde-i386-unstable     142 k
 [ ... ]

If I disable the i386 repositories, I don't see any proposed updates,
even after a "yum clean all".

Is this a mirror issue? A multilib issue? What's the deal with
amarok-util[itie]s?

Thanks for any help,

MEF

[Eelko Berkenpies]

On Wed, 13 May 2009 10:32:06 +0100, Mary Ellen Foster 
wrote:
> I'm running Fedora 11 (preview/rawhide/whatever) on x86_64, with all
> kde-redhat repositories enabled -- including the i386 ones because of
> multilib issues. I've done all of the other (non-amarok) updates
> today, and amarok is still being annoying ...
>
> Right now, I get the following if I attempt to "yum update" (edited to
> show the relevant bits):

================================================================================
> Package              Arch     Version              Repository
> Size

================================================================================
> Installing:
>  amarok-utils         i586     2.0.96-1.fc11        kde-i386-unstable    
>  148 k
>      replacing  amarok-utilities.x86_64 2.0.90-2.fc11
>
> Installing for dependencies:
>  [ ... ]
>  amarok-utilities     i586     2.0.90-2.fc11        kde-i386-unstable    
>  142 k
>  [ ... ]
>
> If I disable the i386 repositories, I don't see any proposed updates,
> even after a "yum clean all".
>
> Is this a mirror issue? A multilib issue? What's the deal with
> amarok-util[itie]s?

amarok-utl[itie]s hold the collection scanner since it got separated in
Amarok 2.1. Furthermore I don't know what kind of strangeness is going on
for you and why an older version of utils is being pulled in for
dependencies.

I can only say that amarok-2.0.90 is Amarok 2.1 beta 1 and amarok-2.0.96 is
Amarok 2.1 beta 2 but you probably figured that out already. :)
> Thanks for any help,
>
> MEF
>
> -- 
> Mary Ellen Foster  --  http://homepages.inf.ed.ac.uk/mef/
> ICCS, School of Informatics, University of Edinburgh
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.

[Mary Ellen Foster]

2009/5/13 Eelko Berkenpies :
> amarok-utl[itie]s hold the collection scanner since it got separated in
> Amarok 2.1. Furthermore I don't know what kind of strangeness is going on
> for you and why an older version of utils is being pulled in for
> dependencies.
>
> I can only say that amarok-2.0.90 is Amarok 2.1 beta 1 and amarok-2.0.96 is
> Amarok 2.1 beta 2 but you probably figured that out already. :)

Well, on looking closer at the actual update transaction, it seems
that there's no amarok-2.0.96 in the kde-unstable x86_64 repository,
but there is one in kde-unstable i586. So that's what's causing the
weird update transaction. I'll temporarily blame this on mirror issues
and hope that it fixes itself soon ...

... and one "yum clean metadata" later, it looks like the 64-bit
Amarok is indeed now there. Sorry for the noise.

MEF

[Rex Dieter]

Mary Ellen Foster wrote:
> 2009/5/13 Eelko Berkenpies :
> > amarok-utl[itie]s hold the collection scanner since it got separated in
> > Amarok 2.1. Furthermore I don't know what kind of strangeness is going on
> > for you and why an older version of utils is being pulled in for
> > dependencies.
> >
> > I can only say that amarok-2.0.90 is Amarok 2.1 beta 1 and amarok-2.0.96 is
> > Amarok 2.1 beta 2 but you probably figured that out already. :)
>
> Well, on looking closer at the actual update transaction, it seems
> that there's no amarok-2.0.96 in the kde-unstable x86_64 repository,
> but there is one in kde-unstable i586. So that's what's causing the
> weird update transaction. I'll temporarily blame this on mirror issues
> and hope that it fixes itself soon ...
>
> ... and one "yum clean metadata" later, it looks like the 64-bit
> Amarok is indeed now there. Sorry for the noise.

All builds are there now, apparently you hit the repo when it was only 
partially updated for amarok-2.0.96 builds.

-- Rex