|
Bugzilla – Full Text Bug Listing |
| Summary: | Check update display for software management | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Markus Elfring <Markus.Elfring> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
solver test case
log file solver test case detailed log |
||
|
Description
Markus Elfring
2009-07-23 13:57:17 UTC
Markus, this seems perfectly OK. 'zypper lu' only shows updates installable with no problems (dependencies, vendor changes). If you want to see all installed packages for which newer versions exist, do 'zypper lu -a'. The difference between these two lists then are, obviously, the packages not upgradable due to dependency problems, or those which need a change of (untrusted) vendor. bug #483179 is not related to this If i overlooked something, please reopen and explain. Thanx! I'm sorry. - I overlooked that some vendor changes were really needed for several components. 1. The situation for the package "liblzo2-2-32bit" remains to be resolved for the command "zypper lu". 2. The command "zypper lu --all" shows the following still after recent updates. v | openSUSE BuildService - Java | xmlbeans | 2.1.0-3.9 1. I overlooked that 'lu' and 'up' disagree on whether the package is installed. Can you please reproduce and attach zypper.log? 2. OK, but what about it? Is that wrong? Created attachment 307652 [details]
log file
Why do the subfunctions disagree on which software is recent on my system?
Sonne:~ # zypper update liblzo2-2-32bit xmlbeans
Loading repository data...
Reading installed packages...
Package 'liblzo2-2-32bit' is not installed.
Resolving package dependencies...
Nothing to do.
Sonne:~ # zypper info xmlbeans
Loading repository data...
Reading installed packages...
Information for package xmlbeans:
Repository: openSUSE BuildService - Java
Name: xmlbeans
Version: 2.1.0-3.9
Arch: noarch
Vendor: openSUSE Build Service
Installed: Yes
Status: out-of-date (version 2.1.0-2.29 installed)
Installed Size: 3.0 M
Summary: XML-Java binding tool
thanx c#3, 1: this is already reported in bug 471278, we'll track it there. c#4: this could be because of repository priorities (maybe the xmlbeans-2.1.0-2.29 are in a repo with lower priority?). Solver testcase would tell; is the one from c#0 still relevant, or can you get me a new one? (In reply to comment #5) > c#3, 1: this is already reported in bug 471278, we'll track it there. I guess that my issue is a little bit different because of an update notification for an uninstalled component. https://bugzilla.novell.com/show_bug.cgi?id=483179#c5 > Solver testcase would tell; is the one from c#0 still relevant, > or can you get me a new one? The attachment #307219 [details] is still applicable. Created attachment 309791 [details]
solver test case
Can this current test data help better to resolve any open issues?
Created attachment 309797 [details]
detailed log
This file was the result of the following command.
Sonne:~ # ZYPP_FULLLOG=1 ZYPP_LOGFILE=/home/elfring/Projekte/YaST/zypper524625b.log zypper update liblzo2-2-32bit xml-commons-resolver xmlbeans
Sure, thanx! Wow, quite a repo list :O) So here are the answers using <whatprovides provides="..."> in the sovler-test.xml and /usr/lib/zypp/testsuite/bin/deptestomatic.multi solver-test.xml: ################################################################# poolItems providing 'liblzo2-2-32bit' U__s_(15761)liblzo2-2-32bit-2.03-2.29.x86_64(Haupt-Repository_(OSS)_11.1) => liblzo2-2-32bit is really not installed (the U indicates that), so no issue here. ################################################################# poolItems providing 'xml-commons-resolver > 1.1-238.16' U__s_(24400)xerces-j2-xml-resolver-2.8.1-239.13.noarch(Java) U__s_(24207)xml-commons-resolver-1.1-238.17.noarch(Java) U__s_(12277)xerces-j2-xml-resolver-2.8.1-238.15.noarch(Haupt-Repository_(OSS)_11.1) I__s_(4016)xerces-j2-xml-resolver-2.8.1-239.13.noarch(@System) => the already installed xerces-j2-xml-resolver-2.8.1-239.13 already provides 'xml-commons-resolver > 1.1-238.16'. Zypper should report this. This bug is already fixed in latest zypper (maybe even 11.2) see bug 463772. ################################################################# poolItems providing 'xmlbeans > 2.1.0-2.29' U__s_(24216)xmlbeans-mini-2.1.0-3.3.noarch(Java) U__s_(24213)xmlbeans-2.1.0-3.10.noarch(Java) I__s_(4066)xmlbeans-mini-2.1.0-3.3.noarch(@System) => the already installed xmlbeans-mini-2.1.0-3.3 already provides xmlbeans > 2.1.0-2.29, and xmlbeans-2.1.0-3.10.noarch(Java) will not install because of vendor change. This should be reported by zypper, the problem is tracked in bug 555296. ################################################################# So, we need to fix bug 555296, and we'll be fine, right? *** This bug has been marked as a duplicate of bug 555296 *** |