RFC: best way to fix the regular yum dependency problems with add-on packages from 3rd party repositories

[Thorsten Leemhuis]

On 02.08.2008 16:34, John Ellson wrote:
> Thorsten Leemhuis wrote:
>> On 02.08.2008 15:41, John Ellson wrote:
>>> Thorsten Leemhuis wrote:
>>> Neither of these dependency issues is flagged in: "rawhide report:
>>> 20080802 changes"
>>> It would really help if yum would automatically skip any rpm that
>>> conflicted with any *installed* rpm.  Both for Rawhide and 
>>> third-party rpms.
>>>     $ yum update phonon*
>>>     Error: Missing Dependency: phonon = 4.2.0-1.fc10 is needed by 
>>> package phonon-backend-gstreamer-4.2.0-1.fc10.x86_64 (installed)
>> Look closer! It says "[...] (installed)" there -- the scripts that 
>> generates the rawhide report can't know what you have one your 
>> harddisk and thus it can't detect this broken dep.
> But (1) the rawhide reports do know what is in the rawhide repository 
> that might be installed, and which shouldn't conflict if they are.

I can't follow, sorry. As mentioned already, phonon-backend-gstreamer 
isn't in rawhide anymore. Yes, it once was, but you can't expect the 
script to check all "was once in rawhide" packages, as the script then 
would take ages to complete.

But whatever; Rex fixed it afaics, so this specific problem should 
vanish today.

> But (2) I suggested that yum, on the client, should automatically skip 
> over new rpms (and and new rpms that depend on the new rpm)
> that conflict with an installed rpm. 

But especially in rawhide this bug must be fixed. If users don't notice 
it it will never be fixed, which would lead to a Fedora which is worse 
in the end.

 > [...]
>> Further: Looking for file conflicts in all packages is a very 
>> time-consuming task -- it takes many hours iirc and thus to long to do 
>> it for each rawhide push. In the old Fedora Extras days mschwendt iirc 
>> had a script that did such checks that; he started it now and then 
>> manually. But this script just like a lot of other (semi-)automatic 
>> check scripts from Extras afaics one got lost/forgotten during the 
>> Core and Extras merge. :-((
> Fine.  Don't check it on the server.  Just have yum on the client 
> recover gracefully from these and skip over them.
> That would also solve the livna problem.

Feels to me like a car where that is oxidizing all over the place. Yeah, 
you go out and by a new parts for the car body. It then will look good 
on a first sight again, but the car structure will continue to rust; 
sooner or later it will fall apart might do damage then.

CU
knurd