FW: [SLE] YaST Online Update Problem

From: Greg Wallace (jgregw_at_acsalaska.net)
Date: 09/07/04

  • Next message: Thorsten Kukuk: "Re: [SLE] NIS - yppasswdd"
    To: <suse-linux-e@suse.com>
    Date: Mon, 6 Sep 2004 22:59:35 -0800
    
    

    On Sunday, September 05 2004 5:44 PM ADT, Greg Wallace wrote:
    >On Saturday 04 September 2004 11:05 PM (some earlier time zone), Anders
    Johanson wrote:
    >>On Sunday 05 September 2004 07:59 ADT, Greg Wallace wrote:
    >>> I just migrated from SuSE Linux 8.1 Professional to 8.2 Professional
    (I'm
    >>> moving toward 9.1 one version at a time). I didn't lose any data and
    >>> everything seems to be functioning fine, with one notable exception.
    YaST
    >>> Online Update no longer works! After I upgraded to 8.2, one of the
    first
    >>> things I did was go to Online Update to pick up the latest updates to
    the
    >>> particular packages in my installation. When I checked for updates,
    YaST
    >>> returned a list of patches to 30 or 40 of my packages. I clicked the
    >>> "Accept" button and YaST proceeded to "retrieve" all of the package
    >>> updates. That part apparently worked fine, but when it went to the
    >>> installation step, that step failed on every single one of the
    downloaded
    >>> patches with the exact same error message -
    >>>
    >>> Error Installing patch '.' <-- Name of particular patch
    >>> Skip this patch or abort the update?

    >>Did you click the "Details" button, to see if there was a better error
    >>message? You can also look at the y2log files in /var/log to see if it
    gives
    >>you a better idea of what's going wrong

    >>You can also go to /var/lib/YaST2/you/mnt/i386/update/8.2/rpm and try to
    >>update one of the rpms manually to see if rpm will give you a better error

    >>message.

    >1) Did you click the "Details" button ...

    >I tried that and I get the following for each patch that YaST is trying to
    >install --
    >ERROR (YOU: rpm failed)
    >/var/lib/YaST2/you/mnt/i386/update/8.2/rpm/i586/"a patch number here"

    >2) You can also look at the y2log files...

    >This does show more info. For each patch failure, I see a set of lines
    that
    >looks like this (some extraneous info at the beginning of each line is
    removed) --

    >RpmDB::installPackage(/var/lib/YaST2/you/mnt/i386/update/8.2/rpm/i586/"a
    patch number here"
    >[rpmdb] RpmDb.cc(InstallPackage):1539 rpm failed, message was:
    >[vi-shortcuts] YShortcutmanager.cc(check shortcuts):96 No valid shortcut
    for
    YPushButton "Skip Patch"
    >[vi-shortcuts] YShortcutmanager.cc(check shortcuts):96 No valid shortcut
    for
    YPushButton "Skip ALL"
    >[vi-shortcuts] YShortcutmanager.cc(check shortcuts):96 No valid shortcut
    for
    YPushButton "Abort update"
    >[rpmdb] Rpmdb.cc(installPackage):1456

    >When I was running this in YaST, each time I got the error I was given 3
    >options, "Skip Patch", "Skip ALL, or "Abort update". Those 3 messages show
    >up above in the details in the log. I guess it repeats the error (No valid
    >shortcut...) for each option it gave you when you were running YaST, so
    >maybe the "No valid shortcut for YPushButton" is the real error (or maybe
    >the real error isn't even showing up in this log, other than it maybe being
    >the 1539 -- maybe that's a YaST error number?).

    >3) You can also go to /var/lib/... and try to update one of the rpms
    manually...

    >I went to the location you specify (it does have an additional i586 node at
    >the end) and it appears that all of the patches were downloaded and are
    >indeed sitting right there ready to be applied. What would I key in to
    tell
    >SuSE to try to apply one of the patches? I know (VERY) little about RPM.
    >I've always used YaST for Online Updates and for installing new packages.

    >Thanks and yours truly,
    >Greg Wallace

    Never mind on this problem. I've gotten around it. I suspected all along
    that the problem might be that, since I updated my 8.1 system to 8.2 instead
    of doing a fresh 8.2 install and then adding the packages I needed
    afterward, the packages I brought over from 8.1 were not compiled in a way
    that they could be updated as is via "online update". I was thinking that
    8.2 uses a different compile process and I still think that was the problem,
    but maybe I'm wrong. That would explain why none of the updates could be
    applied. I was thinking I'd need to figure out how to do recompiles on all
    of those old packages manually via rpm first before I could apply patches to
    them (I've never done an rpm compile). Then it dawned on me that, since
    everything was actually functioning properly (even though I couldn't apply
    those updates), maybe I'd be better off just trying to go on to 9.0 instead
    of trying to get 8.2 working. I wanted to go to 9.0 anyway so I figured
    "what the heck, what do I have to lose". I could always go back and
    re-install 8.2 or even 8.1 and start over if it didn't work. Well, I got
    lucky! When installing 9.0, one of the things that caught my eye early on
    was that I got a message saying it was doing a conversion of all of my
    packages automatically! Not only that, but at the end of the install, it
    automatically sent me to online update to pick up any new patches for all of
    the packages I had installed! Without having to do anything manually, the
    9.0 installation took care of any and all of my installation problems
    automatically! What a nice touch as far as smoothing out the installation
    process! I'm pretty impressed! I did have to go in and manually start
    inetd and also do a manual reinstallation of Samba (even though I already
    had it installed going into the update), but, after that, everything started
    up and worked perfectly! Well, almost. The Smbfs Samba package no longer
    works. Apparently, the old "mount -t smbfs..." method it uses to mount a
    samba share into your directory structure is no longer supported in SuSE
    9.0. When you run smbfs, error messages come out directing you to use a
    different mount command. I haven't tried to work through that yet, but
    that's a very minor glitch to me and I can work through it down the road in
    my spare time (maybe there's an updated smbfs out there that I just need to
    install). I know I've rambled on a bit here, but I really am excited about
    having 9.0 on my machine now, so, hopefully, I can be excused a bit. I also
    have 9.1 sitting in the closet, but I may hold off on that for a while
    (maybe it's better to stay one version behind so that all of the kinks get
    worked out before you move to the next version?). Right now, I plan to just
    stay with 9.0 for a while and enjoy it.

    Greg Wallace

    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Thorsten Kukuk: "Re: [SLE] NIS - yppasswdd"