http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c1 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@sven-seeberg.de Flags| |needinfo?(mail@sven-seeberg | |.de) --- Comment #1 from Michael Andres --- It almost looks like you've got an old zypper together with a new libzypp. may it be you performed the 'zypper dup' with the old 15.0 repos still enabled? Anyway: The 'zypper dup' command creates a resolver testcase at /var/log/updateTestcase-YYYY-MM-DD-hh_mm_ss (date the dup command was executed). Please pack the output directory together with /var/log/zypper.log and attach it to the bugreport:

$ cd /tmp $ tar cvjf zypper.updateTestCase.tar.bz2 /var/log/updateTestcase-'YYYY-YOUR_DATE...'

In case the testcase exceeds the 10MB limit for bugzilla uploads, you can use 'split' to divide the file into smaller pieces:

$ split -b 10M --additional-suffix=-zypper.updateTestCase.tar.bz2 zypper.updateTestCase.tar.bz2

The created pieces will be named like this: xaa-zypper.updateTestCase.tar.bz2 xab-zypper.updateTestCase.tar.bz2 xac-zypper.updateTestCase.tar.bz2 ...

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c3 --- Comment #3 from Sven Seeberg --- Created attachment 809018 --> http://bugzilla.opensuse.org/attachment.cgi?id=809018&action=edit List of active repos -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c5 --- Comment #5 from Sven Seeberg --- What I also found: zypper was not installed. After fixing some DNS issues, I was able to run "zypper in zypper". Not sure if that makes sense. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c7 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mail@sven-seeberg | |.de) --- Comment #7 from Michael Andres --- (In reply to Sven Seeberg from comment #5)

What I also found: zypper was not installed. After fixing some DNS issues, I was able to run "zypper in zypper". Not sure if that makes sense.

How can you update zypp with zypper, if zypper is not installed? An explanation would be a broken rpm database. It could have hidden the fact that zypper was installed (and probably other packages as well). This would also explain why zypper was not updated in "zypper dup". It stayed old because it was not seen. To be safe, you should run (as root): rpm --rebuilddb This will rebuild all database index files. If this is done, you should repeat the `zypper dup` to make sure no updates are missing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c9 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mail@sven-seeberg | |.de) --- Comment #9 from Michael Andres --- Well, your problem is (hopefully) solved. The testcase revealed that there seem to be a lot of packages still from leasp-15.0, and some, like zypper, are not visible. This is a strong hint to a broken rpm database. The question still is, whether zypper could have recognized this. The only source of information left is the zypper.log showing the initial 'zypper dup' that led to this report. If it's still available on your system, please attach it and I'll have a closer look at it. ---- Please attach the zypper logfile /var/log/zypper.log (or an older and compressed /var/log/zypper.log-YYYYMMDD.xz) that shows the reported behavior. To see the execution dates and zypper commands included in a logfile you can install the zypper-log package and execute: zypper-log To extract the log of a specific command use zypper-log pid See the manual page zypper-log(8) for details on how to read older (rotated) zypper-log files. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1139900 http://bugzilla.opensuse.org/show_bug.cgi?id=1139900#c11 --- Comment #11 from Sven Seeberg --- Now that I think about it: It could be that the broken RPM database is related to an event in the past. I remember that I did some hackish things to repair this machine after I broke something. I do not remember the details, but the fix was something like forcefully/manually reinstalling all packages. If I remember correctly, then it was definitely human (my) error. The only question that remains is, whether it could have been detected. -- You are receiving this mail because: You are on the CC list for the bug.