Bugzilla – Bug 240286
yast onlineupdate constantly reports: "this patch is broken !!!"
Last modified: 2008-03-25 22:51:55 UTC
hello, i have a system that has been constanly upgraded from one suse linux version to the next. after the last upgrade from suse 10.1 to suse 10.2 the system seemd fine (apart from some other bugs, never mind). but for a few weeks now, yast onlineupdate reports a hugeloads of problems and apparently never applies/installes the found upgradable packages. i also reported this behaviour in relation to a squid bug in suse 10.2 please see comment #10: https://bugzilla.novell.com/show_bug.cgi?id=223067#c10 i dont know whats going on with the suse update / yast / zypp system, but there is definitely something wrong here.... yast onlineupdate shows me for allmost all the descriptions of the to-be installed packages the following line at the very top of the package description: "----- this patch is broken !!! -----" and from time to time i get little windows that pop-up and complain about screen rpm being already installed and generating errors. well ever since i had this screen-rpm mess, i even uninstalled/removed the screen package, and there is no screen-packages on that system any more, and never the less yast onlineupdate still complains about screen-rpm-errors (similar to this from the other bugreport) Subprocess failed. Error: RPM failed: 2006-12-11 00:12:26 screen-4.0.2-81.i586.rpm install failed┴ rpm output: package screen-4.0.2-81 is already installed 2006-12-11 00:12:26 screen-4.0.2-81.i586.rpm install failed ------- oh and i can start the update-process of the found packages in yast onlineupdate, and sometimes yast even downloads some rpm packages and apparently tries to install something, but then brings up these crazy screen-rpm-errors or other stuff, and in the end it never really does anything, since the very same updates still appear on the yast onlineupdate-list the next time i start it. so patches dont get installed, and i reason that it has to do with this line telling me "this patch is broken !!!" oh, by the way, i found some sourcecode/diff for this line on the mailing-list "opensuse commit" http://lists.opensuse.org/opensuse-commit/2006-11/msg00081.html that posting at least contains the description: + descr += _( "----- this patch is broken !!! -----" ); so whats going on here? i will upload my y2log file (with debug settings) as soon as this bug has been created properly in the novell bugzilla system. thanks and cheers. -- Linux chef 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 i686 i386 GNU/Linux openSUSE 10.2 (i586) VERSION = 10.2
doh, the novell bugzilla system only accepts 5megs of attachments :/ jebuz, did i miss this information on any of the upload pages or is it a matter of userfriendliness to tell so in advance before acutually uploading big files and the system simply rejecting the file even though the upload actually succeeded :/ so the tarbzip2 file should be reachable at http://www.filefactory.com/file/a8cb43/ filesize: 15.021.015 bytes (~15megs) md5sum 95 25 F0 4C CD A9 FD 31 D0 EB 93 E1 5B 05 EC F8 sh1sum 09A0 2C8C B7F5 90E4 4183 73E5 EB68 1C3E D204 158B
Created attachment 116421 [details] latest entries from y2log - after yast online update configuration failed i just checked / tried the yast online update configuration once more, and yast comes up with errors that no product could be registered with the novell service.... this used to work in the past. maybe this is also a reason for the failures of yast onlineupdate.
It seems that you are reporting problems with ncurses YaST. Does it behave the same if you try Qt version of online-update? Is it possible to mark the broken patch for re-installation in the UI (and reinstall it)? What does 'zypper pch' (or 'rug pch') report? What is the output of 'rpm -Va --nofiles'? If nothing strange, what about 'rpm -Va'? Did you install some packages manually before your problems with broken patches?
the system was actually constantly being upgraded ever since round about suse 9.x or late 8.x not sure any more.... the last ugrade from suse 10.1 to opensuse 10.2 was actually working well (more or less) nothing spectacular. and yast online_update was able to fetch updates in december and early january at the beginning. somewhen it started displaying me these "patch broken" messages and everything came to a stop more or less... i tried to get some of the more important rpms from the update-repositories/servers out there and manually downloading some and rpm -Uvh packagename.rpm something like that.... but only recently like after my initial bugreport. i also found some other bug regarding upgrade-loops and problems with suse 10.1 that talked about corrupted rpm-database and doing rpm rebuild stuff. see: https://bugzilla.novell.com/show_bug.cgi?id=229584 so i also did the rpm --rebuild which went through all right, but the yast online_update problems are still there. and i created those extensive yast logfiles in the uploaded file with the help of http://en.opensuse.org/Bugs/YaST ------ okay so i have run those commands you said and some error-outputs were displayed. here are the lines: chef:/tmp # zypper pch Restoring system sources... Parsing metadata for 20070119-160359... Parsing metadata for 20070119-160438... Parsing RPM database... Catalog | Name | Version | Category | Status ----------------+----------------------+---------+-------------+--------------------- 20070119-160438 | ImageMagick | 2413-0 | recommended | Not Applicable 20070119-160438 | MozillaFirefox | 2418-0 | security | Not Applicable 20070119-160438 | MozillaThunderbird | 2421-0 | security | Not Applicable 20070119-160438 | acroread | 2506-0 | security | Not Applicable 20070119-160438 | amarok | 2516-0 | recommended | Not Applicable 20070119-160438 | autoyast2 | 2466-0 | recommended | Not Needed 20070119-160438 | bind | 2529-0 | security | Not Needed 20070119-160438 | bluez-utils | 2492-0 | recommended | Not Needed 20070119-160438 | cacti | 2447-0 | security | Not Applicable 20070119-160438 | clamav | 2391-0 | security | Not Applicable 20070119-160438 | compat-g77 | 2510-0 | recommended | Not Applicable 20070119-160438 | compiz | 2458-0 | recommended | Not Applicable 20070119-160438 | compiz | 2519-0 | recommended | Not Applicable 20070119-160438 | cups | 2430-0 | recommended | Not Needed 20070119-160438 | cups | 2527-0 | security | Not Needed 20070119-160438 | cups | 2406-0 | recommended | Not Needed 20070119-160438 | cyrus-imapd | 2454-0 | recommended | Not Applicable 20070119-160438 | dazuko | 2404-0 | security | Not Applicable 20070119-160438 | evince | 2362-0 | security | Not Applicable 20070119-160438 | fetchmsttfonts.sh | 2333-0 | optional | Not Needed 20070119-160438 | flash-player | 2359-0 | security | Not Applicable 20070119-160438 | flash-player | 2509-0 | recommended | Not Applicable 20070119-160438 | gdm | 2387-0 | security | Not Applicable 20070119-160438 | glabels | 2348-0 | recommended | Not Applicable 20070119-160438 | gpg | 2388-0 | security | Not Needed 20070119-160438 | gtk2 | 2499-0 | security | Not Needed 20070119-160438 | gv | 2350-0 | security | Not Applicable | gv | 2350-0 | security | No Longer Applicable 20070119-160438 | hal | 2500-0 | recommended | Not Needed 20070119-160438 | jarnal | 2451-0 | recommended | Not Applicable 20070119-160438 | java-1_4_2-sun | 2425-0 | security | Not Applicable 20070119-160438 | java-1_4_2-sun-demo | 2469-0 | security | Not Applicable 20070119-160438 | java-1_5_0-sun | 2427-0 | security | Not Applicable 20070119-160438 | kchmviewer | 2539-0 | security | Not Applicable 20070119-160438 | kdeaddons3-konqueror | 2383-0 | recommended | Not Applicable 20070119-160438 | kdelibs3 | 2452-0 | recommended | Not Applicable 20070119-160438 | kdeutils3-extra | 2450-0 | recommended | Not Applicable 20070119-160438 | krb5 | 2442-0 | security | Not Needed 20070119-160438 | krusader | 2386-0 | recommended | Not Applicable 20070119-160438 | libgtop | 2512-0 | security | Not Needed 20070119-160438 | liboil | 2419-0 | recommended | Needed | liboil | 2419-0 | recommended | Broken 20070119-160438 | libsoup | 2503-0 | security | Not Needed 20070119-160438 | libzypp | 2533-0 | recommended | Not Needed 20070119-160438 | libzypp | 2477-0 | recommended | Not Needed 20070119-160438 | lineak_kde | 2361-0 | recommended | Not Applicable 20070119-160438 | lvm2 | 2438-0 | recommended | Not Needed 20070119-160438 | mediawiki | 2457-0 | security | Not Applicable 20070119-160438 | mono-core | 2392-0 | security | Needed | mono-core | 2392-0 | security | Broken | neon | 2476-0 | security | Broken 20070119-160438 | neon | 2476-0 | security | Needed 20070119-160438 | nss_ldap | 2480-0 | recommended | Not Needed 20070119-160438 | openssl | 2349-0 | security | Not Needed 20070119-160438 | opera | 2456-0 | security | Not Applicable 20070119-160438 | pm-utils | 2422-0 | recommended | Not Needed 20070119-160438 | powersave | 2526-0 | recommended | Not Applicable 20070119-160438 | privoxy | 2375-0 | recommended | Needed | privoxy | 2375-0 | recommended | Broken 20070119-160438 | python | 2446-0 | recommended | Not Needed 20070119-160438 | release-notes | 2374-0 | recommended | Not Needed 20070119-160438 | resmgr | 2371-0 | recommended | Needed | resmgr | 2371-0 | recommended | Broken 20070119-160438 | rrdtool | 2540-0 | security | Needed 20070119-160438 | sax2 | 2445-0 | recommended | Not Needed 20070119-160438 | smb4k | 2514-0 | security | Not Applicable 20070119-160438 | squid | 2467-0 | recommended | Not Needed 20070119-160438 | squid | 2504-0 | security | Not Needed 20070119-160438 | squirrelmail | 2409-0 | security | Not Applicable 20070119-160438 | squirrelmail | 2417-0 | security | Not Applicable 20070119-160438 | sysstat | 2401-0 | recommended | Not Applicable 20070119-160438 | sysvinit | 2424-0 | recommended | Not Needed 20070119-160438 | tar | 2351-0 | security | Not Needed 20070119-160438 | totem | 2468-0 | recommended | Not Applicable 20070119-160438 | ulogd | 2470-0 | security | Not Applicable 20070119-160438 | unison | 2436-0 | recommended | Not Applicable 20070119-160438 | w3m | 2433-0 | security | Not Needed 20070119-160438 | wxGTK | 2411-0 | recommended | Not Applicable 20070119-160438 | xine-lib | 2487-0 | security | Not Applicable 20070119-160438 | xorg-x11-Xvnc | 2491-0 | recommended | Not Applicable 20070119-160438 | xorg-x11-server | 2453-0 | security | Not Applicable 20070119-160438 | yast2-printer | 2525-0 | recommended | Not Needed 20070119-160438 | yast2-sound | 2541-0 | recommended | Needed | yast2-sudo | 2441-0 | recommended | Broken 20070119-160438 | yast2-sudo | 2441-0 | recommended | Needed 20070119-160438 | yast2-trans-de | 2518-0 | recommended | Not Applicable 20070119-160438 | zypper | 2513-0 | recommended | Not Needed chef:/tmp # rug pch Waking up ZMD...Done Catalog | Name | Version | Category | Status --------+---------+---------+----------+---------- System | gv | 2350-0 | security | Installed System | openssl | 2349-0 | security | Installed System | tar | 2351-0 | security | Installed chef:/tmp # rpm -Va --nofiles Unsatisfied dependencies for mono-data-sqlite-1.1.18.1-12.2.i586: mono-core = 1.1.18.1-12.2 Unsatisfied dependencies for mono-web-1.1.18.1-12.2.i586: mono-core = 1.1.18.1-12.2 Unsatisfied dependencies for mono-data-1.1.18.1-12.2.i586: mono-core = 1.1.18.1-12.2
Was it possible to reinstall the patch from YaST (ncurses or Qt) online update? Have you reinstalled some yast2-* packages?
i dont recall having installed yast packages manually. i have listed the yast packages that are on my system: #rpm -aq | grep -i ya yast2-packager-2.14.10-3 yast2-hardware-detection-2.14.0-6 yast2-nis-server-2.14.1-14 yast2-xml-2.14.0-3 yast2-security-2.14.2-15 yast2-kerberos-client-2.14.5-3 yast2-samba-server-2.14.3-10 yast2-online-update-2.14.2-10 yast2-core-2.14.4-9 yast2-firewall-2.14.1-15 yast2-runlevel-2.14.1-15 yast2-2.14.15-3 yast2-vm-2.14.2-7 yast2-samba-client-2.14.4-3 yast2-power-management-2.14.3-7 yast2-powertweak-2.14.0-8 yast2-ncurses-2.14.4-3 yast2-storage-2.14.18-3 yast2-online-update-frontend-2.14.2-10 yast2-slp-2.14.1-5 yast2-iscsi-client-2.14.0-17 yast2-restore-2.14.0-36 yast2-bootfloppy-2.14.14-3 yast2-irda-2.14.0-12 yast2-tune-2.14.0-10 yast2-repair-2.14.0-16 yast2-bootloader-2.14.14-3 yast2-sound-2.14.0-10 yast2-dns-server-2.14.2-10 yast2-sysconfig-2.14.0-8 yast2-ldap-2.14.0-12 yast2-dhcp-server-2.14.1-5 yast2-theme-openSUSE-2.14.1-10 autoyast2-2.14.16-0.1 yast2-ntp-client-2.14.2-10 yast2-update-2.14.7-12 yast2-storage-lib-2.14.18-3 yast2-apparmor-2.0.1-11 yast2-users-2.14.1-3 yast2-nfs-client-2.14.0-4 yast2-installation-2.14.15-3 yast2-tv-2.14.0-12 yast2-nis-client-2.14.0-12 yast2-perl-bindings-2.14.0-9 yast2-inetd-2.14.1-23 yast2-network-2.14.12-3 yast2-http-server-2.14.5-3 yast2-bluetooth-2.14.0-33 yast2-schema-2.14.2-3 autoyast2-installation-2.14.16-0.1 yast2-printer-2.14.16-2.1 yast2-country-2.14.5-10 yast2-mail-2.14.0-12 yast2-trans-en_US-2.14.1-3 yast2-pam-2.14.0-31 yast2-pkg-bindings-2.14.4-5 yast2-sudo-2.14.2-31 yast2-mouse-2.14.1-8 yast2-profile-manager-2.14.1-12 yast2-registration-2.14.2-4 yast2-nfs-server-2.14.0-4 yast2-backup-2.14.1-16 yast2-phone-services-2.14.0-5 yast2-storage-evms-2.14.18-3 yast2-support-2.14.0-8 yast2-trans-stats-2.11.0-74 yast2-ldap-client-2.14.5-10 yast2-transfer-2.14.0-10 yast2-scanner-2.14.11-3 yast2-mail-aliases-2.14.0-12 yast2-tftp-server-2.14.0-8 are any missing? or are these the current ones? do you need any more information? thanks.
> do you need any more information? Yes, you didn't answered my questions if Qt version of yast2 online update has the same problems and if it is possible to reinstall the patch from online update GUI. As a next step, please attach also output of 'rpm -Va'.
oh, i actually only run the whole box in textmode. so nothing else except the ncurses will run, am i right? i dont have gnome, kde, x on that box if im not mistaken.... what about that suse_register process... which also fails and tells me that there are no products or something. anything about that?
> oh, i actually only run the whole box in textmode. OK. But if you could upgrade to version with X, it might help. Anyway, setting the patch to reinstall should be possible also in text mode, please try it ([Actions] -> Update). > what about that suse_register process... This is also strange. Let's do another test with logfiles (your old ones are so big it is hard to read them). Remove (backup) your old log files, than run just online update your prefered way, try to reinstall the patch and finish yast. Than attach those new log files (no debug option needed). And also that rpm -Va output can help.
ok, so still in textmode so far: i start up yast online_update (non-debugging environment settings, otherwise it takes ages on this old box... will do that later if neccessary again...) it reads some repositories, parses stuff, packages... then it displays some packages to be applied all the proposed patches (except for the fonts download..) have this a> next to them... i suppose this means automatically set to download/apply patch. right? i can enforce it to > only, either with the menu or some keys... in the first try i left all the a> and simply selected that it should install all those patches. what it did was to download exactly two patches and id said that it was able to install them. after the two patches yast finished. will check now whats left of the patches in the list or if it did anything at all.
ok so i suppose the list is still the very same in the second run of yast onlineupdate. the list currently displays as follows: │Download Microsoft(r) TrueType Core Fonts │optional │ │ a> │liboil: GStreamer applications crash when plugins use liboil│recommended │ │ a> │mono: security update for ASP.net source disclosure. │security │ │ a> │neon: This update fixes a possible crash in the URI parser. │security │ │ a> │Fix: privoxy stops working after networkmanager switch │recommended │ │ a> │resmgr Active Directory bugfix │recommended │ │ a> │Fix for defunct kdesu after editing sudoers with yast2-sudo │recommended ok, so i can toggle with the "space" key all the a> to > but the weird thing is, that the total download size always remains at 0 bytes and all the descriptions still tell me this "the patch is broken" stuff... i can select "ok" then... it says calculating.... does nothing... the only display now is "finished..."... then "close...." it still does however, the writing system configuration, setting up linker cache, running suseconfig...... and that stuf.... weird.
Created attachment 116805 [details] y2log data (nondebug) from 2007-02-01 only
Stefan, could you read what's going on in the last log? Are some patches getting installed or not?
I cannot see any error in the logfiles. Please reproduce it again and generate a testcase then: http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F Could you please give me an example ( which patch is broken, which package will not be updated/installed) ?
well i did create that tbz2 file and uploaded it to some free filehoster before. those logs (the newer ones in the var/log/Yast2/ folder) were created with that extensive debugging settings. i can create / start a new yast-onlineupdate session again with clean logs and extensive debugging mode on, only it will take a while as this box is pretty old and slow.
You only have to use the menue entry while running YOU: "Since OpenSUSE 10.2 you can create additional information by selecting the menue entry Extras/Generate_Dependency_Resolver_Test_Case in the single package selection frame. You will be asked for generating the logfiles which you should add to the bugzilla entry as described" /var/log/YaST2/solverTestcase/* would be enough for seeing what goes on. Thanks !!!
Created attachment 116876 [details] i checked the solvertestcase and here comes the tbz2 file uploaded i checked the solvertestcase and here comes the tbz2 file uploaded
so this is still the list that yastonlineupdate displays whenever it is started currently: ¦ ¦Download Microsoft(r) TrueType Core Fonts ¦optional ¦ ¦ a> ¦liboil: GStreamer applications crash when plugins use liboil¦recommended ¦ ¦ a> ¦mono: security update for ASP.net source disclosure. ¦security ¦ ¦ a> ¦neon: This update fixes a possible crash in the URI parser. ¦security ¦ ¦ a> ¦Fix: privoxy stops working after networkmanager switch ¦recommended ¦ ¦ a> ¦resmgr Active Directory bugfix ¦recommended ¦ ¦ a> ¦Fix for defunct kdesu after editing sudoers with yast2-sudo ¦recommended all these packages (except for the fonts) give me this "patch is broken" line at the bottom in the description when i navigate onto them. anything else needed?
Thank you. Now it is clear: You have installed: <patch> <name>liboil</name> <arch>noarch</arch> <version>2419</version><release>0</release> <atom> <name>liboil</name> <arch>i586</arch> <version>0.3.9</version><release>15.2</release> <package> <name>liboil</name> <arch>i586</arch> <version>0.3.9</version><release>15</release> So, you have an older version of liboil installed than the INSTALLED patch needs. The reasons for downgrading this package I cannot see anymore. But there is already a bug that these patches will not be updated correclty (Bug 191810) in order to satify it again. Meanwhile you can solve it manually by update the concerning packages per hand ( Toggle the update/keep status in the package selection while calling YOU). So the solver has to update these packages cause you have said explicity. The other possibility would be to delete the concerning installed patches in /var/lib/zypp_db/patches/ So these patches would be installed again. *** This bug has been marked as a duplicate of bug 191810 ***
According to comments #10 and #11, it looks for me that there's another problem that the patches can't be forced to reinstall.
I have seen a similar broken system. The situation was done by killing the online update in the middle of the process, so the patch is installed, but not all packages. None of our tools is able to fix a broken patch. This is not a major.
yes there is still something missing here.... i already wrote to stefan schubert by mail that for testing i deleted the comlete contents of /var/lib/zypp/db/patches/ after that i ran yast onlineupdate. the list now was bigger, and the "patch is broken" stuff didnt appear in the descriptions. there were some packages with a+ markings. i could select all the other packages too manually. but as soon as i triggered their installation, yast would simply print out that it was finished, doing nothing except for this running suseconfig, linker... stuff. then finished.... now my /var/lib/zypp/db/patches/ directory contains only one file: -rw-r--r-- 1 root root 3434 Feb 2 11:21 090f80f30c89c1ec6975208099d1f149 actually this is quite a mess i would say. my only final real-world question is actually, how can i simply fix this complete mess, delete/reinstall/fix/cleanup this whole libzypp/database/cache/yastonlineupdate stuff so that it simply works. yast should download all the patches all over and make them install. fullstop. my system is likely insecure or pretty messed up by now for quite a while now as i dont seem to be getting security relevant patches and so forth... i dont really actually care about fixing this bug any more, as this is getting insane and worse with each step :( thanks.
I have said "delete the concerning installed patches" and not all patches;-) Anyway, I assume that 090f80f30c89c1ec6975208099d1f149 is a libzypp patch which will be installed BEFORE ALL other patches. A second call of should take the other patches. Isn'it ?
ok well, you are right, after one more run of yast onlineupdates a lot of patches were displayed, and this time they actually downloaded again and got installed. at least one more run of yast onlineupdate only displays the microsoft fonts download as the single item in the list. my /var/lib/zypp/db/ directory now also displays -rw-r--r-- 1 root root 3434 Feb 2 11:21 090f80f30c89c1ec6975208099d1f149 -rw-r--r-- 1 root root 4988 Feb 2 12:08 f658ce5b74d1a22209a998704ecd7104 -rw-r--r-- 1 root root 8589 Feb 2 12:08 e87a2c13909937480653c592b645a83c -rw-r--r-- 1 root root 3786 Feb 2 12:08 dfdcbf4e15c75b18e66e16298e5128fc -rw-r--r-- 1 root root 4059 Feb 2 12:08 de7f398019c47f9fa0faa50626e2f7ea -rw-r--r-- 1 root root 8836 Feb 2 12:08 ccf6699222299fe6b5edb2a6e207e9d3 -rw-r--r-- 1 root root 9772 Feb 2 12:08 b45e4e3aeea650388161f73dbcc35676 -rw-r--r-- 1 root root 5011 Feb 2 12:08 a8c55c46181f4c58341d1e1cfbbedc82 -rw-r--r-- 1 root root 4441 Feb 2 12:08 9820ce4193479036a1cf050bfc4cce35 -rw-r--r-- 1 root root 3468 Feb 2 12:08 80b73331d08414c7f83d3d8ddbe551f7 -rw-r--r-- 1 root root 4660 Feb 2 12:08 807bb1444a4e4ff31c9fb189be7d2432 -rw-r--r-- 1 root root 6929 Feb 2 12:08 746e7c39cf12f60075f82b674de6fc5e -rw-r--r-- 1 root root 4143 Feb 2 12:08 5fdd31f8c4b238ae286753c0ffbf2654 -rw-r--r-- 1 root root 2997 Feb 2 12:08 5c91f9a5011a521e3d382f2b227859d5 -rw-r--r-- 1 root root 3351 Feb 2 12:08 5b7fcb9370f9cd39e4e1d7b0254b0141 -rw-r--r-- 1 root root 9782 Feb 2 12:08 52d54b3ed48a231ea0b21d91ce9f9c05 -rw-r--r-- 1 root root 9682 Feb 2 12:08 4d4bcbfef4bfc4754becee417f17b900 -rw-r--r-- 1 root root 5897 Feb 2 12:08 4c596538d5525cb966de9e8adefce9e2 -rw-r--r-- 1 root root 3008 Feb 2 12:08 458469a6a19293474c8e30b6d23b6921 -rw-r--r-- 1 root root 3923 Feb 2 12:08 381227717216018f9ff5e649a60ee2f8 -rw-r--r-- 1 root root 6866 Feb 2 12:08 309c05ac523cf894fdd5bd85f13bf469 -rw-r--r-- 1 root root 3449 Feb 2 12:08 f76a92cec95dc7468e97bbda6b8ea081 -rw-r--r-- 1 root root 3977 Feb 2 12:08 f1821d492cdc1661c512e0d79b27ccbd -rw-r--r-- 1 root root 5627 Feb 2 12:08 f0ba0bb7aa398520457189e47d322c53 -rw-r--r-- 1 root root 5590 Feb 2 12:08 ca720eee89153307f09c603aa2a8560c -rw-r--r-- 1 root root 3438 Feb 2 12:08 b754f2b605ed5badf032278a45925329 -rw-r--r-- 1 root root 5923 Feb 2 12:08 8af572d82af7cdc84dffb5bce9af7482 -rw-r--r-- 1 root root 3272 Feb 2 12:08 68f66cda7c49ed4154ac1e3ea3ebdd4f -rw-r--r-- 1 root root 7005 Feb 2 12:08 39f1537d3966ca6e2f7e58a883db488c -rw-r--r-- 1 root root 5294 Feb 2 12:08 1cb38697e76f7ffa07d3807a711c29eb -rw-r--r-- 1 root root 9055 Feb 2 12:08 0df2cdd149b708002d3fb2ce202a3e19 -rw-r--r-- 1 root root 24222 Feb 2 12:08 01ebda1c0ae07eba4b4326fef233e34a i guess the problem here now is solved. i only wonder what got it started in the first place, since i never manually install suse update/packages in the shell, so to recap yast onlineupdate was working fine after the upgrade from suse 10.1 to 10.2 and then somewhere in the midst started to misbehave. anyways, thanks for all the help and good luck with these bugs. maybe some of the documentation or the wiki should be enhanced or added in relation to these bugs, giving end-users an easy way to fix their libzypp and onlineupdate stuff if they ever get into this situation.
I know this is last year & I know some dont like reviving old posts (if this describes you, stop reading here & go back to what you were doing) but I just very quickly post a confirmation that this does seem (at least to me) to be the result of an update that crashes or was interrupted or whatever it was in the middle of the update. I had a lot of (seeming) cruft in my cache directory, which I deleted then successfully updated after not being able to since the update borked long ago. It is good to know that the box is fully patched again. Thanks all. Cheers.