Re: Using yum to update livna nvidia packages?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2005-03-15 at 20:19 -0600, Jeff Vian wrote:
> Yum by default does an install on new kernels and modules.  That is so
> it does not break the existing installation.
> 
> However, as Paul has stated, other packages are not installed but
> upgraded. (The older package is removed)
> 
> I would be willing to guess that using Paul's procedure it will work or
> you simply might try
>      yum install kernel-module-nvidia.....  nvidia-glx.....  
> with the matching 7167 version numbers and it should work.
> You might need to use a force or nodeps option.
> 
> This might be a failed dependency configuration of the nvidia-glx
> package and since that comes from livna the issue at that point would
> need to be addressed to Axel there.
> 
> As I said above, it may be a packaging issue.  That would need to be
> addressed to the packager directly,  Livna.

Thanks, Jeff.

I've already added comments to this bug:

http://bugzilla.livna.org/show_bug.cgi?id=385

You and Paul are bringing me round to the idea that "yum install" is
what is needed, but I think that is a failure in yum. Or, it could be a
packaging bug. But I don't think a user, especially one who is not as
experienced as I am (I've been using GNU/Linux for years, I'm a web
developer, etc.), should ever be confronted with this conundrum:

$ sudo yum list updates
[snip]
Updated Packages
kernel-module-nvidia-2.6.10-1.770_FC3.i6 1.0.7167-0.lvn.1.3     livna-testing
nvidia-glx.i586                          1.0.7167-0.lvn.1.3     livna-testing

$ sudo yum update
[snip]
Error: Unable to satisfy dependencies
Error: Package kernel-module-nvidia-2.6.10-1.770_FC3 needs nvidia-glx = 0:1.0.6629, this is not available.

Yum may be hard-coded to not update kernel modules, but that shouldn't
include a newer version of the *same* (i.e. built for exactly the same
kernel) module. Maybe the shortcoming is in rpm, maybe yum has no way of
telling what is a new version of an existing kernel module and what is a
kernel module for a totally different kernel. But whether the fault is
with yum or rpm it still needs an RFE. Now if I can just determine what
exactly is going on, I'm happy to do the honours. Yum RFE? RPM RFE? or
Livna packaging bug?

Suggestions welcome!

Best, Darren

-- 
=====================================================================
D. D. Brierton            darren@xxxxxxxxxxx          www.dzr-web.com
       Trying is the first step towards failure (Homer Simpson)
=====================================================================


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux