Bugzilla – Bug 510139
"zypper rm mozilla-xulrunner181" installs seamonkey
Last modified: 2016-01-29 15:44:45 UTC
This is slightly uninuitive and seem seriously broken: % sudo zypper rm mozilla-xulrunner181 Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: seamonkey The following package is going to be REMOVED: mozilla-xulrunner181 Overall download size: 8.5 MiB. After the operation, additional 10.6 MiB will be used. Continue? [_y_/n/p/?]: Now, the original bug I wanted to report was the following list of packages on my FACTORY system, and it is entirely possible, if not likely, these two are related: # rpm -qa | grep xulrunner | sort mozilla-xulrunner181-1.8.1.19-0.1 mozilla-xulrunner190-1.9.0.10-1.8 mozilla-xulrunner190-gnomevfs-1.9.0.10-1.8 mozilla-xulrunner190-translations-1.9.0.10-1.8 mozilla-xulrunner191-1.9.1b4-2.2 mozilla-xulrunner191-gnomevfs-1.9.1b4-2.2 mozilla-xulrunner191-translations-1.9.1b4-2.2
Created attachment 296361 [details] Solver testcase: package.xml.gz
Created attachment 296362 [details] Solver testcase: solver-system.xml.gz
Created attachment 296363 [details] Solver testcase: solver-test.xml
Created attachment 296364 [details] Solver testcase: y2log
Hah! I always wondered why nobody complained about this. Currently deleting packages only block the installation of packages of the same name. Actually hard to fix, a possible solution would be an "removeonly" option in the solver (which basically disables all repositories). That would help zypper, but not the YaST UI. I don't think this is related to your multiple xulrunner versions, though.
The reason here is that something probably requires libgtkembedmoz.so, and seamonkey provides it. You should deinstall the requirer too
(In reply to comment #0) > Continue? [_y_/n/p/?]: You can also enter 'p' to show the problem which led the solver to force this solution. 'p' restarts the solver in --no-force-resolution mode.
So what do we do about this? This does not seem to happen too often, and it's not that much of a bug, why just not close it?
You could fix that for 'zypper rm' by using just the @System repository. A different way would be to make the "choice rules" I added before going on vacation hard rules (currently they are weak). This would also have some other nice benefits, but I have to do some more experiments and thinking first. Nothing for 11.2, I'm afraid.
Fixed in zypper-1.12.31 *** This bug has been marked as a duplicate of bug 606220 ***