[ATrpms-users] Can't upgrade to ivtv-1.2.0-140.fc8

[Axel Thimm]

On Wed, Sep 03, 2008 at 09:48:57AM -0400, Kevin J. Cummings wrote:
> Axel Thimm wrote:
> > On Mon, Aug 25, 2008 at 04:30:52PM -0400, Kevin J. Cummings wrote:
> >> Could someone please explain to me what the difference is between 
> >> video4linux and video4linux-ivtv stuff please?
> > 
> > video4linux was split between a package of the same name and the ivtv
> > components so people could choose where to get ivtv from (while the
> > same author, ivtv from ivtvdriver.org and v4l were really desynced and
> > sometimes one would be better than the other).
> > 
> > These days you should preferably use what the kernel >= 2.6.26 ships
> > with.
> 
> I was under the impression that the ivtv package contained the user 
> utilities, and that the ivtv-kmdls contained the PVR-350 framebuffer 
> stuff, and that I was using the ivtv driver proper from the installed 
> kernel.  Am I wrong?

That was true until kernel 2.6.something, then ivtv-kmdl contained
saa717x. That was no packaging decision, but closely following
upstream.

So today on kernel < 2.6.26 (e.g. F9, F8, but not F10) you need (if
you have the matching hardware) saa717x, otherwise you don't need any
*ivtv-kmdl.

> >> And does it have anything to do with why I can't update my F8 system 
> >> with the new ivtv-1.2.0-140:
> > 
> >>> Transaction Check Error:
> >>>   file /lib/modules/2.6.25.14-69.fc8/updates/drivers/media/video/saa717x.ko from install of ivtv-kmdl-2.6.25.14-69.fc8-1.2.0-140.fc8.i686 conflicts with file from package video4linux-kmdl-2.6.25.14-69.fc8-20080622-86.fc8.i686
> > 
> > See above, you can't have both. There should probably be an explicit
> > package level conflict to document this.
> 
> But, how do I fix this?

Do you need video4linux? ATM you can't have both.

> yum check-update tells me that an update of ivtv is waiting.  From what 
> I can see, I have ivtv-fedora installed on my system (from the version 
> number).  I have no idea why it is installed vs the "regular" ivtv, but 
> it is.  yum want to update it with the "regular" ivtv.  I have had no 
> problems updating this in the past, but now I do.  Why?  And how do I 
> fix this?  Please note that I did not try and install ivtv-kmdl in my 
> update, I believe that the yum-plugin-kmdl is trying to install it for me.
> 
> (Maybe its just the software engineer in me wanting to understand what 
> is broken, and why is it broken, so I can fix it correctly.)

I like the software engineer in you :)

No, really, there are issues with ivtv floating from ivtvdriver.org to
v4l repo and finally to the kernel itself, and if you have a
particular set of mixed hardware that needs both ivtv-kmdl and devices
that are supported in v4l, but not the kernel, yet, you do run into
these conflicts (package and upstream wise).

I could fix the package issue by choosing one over the other, but I
have no idea what kind of hardware mix people use.

Ideally with F10 (kernel 2.6.27) there will be no ivtv-kmdl anymore,
which is the "Fedora" version, which I submitted for Fedora inclusion.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20080903/839f42bd/attachment-0001.bin