[opensuse] 10.3 Beta 2 - Yast installer issues?
Hi, Been messing around with beta 1 for the last couple of days evaluating it as a replacement for my ailing Kubuntu system, mostly works well, runs fast. However I managed to hose my test install 3 times today while trying to upgrade packages using Yast. I may be totally wrong in this, seeing as I'm a Suse newbie (but 10 year linux user/developer), but I'll float it anyway as it looks pretty lethel to me. Up to this morning, Yast would happily apply upgrades as rpm upgrades. After applying the latest Yast version, it now appears to be applying upgrades as a delete then an install. I'm basing this on what I think is the new appearance in the Yast update progress listing of lines of 'Deleting xxx' that delete all the packages selected for upgrade, followed by the downloads and installs. Now, that could just be deleting the rpm files from cache, in which case the message needs to be changed to something less scary, but I think it does delete the installed package. Trouble here is that if there is then a problem with the download or install, like I had 3 times running, your system can be seriously borked with important files deleted and not yet replaced. It's also not helped by the Abort and Cancel buttons not working properly when a problem is reported, or that network issues don't even return an error message and give you the chance to skip, your install is automatically aborted and you're dumped back to Yast with a borked system, or that trying to reapply failed installs re-downloads everything again (this was a problem yesterday, today you don't get there as you get error messages that the delete failed, and the skip abort buttons get all random on you). Has anyone else seen this, or am I way off-base here? Having been through the KDE CD installer about 5 or 6 times now, I spotted a couple of other things, the main one being you can't change CD's in the actual install step, and pre-added online repos not being used or remembered. Cheers! John. Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
A bit of testing confirms that I'm right, Yast is deleting the installed files first. For example, I just tried to upgrade a few rpms, including libbz2. So the installer deletes libbz2, then tries to install the new rpm, but fails because libbz2.so.1 is missing so it can't unpack it. Ouch! Also, the full error message when the delete fails makes it clear that it is an rpm error from trying to remove the actual package files. John. --- John Layt <johnlayt@yahoo.com.au> wrote:
Up to this morning, Yast would happily apply upgrades as rpm upgrades. After applying the latest Yast version, it now appears to be applying upgrades as a delete then an install. I'm basing this on what I think is the new appearance in the Yast update progress listing of lines of 'Deleting xxx' that delete all the packages selected for upgrade, followed by the downloads and installs. Now, that could just be deleting the rpm files from cache, in which case the message needs to be changed to something less scary, but I think it does delete the installed package. Trouble here is that if there is then a problem with the download or install, like I had 3 times running, your system can be seriously borked with important files deleted and not yet replaced. It's also not helped by the Abort and Cancel buttons not working properly when a problem is reported, or that network issues don't even return an error message and give you the chance to skip, your install is automatically aborted and you're dumped back to Yast with a borked system, or that trying to reapply failed installs re-downloads everything again (this was a problem yesterday, today you don't get there as you get error messages that the delete failed, and the skip abort buttons get all random on you).
Has anyone else seen this, or am I way off-base here?
Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 04:14:46 pm John Layt wrote:
A bit of testing confirms that I'm right, Yast is deleting the installed files first. For example, I just tried to upgrade a few rpms, including libbz2. So the installer deletes libbz2, then tries to install the new rpm, but fails because libbz2.so.1 is missing so it can't unpack it. Ouch!
Also, the full error message when the delete fails makes it clear that it is an rpm error from trying to remove the actual package files.
John.
Same here, during libzypp update. YaST suddenly exits. Ouch2. YaST Control Center starts, but there was no modules. Manual recovery with rpm worked. Reproduced your test with libbz2. Now let me see how to recover from this. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
If you are still able, you need to log into bugzilla and file a report so the guys there can fix it. I doubt they read this user forum buty they pay serious attention to the bug reports filed. http://bugzilla.novell.com This sounds like one of their fixes had a major undesirable side effect and they probably didn't know about it or they wouldn't have released it as an update. Richard Rajko M. wrote:
On Saturday 18 August 2007 04:14:46 pm John Layt wrote:
A bit of testing confirms that I'm right, Yast is deleting the installed files first. For example, I just tried to upgrade a few rpms, including libbz2. So the installer deletes libbz2, then tries to install the new rpm, but fails because libbz2.so.1 is missing so it can't unpack it. Ouch!
Also, the full error message when the delete fails makes it clear that it is an rpm error from trying to remove the actual package files.
John.
Same here, during libzypp update. YaST suddenly exits. Ouch2. YaST Control Center starts, but there was no modules.
Manual recovery with rpm worked.
Reproduced your test with libbz2.
Now let me see how to recover from this.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 17:10, Richard Creighton wrote: ...
Reproduced your test with libbz2.
Now let me see how to recover from this.
Done.
If you are still able, you need to log into bugzilla and file a report so the guys there can fix it. I doubt they read this user forum buty they pay serious attention to the bug reports filed.
This sounds like one of their fixes had a major undesirable side effect and they probably didn't know about it or they wouldn't have released it as an update.
Hi Richard, John found the test case and he has right to report it. I just finished recovery from the first glitch that left YaST useless state and installed few other packages when John's mail came in. The libbz2 update leaves no package management available, as it cuts out the very base of rpm that is used everywhere. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 17:10, Richard Creighton wrote:
...
Reproduced your test with libbz2.
Now let me see how to recover from this.
Done.
If you are still able, you need to log into bugzilla and file a report so the guys there can fix it. I doubt they read this user forum buty they pay serious attention to the bug reports filed.
This sounds like one of their fixes had a major undesirable side effect and they probably didn't know about it or they wouldn't have released it as an update.
Hi Richard,
John found the test case and he has right to report it.
I just finished recovery from the first glitch that left YaST useless state and installed few other packages when John's mail came in.
The libbz2 update leaves no package management available, as it cuts out the very base of rpm that is used everywhere. I think I would find the RPMs that contain ZYPPER and LIBZYP and get your install CD and restore them from that and use RPM to reinstall
Rajko M. wrote: those two packages. That probably will restore your ability to perform updates until a proper patch comes out. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 18:05, Richard C Creighton wrote: ...
The libbz2 update leaves no package management available, as it cuts out the very base of rpm that is used everywhere.
I think I would find the RPMs that contain ZYPPER and LIBZYP and get your install CD and restore them from that and use RPM to reinstall those two packages. That probably will restore your ability to perform updates until a proper patch comes out.
It is one of the ways, though, libbz2 is separate package. Live CD will give faster results. I used 10.2 installation and Midnight Commander to download libbz2 rpm files, open them and copy to mounted Beta1 partition in /lib and /lib64. Though, with little precaution to check where both libs are located (YaST has that list) and making backup copy will preserve reboot, download, etc. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yeah, i hit the libzypper problem too. First couple of times too many things had been deleted to be salvageable so had to full reinstall. Next 2 times was able to rescue it, first by downloading and installing libzypper, second by compiling and installing libbz2 from source. I've been trawling through bugzilla to see if anyone has reported it yet, but wanted to confirm it just wasn't a newbie mistake. All the other bugs I've hit are already there so I guess it's time to add this one. Cheers! John. Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 August 2007 16:37, Rajko M. wrote:
On Saturday 18 August 2007 04:14:46 pm John Layt wrote:
A bit of testing confirms that I'm right, Yast is deleting the installed files first. For example, I just tried to upgrade a few rpms, including libbz2. So the installer deletes libbz2, then tries to install the new rpm, but fails because libbz2.so.1 is missing so it can't unpack it. Ouch!
Also, the full error message when the delete fails makes it clear that it is an rpm error from trying to remove the actual package files.
John.
Same here, during libzypp update. YaST suddenly exits. Ouch2. YaST Control Center starts, but there was no modules.
Manual recovery with rpm worked.
Reproduced your test with libbz2.
Now let me see how to recover from this.
Done. There is always some rpm that is functional around. John who's going to report this to http://bugzilla.novell.com -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 18/08/07, John Layt <johnlayt@yahoo.com.au> wrote:
Been messing around with beta 1 for the last couple of days evaluating it as a replacement for my ailing Kubuntu system, mostly works well, runs fast. However I managed to hose my test install 3 times today while trying to upgrade packages using Yast. I may be totally wrong in this, seeing as I'm a Suse newbie (but 10 year linux user/developer), but I'll float it anyway as it looks pretty lethel to me.
Yes the version of libzypp in factory/svn is currently pretty broken, and does indeed cause this behaviour. https://bugzilla.novell.com/show_bug.cgi?id=301676 and I see you filed https://bugzilla.novell.com/show_bug.cgi?id=301682 _ Benjamin Weber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
--- Benji Weber <b.weber@warwick.ac.uk> wrote:
Yes the version of libzypp in factory/svn is currently pretty broken, and does indeed cause this behaviour.
https://bugzilla.novell.com/show_bug.cgi?id=301676
and I see you filed https://bugzilla.novell.com/show_bug.cgi?id=301682
_ Benjamin Weber
Didn't see your bug report... Anyway, I don't think it is libzypper itself, as there was definitely 1 time where I saw it delete libzypper itself and the whole thing segfaulted. So could be in Zypper in Yast2. Alternatively, there was one update on Friday night, and another lot on Saturday morning, so perhaps the earlier update did it? Well, I'm not about to try it again to find out :-) John. Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 August 2007 03:45:31 am John Layt wrote:
--- Benji Weber <b.weber@warwick.ac.uk> wrote:
Yes the version of libzypp in factory/svn is currently pretty broken, and does indeed cause this behaviour.
https://bugzilla.novell.com/show_bug.cgi?id=301676
and I see you filed https://bugzilla.novell.com/show_bug.cgi?id=301682
_ Benjamin Weber
Didn't see your bug report...
Anyway, I don't think it is libzypper itself, as there was definitely 1 time where I saw it delete libzypper itself and the whole thing segfaulted. So could be in Zypper in Yast2. Alternatively, there was one update on Friday night, and another lot on Saturday morning, so perhaps the earlier update did it? Well, I'm not about to try it again to find out :-)
John.
The 301676 was filed, just a few hours earlier, and if you looked for YaST bugs, like I did, than zypper one would not show up. You can select some lesser important package and look messages, as in your bug it is clear that YaST was deleting packages first. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Some new zypper/libzypp/yast2 packages uploaded today (along with a 1000 others), installed with rpm -Uvh but still broken... So stay well away from that upgrade button :-) John. Send instant messages to your online friends http://au.messenger.yahoo.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 August 2007 11:30:42 am John Layt wrote:
Some new zypper/libzypp/yast2 packages uploaded today (along with a 1000 others), installed with rpm -Uvh but still broken... So stay well away from that upgrade button :-)
John.
I update one package at the time. That way you have some control who is culprit if something turns bad. In the Factory it is bad idea to use: zypper up In this particular situtation you want to use rpm or Smart to install newer libzypp and zypper. BTW, updated Smart using Smart, and it works. Factory seems to be source of eternal fun. Did I mentioned that this might be better to post in opensuse-factory@opensuse.org mail list. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Benji Weber -
John Layt -
Rajko M. -
Richard C Creighton -
Richard Creighton