Bug 527903

Summary: zypper does not recognize the availability of updates
Product: [openSUSE] openSUSE 11.1 Reporter: Elmar Stellnberger <estellnb>
Component: libzyppAssignee: E-mail List <zypp-maintainers>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: dmacvicar, ma
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper.log
available updates checkroot could not install because of unsatisfied dependencies
all available updates found by checkroot
output of zypper -lu, after checkroot has performed update
zypper.solverTestCase for another update
zypper.solverTestCase for another update (part2)
error message and zypper.log

Description Elmar Stellnberger 2009-08-04 10:01:44 UTC
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE

  As far as I can remember I have already filed a bug about this. Unfortunately  I could not find it again (perhaps deleted).
  'checkroot -n --update /' has found and installed 40 updates and could install 20 of them directly after 'zypper up' has reported no more updates to be available. Please have a look at this (checkroot: www.elstel.com/checkroot).

Reproducible: Sometimes
Comment 1 Elmar Stellnberger 2009-08-04 10:04:06 UTC
Created attachment 310289 [details]
zypper.log
Comment 2 Elmar Stellnberger 2009-08-04 10:05:52 UTC
Created attachment 310291 [details]
available updates checkroot could not install because of unsatisfied dependencies
Comment 3 Elmar Stellnberger 2009-08-04 10:07:10 UTC
Created attachment 310293 [details]
all available updates found by checkroot
Comment 4 Elmar Stellnberger 2009-08-04 10:19:32 UTC
old bug: Bug 520148
Comment 5 Elmar Stellnberger 2009-08-04 10:23:21 UTC
An additional zypper refresh/up did not find any of the remaining 20 updates.
Comment 6 Jan Kupec 2009-08-04 10:46:17 UTC
does "zypper lu --all find them"?
Comment 7 Elmar Stellnberger 2009-08-04 15:09:11 UTC
At least those updates which checkroot could not install seem to be listed by zypper -lu (should have tried this before) though with different version number.
Comment 8 Elmar Stellnberger 2009-08-04 15:11:28 UTC
Created attachment 310423 [details]
output of zypper -lu, after checkroot has performed update

You may yourself have a look (updates*.lis & zypper-lu).
Comment 9 Michael Andres 2009-08-05 12:52:02 UTC
Problem with this command output is, that the information about the installed system is missing. Without installed versions, vendor, repositories... it's hard to tell which command is right and which is wrong.

Please attack a solver testcase, it provides all this information.


At least zyppers suggestion to update ppracer from os11.0-oss looks suspicious, but depends on the vendor of the installed one and the one from the tuxracer repo.
Comment 10 Elmar Stellnberger 2009-08-08 11:24:40 UTC
Created attachment 311454 [details]
zypper.solverTestCase for another update

This time checkroot said the following
(I can not believe that on my own: 187 updates not discovered by zypper ?!):
19 updates could not be installed; you may try chroot & zypper up.
187 packages updated successfully.
Comment 11 Elmar Stellnberger 2009-08-08 11:37:37 UTC
Created attachment 311455 [details]
zypper.solverTestCase for another update (part2)
Comment 12 Alexander Orlovskyy 2009-10-16 13:18:09 UTC
Created attachment 322875 [details]
error message and zypper.log
Comment 13 Alexander Orlovskyy 2009-10-16 13:19:28 UTC
I got this bug on openSUSE 11.2 RC1

Executed command: zypper lu --all
Comment 17 Jan Kupec 2010-02-12 18:00:08 UTC
'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'. 'zypper up' only updates packages shown by 'zypper lu'.

In your testcase, all the packages that were not updated were either from repo with lower priority, or would need a vendor change, or must have had some other installability problem.

So this is not a bug so i'm closing it as invalid.