Re: Using yum to update livna nvidia packages?

From: Jeff Vian (jvian10_at_charter.net)
Date: 03/19/05

  • Next message: Ken Cooper: "Re: Trouble with fedora" 
    To: For users of Fedora Core releases <fedora-list@redhat.com>
Date: Fri, 18 Mar 2005 19:13:10 -0600

    On Wed, 2005-03-16 at 03:33 +0000, D. D. Brierton wrote:
    > 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.
    >

    I see the issue here. You already have kernel-module-nvidia for the
    6629 drive installed for the existing kernel 2.6.10-1.770. So when you
    install the new driver level for the same kernel it breaks the
    dependency for the nvidia-glx. You will need to do an uninstall of the
    old driver and an install of the new driver since they are for the same
    kernel level.

    > 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?
    >

    That would be 1) rpm related and 2) packager related.

    However, since a driver needs to be exactly one driver for that piece of
    hardware, then the rpm packager needs to do an uninstall of the existing
    driver as he installs the new driver.

    I would file that with Livna as a packaging issue. It needs to remove
    the old package, and everything else that depends on that package before
    it installs the new one.

    As I see it, the new kernel module is being installed, but that would
    break the related nvidia-glx package, so it also should remove the glx
    package as part of installing the new kernel module package.

    It still seems a packager issue since they apparently did not handle
    removing packages that depend on the module when upgrading the module.

    > Suggestions welcome!
    >
    > Best, Darren
    >
    > --
    > =====================================================================
    > D. D. Brierton darren@dzr-web.com www.dzr-web.com
    > Trying is the first step towards failure (Homer Simpson)
    > =====================================================================
    > 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Ken Cooper: "Re: Trouble with fedora"

    Relevant Pages

    • Re: Upgrading from old Sarge (Testing) to Unstable
      ... > The package I'm most concerned about upgrading is the kernel. ... If you installed it via the debian tools, ie. via a .deb package it will be found in the 'Obsolete and locally created packages' section in aptitude. ... You can later install a new kernel or compile a new kernel, but as said in the release info, I strongly recommend to do this in a separate step: use your existing kernel to see if everything works fine; ... 50% Building Dependency Tree Reading extended state information... ...
      (Debian-User)
    • Yum upgrade from F8 to F9 with KDE desktop - installation notes
      ... nVidia drivers from Freshrpms, and I had to install the latest nVidia driver ... kernel in step 5; once I did that, the dkms package (which gets installed from ... Use your preferred method to install the above file: ...
      (Fedora)
    • SUSE Security Announcement: several kernel security problems (SUSE-SA:2005:044)
      ... please install the update packages. ... Use the following command to determine which kind of kernel is ... Download the kernel RPM package for your distribution with the ... Starting from SUSE LINUX 9.2, ...
      (Bugtraq)
    • Re: Basic yum question- latest version isnt latest version.
      ... right now yum has postgres 8.1.9 ... Package apr-util needs libpq.so.4, ... was install the "comat" rm for postgresql, ... duplicate lib is loaded for each app, it's also one of the reasons you ...
      (comp.os.linux.misc)
    • Re: Comments from a new user: what is Distrowatch complaining about?
      ... install klipper. ... "yum install klipper" didn't produce any result, as urpmi klipper, in ... I've seen that sort of thing work (yum finding the right ... Download the x86_64 package, un gzip it on the desktop, copy to: ...
      (Fedora)