Re: xine, xine-lib-moles, etc...

Troy Engel wrote :

> Drew Bertola wrote:
> > 
> > I'm having a problem installing xine because I'm getting a complaint:
> 
> It's something in the repository, we'll have to wait for it to get 
> fixed. I just encountered the error myself doing a yum upgrade.
> 
> BTW to all: there's a new yum module/RPM you can install to skip broken 
> packages when upgrading: yum-skip-broken. When encountering problems 
> like this xine you can 'yum upgrade --skip-broken' and keep on going, 
> sidestepping the upstream repository problem.

It's more of a "new" situation which will need to be sorted out. I
can't think of any easy way to do so, though. Until now, only Core
packages went through "updates-testing" before the main "updates",
and Extras was a moving target, and Extras was where most of the
multimedia libraries were. So when a new lib was pushed to Extras, I
just rebuilt dependant packages ASAP, and that was it.

But now, xine-lib 1.1.7 is in "updates-testing", which I have enabled
on all my F7 systems, and many other users seem to do it too (for
experienced users, it can only be a good thing in order to help catch
bugs before they hit the main updates!). So I rebuilt xine-lib-moles
against 1.1.7, which will appear "broken" when "updates-testing" isn't
enabled, until xine-lib 1.1.7 hits "updates".

One solution would be to encourage all freshrpms users to enable
"updates-testing". Another would be to have a new "freshrpms-testing"
repo, synced with "updates-testing". But that means more work for me,
and matching the Fedora pushes from "updates" to "updates-testing"
can't be done perfectly anyway...

I'm open to more suggestions ;-)

A current workaround should be :
yum --enablerepo=updates-testing update xine-lib

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.21-1.3194.fc7
Load : 0.65 0.93 0.76