https://bugzilla.novell.com/show_bug.cgi?id=304266#c18
--- Comment #18 from Harald Koenig
Created an attachment (id=174097) --> (https://bugzilla.novell.com/attachment.cgi?id=174097) [details] screen shot update summary
different try in this 10.1 update disaster: a SUSE 10.1 x86_64 partition on my IBM T60 (2 GHz T7200, 2 GB ram) with a plain 10.1 installation (994 RPMs,no packman etc). I booted from 10.3-GM x86_64 DVD, included network repos (oss and non-oss) for update, and the installation summary looked ok. BUT then I tried to change the pattern selection -- very bad idea: after selecting "extended base" pkgs weird conflicts showed up again. I tried deleting a few problem pkgs, sometime selected "check all archs" and later I got a solver "timeout" again :-( I increased the solver timeout to 240 secs (on a 2Ghz 2GB box!!) before I cancled that conflict test and gave up again:-( anyone at SUSE ever tested an update from 10.1 to 10.3 with network repos ???? small problem aside: when starting another conflict test, the solver timeout still is set to 240 secs and there is _no_ way to stop this run. you really have to wait the until timeout. it would be nice if there would be a CANCEL button for this case! obviously it would be even nicer if this problem would not happen at all;) anyone at SUSE ever tested an update from 10.1 to 10.3 with network repos (e.g. trying to reproduce my reports or just in generic tests)???? y2logs.tgz available if needed (again 36 MB!!). next I started another update on this partition without network repos. this time eveyrthing went fine -- I could select many more patterns, only two simple conflicts to resolve, update from 10.1 to 10.3 started ok. bad news 1: I can't reproduce this test on the T60 (but I still have the AMD1200 with 10.1 partition;) bad news 2 (extra ticket coming): the updated system does not boot anymore :-( it hangs just after "GRUB loading stage2.." hmmmmm.... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.