http://bugzilla.opensuse.org/show_bug.cgi?id=931273 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com --- Comment #2 from Stanislav Brabec --- Obsoletes is not sufficient in case of file conflict. A.spec Obsoletes: B says: Once the A is installed, B could be uninstalled A.spec Conflicts: B says: If B is installed, A cannot be installed A.spec Obsoletes: B + Conflicts: B says: Uninstall B before installation of A. ZYPP is not aware of file conflicts of A and B, and creates an update plan that first installs A and then uninstalls B. It will fail during checks. If you add both Obsoletes and Conflicts, it creates a plan where B is uninstalled first and the A is installed. To Michael Andres: Strictly speaking, it does not make sense to take obsolete package in account while checking for file conflicts. RPM itself keeps the new file if the order is reverse, isn't it? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=931273 --- Comment #4 from Stanislav Brabec --- Zypper dup called today reported yet another file collision: Problem: konsole4-part-4.14.3-2.1.x86_64 conflicts with kdebase4-workspace-branding-openSUSE provided by kdebase4-workspace-branding-openSUSE-13.2-6.64.x86_64 Solution 1: deinstallation of kdebase4-workspace-branding-openSUSE-13.2-6.63.x86_64 Solution 2: deinstallation of konsole4-part-4.14.3-1.1.x86_64 Solution 3: keep obsolete konsole4-part-4.14.3-1.1.x86_64 Solution 4: keep obsolete konsole4-part-4.14.3-1.1.x86_64 I had to manually select 2. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=931273 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #6 from Wolfgang Bauer --- (In reply to Raymond Wooninck from comment #5)

There is a fix for this on its way to Factory already.

I see you removed the Root Shell.profile from konsole4-part again. Why not just remove it from kdebase4-workspace-branding-openSUSE? I filed a pull request on github for that 2 weeks ago... https://github.com/openSUSE/kdebase-opensuse/pull/25 The profile can be used in the konsole-part as well, not just in the full blown konsole application. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=931273 --- Comment #8 from Wolfgang Bauer --- (In reply to Raymond Wooninck from comment #7)

(In reply to Wolfgang Bauer from comment #6)

...

The profile can be used in the konsole-part as well, not just in the full blown konsole application.

Konsole4-part was provided in order for KDE4 applications to still be able to launch a konsole from within that application. The main usage would be dolphin, where you have the Action "Start a terminal from here".

Dolphin allows to embed a Konsole-part in its window as well via Sidebars-> Terminal or F4 (Konqueror and Krusader too). That's what konsole4-part is actually used/needed for. Right-clicking on that embedded Konsole allows you to reach the profile settings/switch profiles. While the Root Shell.profile probably is not a critical feature, I can imagine situations where it might be useful. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=931273 http://bugzilla.opensuse.org/show_bug.cgi?id=931273#c11 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sbrabec@suse.com) | --- Comment #11 from Wolfgang Bauer --- I think the problems reported here are fixed since quite some time. -- You are receiving this mail because: You are on the CC list for the bug.