https://bugzilla.novell.com/show_bug.cgi?id=471369 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=471369#c1 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.co | |m.au --- Comment #1 from Scott Couston 2009-02-02 19:30:27 MST --- Apologies the conflict that is created by online update in a default installation as above is 1. un-install cifs-mount3.2.4-4.32.x86._64 2. Ignore conflict and proceed. I chose option 1 with no further issues or conflicts but I cannot understand why the conflict exists in the first instance -- 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=471369 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Update Phase on 3.5 KDE |Update Phase on 3.5 KDE |Installation creates an |Installation creates an |'Unresolvable Update |'Unresolvable Update |Conflict' |Conflict' -- | |cifs-mount3.2.4-4.32.x86._6 | |4 -- 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=471369 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=471369#c2 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.co | |m.au --- Comment #2 from Suresh Jayaraman 2009-02-19 21:54:53 MST --- Thanks for bug report. Do you see the same error if you try to update manually? i.e. download the update (http://download.opensuse.org/update/11.0/rpm/x86_64/) and doing rpm -Uvh <new cifs-mount rpm> --test This would help us to isolate the problem. Also I don't see the rpm you mentioned, the latest I see is cifs-mount-3.2.4-4.3.x86_64.rpm, It's odd. Samba Maintainers: Does anything change in winbindd recently so that depends on cifs-mount? -- 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=471369 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=471369#c4 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@virginbroadband.co | |m.au --- Comment #4 from Suresh Jayaraman 2009-02-22 22:26:13 MST --- Yes I would wait. Also, the cifs version number you had mentioned is confusing. Because in the repo, the latest I see is 3.2.4-4.3 whereas you mentioned 3.2.4-4.32? Can you check the version once more? -- 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=471369 User alpha096@virginbroadband.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=471369#c6 --- Comment #6 from Scott Couston 2009-02-26 16:27:44 MST --- During a Repeat of the above environment the online update phase now has 3 separate updates that require Yast to re-start. The above situation only had 2. The second online update phase only downloads a new version of zipper and the Yast will restart for the third online update phase which is the biggest as new versions of Yast have been downloaded and then restarted and now zipper downloaded and then restarted. It is clearly apparent that the reason you could not reproduce and why I cannot reproduce this now is that there is an additional online update second phase that updates zipper which resolves the original conflict. The final 3rd online update phase goes ahead without incident now and finished without any dependency issues. You are probably in a far better position to understand why the new online update of zipper, resolves the dependency issues that created this bug in the first instance. Please close this bug as fixed before I turn it into an enhancement request for ANY installation dependency issue during any installation gets displayed in a separate window that permits copy and save text to a file on HDD rather than forcing you to go through huge Yast Installation logs. A simple Window with dependency problems that could be saved text into *.log file on HDD could make your life much easier for debugging - however I am too tired to do this ;-) -- 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.