Bug 412166

Summary: java-1_6_0-sun update can't be installed because of dependency problems, but updater gives no user feedback
Product: [openSUSE] openSUSE 11.0 Reporter: Christian Boltz <suse-beta>
Component: JavaAssignee: Thomas Göttlicher <tgoettlicher>
Status: VERIFIED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: meissner
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper.log

Description Christian Boltz 2008-07-25 11:10:56 UTC
Created attachment 229997 [details]
zypper.log

Installing the java-1_6_0-sun update (updateinfo-java-1_6_0-sun-97.xml from 11.0 test updates) fails with opensuseupdater-kde.

The reason can be found in zypper.log:

[zypp] SATResolver.cc(problems):990 Encountered problems! Here are the solutions:
[zypp] SATResolver.cc(problems):990
[zypp] SATResolver.cc(problems):994 Problem 1:
[zypp] SATResolver.cc(problems):995 ====================================
[zypp] SATResolver.cc(problems):999 patch:java-1_6_0-sun-97.noarch steht in Konflikt mit java-1_6_0-sun-plugin.i586 < 1.6.0.u7-1.1 angeboten von java-1_6_0-sun-plugin-1.6.0.u6-8.i586
[zypp] SATResolver.cc(problems):1000 ------------------------------------
[zypp] SATResolver.cc(problems):1020 behalten Sie java-1_6_0-sun-plugin-1.6.0.u6-8.i586 nicht installiert
[zypp] SATResolver.cc(problems):1020 behalten Sie java-1_6_0-sun-1.6.0.u6-8.i586 nicht installiert
[zypp] SATResolver.cc(problems):1188 ------------------------------------
[zypp] SATResolver.cc(problems):1025 patch:java-1_6_0-sun-97.noarch nicht installieren
[zypp] SATResolver.cc(problems):1188 ------------------------------------
[zypper] zypper-prompt.cc(get_prompt_reply):181 running non-interactively, returning c

This means:
- zypper cancels the operation
- installation of other updates is also blocked/cancelled as long as the java
  update is selected
- there is _no visible feedback_ (like an error message) shown to the user!
- opensuseupdater-kde shows the same updates as available again (no surprise)

I think that this bug needs to be fixed at two places:
a) in the update, it should be installable without conflicts
b) in zypper - blocking all updates because of one faulty update isn't a good 
   idea :-(  [tell me if I should open a separate report for this]

The attached zypper.log contains only this zypper run (with just the java update selected) to make reading easier.
Comment 1 Jan Kupec 2008-07-28 11:44:41 UTC
It seems you have locked java-1_6_0-sun and the plugin packages. Can you confirm ('zypper ll', or run the command interactively to get the dependency problem dialog)?
Comment 2 Jan Kupec 2008-07-28 11:46:47 UTC
Also check if removing the lock solves your problem.

Regarding point b) yes, that would make sense, please open a separate request, assign to me directly.
Comment 3 Christian Boltz 2008-07-28 12:27:02 UTC
# zypper ll
# | Name                  | Typ     | Repository
--+-----------------------+---------+-----------
1 | libMagick++1          | package | (jedes)
2 | java-1_6_0-sun        | package | (jedes)
3 | java-1_6_0-sun-plugin | package | (jedes)

Hmm, I wonder when/why I locked these packages, but anyway: after removing the locks, I was able to install the updates. (Sorry for the false alarm!)

Since this makes a) probably invalid, I'd propose to handle b) here instead of duplicating it to another report.

Maybe I should add
c) no visible feedback (error dialog) in opensuseupdater-kde (separate report?)
Comment 4 Jan Kupec 2008-07-28 12:37:03 UTC
b) separate report (for me), c) here :O) Thomas?
Comment 5 Thomas Göttlicher 2008-07-28 13:08:42 UTC
Jano, is this a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=399661#c30 where we decided that the updater applet should handle PROMPT_DEP_RESOLVE with a (better) error message?
Comment 6 Jan Kupec 2008-07-28 13:27:59 UTC
Yes, it is. OK i'm closing it. Christian, a new report for b) would still be fine, so that it clear right from the initial description what is the bug about. Thanks gyus.

*** This bug has been marked as a duplicate of bug 399661 ***
Comment 7 Christian Boltz 2008-07-28 14:16:36 UTC
b) split to bug 412640

VERIFIED that a) is invalid and c) is a duplicate.