Eberhard Roloff wrote: > Hi, > > just a warning. > > Since I made an online update yesterday, I can no longer run yast online > update, and also can not start yast software management anymore. > > The helper applet in my kde tray displays: > Error: Can't launch zypp-checkpatches-wrapper helper program..... > > In the meantime I fixed this problem by doing this in the i586 directory > on the suse dvd: > rpm -Uvh --force boost-1*.rpm libzypp-3*.rpm zypper*.rpm > > I got that from a suse forum on the web, where the same happened with > suse 10.3/64 for several people. > > Accroding to the forum the boost update made yast software things unuseable. > > Good luck and take care. > > Eberhard > > It's about time that the updater program and more generally Yast installer provide the OPTION to backup any files it deletes to either the trashcan or to a special directory for the purpose of providing the ability to recover from the increasing number of bad updates, kernels and other software that is currently just deleting what is often perfectly good (read operating) software and replacing it with a 'fix' that too often really 'fixes' things, to the point of being unable to run.
Kernel updates or other critical software like Yast modules, often well intentioned updates will have unintended and sometimes fatal consequences and it leaves you with no alternatives but to reinstall from who knows where. In my own case, KERNEL updates often break a 3rd party disk controller driver and the inability to boot to the old configuration is often very time consuming to repair. When I notice 'kernel' patches or new kernels, I manually download the RPM files and rpm -i <newkernel> which does NOT delete the old information in GRUB or in /boot but appends to it. This is the way it used to be in earlier versions of SuSE. The current method of replace and delete gives you no recovery if the new software/kernel doesn't work. At a minimum, make the remove/delete method which currently is the only method, one of at least 2 options, the other option should be to KEEP the old configuration that is currently installed in place in addition to the new software, appropriately linked to the new software of course, and possibly a 3rd option where the current configuration is replaced as it is now, but the old configuration is moved to a holding area and available for immediate re installation if the new software fails. I am sorry to say that as a BETA tester, I expect an occasional BOMB and I accept it. However, this is on a GM release that bad software is being released or that 'fixes' with disastrous consequences is all too often being pushed out as updates, sometimes as 'mandatory' updates that nag you to death until you either install it or disable the updater applet entirely to make it go away (which defeats the purpose of the program). I am very sorry to say that I NO LONGER TRUST SuSE updates to leave my system intact. I am at least semi-competent to make repairs when these pieces of all too often bad software cause damage. In order for SuSE to become, or have a chance to become, mainstream and compete with Windoze, it has to work for the masses of people that know little more than about computers other than that you occasionally have to recharge the batteries or plug it into the wall before you turn it on. If SuSE gets (or keeps) the reputation of sending out GM releases that won't install, that 'repair' by destroying further whatever went wrong, that wipe out Windows or other OS's because they are on an IDE drive and the installer wants to rename everything to SDxx or whatever reason, SuSE and by association, Novell will lose bigtime. I think Novell needs to see how many Windoze employees are clandestinely working for them and their child organizations. Surely all this 'sabotage' can't all be simple human error. The programmers I've worked with during bets testing seemed too competent to be making all these mistakes. Richard -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
