https://bugzilla.novell.com/show_bug.cgi?id=215445 ------- Comment #1 from olh@novell.com 2006-10-26 13:32 MST ------- Created an attachment (id=102762) --> (https://bugzilla.novell.com/attachment.cgi?id=102762&action=view) bug215445.tar.bz2 -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215445 ------- Comment #3 from olh@novell.com 2006-10-27 00:10 MST ------- after the first 'skip' yast shows a popup 'finishing installation', then yast quits. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215445 andreas.hanke@gmx-topmail.de changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Blocker ------- Comment #5 from andreas.hanke@gmx-topmail.de 2006-10-27 10:55 MST ------- Raising to Blocker because I already know that this will - again - break installations as it did with 10.1 already. It's reproducible in the following way: - Create a YUM repo with A depending on B, B depending on C etc., until G - Modify C after the metadata have been generated, to simulate a read error - Use sw_single, select A for installation, it will pull in all dependencies - Do the installation. It will install G, F, E, and D. As soon as it tries to install C, it will inform you about the read error. - Select IGNORE. But what it will actually do is: ABORT. Expected result: IGNORE means IGNORE, so it should go on with B and A. Actual result: IGNORE is taken as ABORT, the installation is still completely cancelled because of one failed package, and it does not even run SuSEconfig afterwards. During a "real" system installation or upgrade, it would probably even leave the hard disk in a mess etc. It seems that the fix of bug 181658 just doesn't work. This is unfixable after the release because it breaks initial installation => Blocker -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215445 ------- Comment #6 from andreas.hanke@gmx-topmail.de 2006-10-27 10:56 MST ------- Created an attachment (id=102863) --> (https://bugzilla.novell.com/attachment.cgi?id=102863&action=view) YaST2 logfiles -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=215445 dmacvicar@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #8 from dmacvicar@novell.com 2006-11-02 08:20 MST ------- We sat down with Michael to track down this bug. It is not easy to fix due to some broken provideFile semantics. provideFile, offers the user to abort, retry and ignore, without having any semantics for those actions. Anyway, we found a bug where the context information was lost in a exception catch, fixing this makes commit finish the installation. Note, inmediately after skiping a package the rest fail due to dependencies, so they are retried with --nodeps. There is no progress bar anymore, and you have to wait till commit tries to do whatever it can, with no guarantees of a broken system. As Michael said, never expect things to finish if you skip glibc. Fix in zypp r4469. Thanks Andreas for the quality of the bugreport, especially your testing material. -- 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, or are watching someone who is.