https://bugzilla.novell.com/show_bug.cgi?id=291361 Matej Horvath changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jsuchome@novell.com |screening@forge.provo.novell| |.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=291361#c2 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com Status|NEEDINFO |ASSIGNED Info Provider|locilka@novell.com | --- Comment #2 from Lukas Ocilka 2007-07-12 08:45:50 MST --- In my opinion, /var/lib/YaST2/continue_installation contains where installation should (re)start and Online Update shouldn't rely on existence of that file. Installation creates and removes that file. I'd suggest Online Update did the same. Handle its own file for itself. Both creating and removing. Online Update knows that is is going to restart YaST or system... It's very unclear when some file is created by one module and checked for existence by another module, then removed (or not removed) by the first one. Why not /var/lib/YaST2/continue_online_update or something similar? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=291361#c4 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Jiří­ Suchomel 2007-07-13 04:41:38 MST --- Fixed in yast2-online-update-2.15.19 (with /var/lib/YaST2/continue_you). -- 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.