[opensuse] 10.3 WARNING: Yesterdays update killed online update and Software Management
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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Richard Creighton wrote:
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. Richard,
I cannot agree more. Imho your suggestion to have a backup way of installing updates, is one step. The other essential thing I see necessary is quality control BEFORE an update is released to the public. Otoh, let's not forget that this is free software, also free as in beer. I would be much more angry if this happened to me on a SLES based enterprise machine. I also remember that Ubuntu LTS (long term suppport) once got an update that rendered thousands of X configurations worldwide to be unuseable and recently, Microsoft's WGA servers failed, as well. So it is really bad and there is no real excuse, but the competition is not necessairily better. Kind regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Eberhard Roloff wrote:
Richard Creighton wrote:
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.
Richard,
I cannot agree more.
Imho your suggestion to have a backup way of installing updates, is one step. The other essential thing I see necessary is quality control BEFORE an update is released to the public.
Otoh, let's not forget that this is free software, also free as in beer.
I would be much more angry if this happened to me on a SLES based enterprise machine.
I also remember that Ubuntu LTS (long term suppport) once got an update that rendered thousands of X configurations worldwide to be unuseable and recently, Microsoft's WGA servers failed, as well.
So it is really bad and there is no real excuse, but the competition is not necessairily better.
Kind regards Eberhard
I have opened Bug #342590 to hopefully address this issue. It will probably be closed, but who knows, maybe not. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Nov 18, 2007 at 05:11:17PM +0100, Eberhard Roloff wrote:
Richard Creighton wrote:
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. Richard,
I cannot agree more.
Imho your suggestion to have a backup way of installing updates, is one step. The other essential thing I see necessary is quality control BEFORE an update is released to the public.
The QA for box updates QA is limited. We however test them internally from our staging server. The problem is that this update was checked in and immediately released afterwards, which should not have happened. If some days / the weekend had been inbetween checkin and release (as is usual), our internal updates would have caught this and not the general public. We have btw now publictesting update branches prepared for external update testing too, but currently these are not staged yet to the outside. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Marcus Meissner wrote:
On Sun, Nov 18, 2007 at 05:11:17PM +0100, Eberhard Roloff wrote:
Richard Creighton wrote:
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. Richard,
I cannot agree more.
Imho your suggestion to have a backup way of installing updates, is one step. The other essential thing I see necessary is quality control BEFORE an update is released to the public.
The QA for box updates QA is limited.
We however test them internally from our staging server.
The problem is that this update was checked in and immediately released afterwards, which should not have happened.
If some days / the weekend had been inbetween checkin and release (as is usual), our internal updates would have caught this and not the general public.
We have btw now publictesting update branches prepared for external update testing too, but currently these are not staged yet to the outside.
Ciao, Marcus
Thanks much Marcus. I appreciate that things are improving and, again, I understand that QA for box updates needs to be limited in comparison to QA for "paid support" products. Thanks again and kind regards Eberhard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Nov 18, 2007 at 10:50:33AM -0500, Richard Creighton wrote:
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.
How do you want to backup those updates RPMs ... Especially with scripts run and other things. It is very difficult and not workable I guess. As for multiple kernels installed at the same, this is something we consider. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-11-18 at 17:55 +0100, Marcus Meissner wrote:
How do you want to backup those updates RPMs ... Especially with scripts run and other things.
It is very difficult and not workable I guess.
Years ago (suse 7.3?) yast made a backup somewhere under /var of removed rpms, I think.
As for multiple kernels installed at the same, this is something we consider.
That would be really nice. What about a rule "do not ever push updates on friday" ? O;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHQKqutTMYHG2NR9URAllXAKCYB4kc0Bkwz/xmFKjHqHC67rjOjgCggyxe UEpCQ7wdQ3Dcz26KO9rBpBs= =7fmH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Carlos E. R. wrote:
Years ago (suse 7.3?) yast made a backup somewhere under /var of removed rpms, I think.
Nope, that was just for backups of the RPM DB itself. And it still does
that: check /var/adm/backup/rpmdb
Bye,
LenZ
- --
- ------------------------------------------------------------------
Lenz Grimmer
On Sunday 18 November 2007 15:12:12 Carlos E. R. wrote:
The Sunday 2007-11-18 at 17:55 +0100, Marcus Meissner wrote:
How do you want to backup those updates RPMs ... Especially with scripts run and other things.
It is very difficult and not workable I guess.
Years ago (suse 7.3?) yast made a backup somewhere under /var of removed rpms, I think.
As for multiple kernels installed at the same, this is something we consider.
That would be really nice.
What about a rule "do not ever push updates on friday" ? O;-)
-- Cheers, Carlos E. R.
I had the same problem. I used the distribution DVD to reinstall the missing packages and it fixed the problem. -- -------------------------------------------------------------- Registered Linux User #169330 ( http://counter.li.org ) Pure Linux (SUSE) User GnuPGP key available on request Jaxtr Phone: http://www.jaxtr.com/dlj53tx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
I have not seen that problem here. I'm running 64 bit. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos E. R. -
dj53tx-sle＠yahoo.com -
Eberhard Roloff -
James Knott -
Lenz Grimmer -
Marcus Meissner -
Richard Creighton