Comment # 19 on bug 1061208 from Michael Andres

(In reply to Patrick Finie from comment #18)
> In this instance the version of libzypp is a higher number in 15.0 than the
> 15.1 which may be where the zypper dup issue stems.

As I tried to explain: 'dup' will not look at the installed packages version. 

The 'dup' job requires an installed libzypp to be replaced by a version
provided by the enabled repos. If this can not be done, a conflict is raised. 

(You want the packages to come from the new distro, even if the distro decided
to downgrade some package)


If your repos provided lp15.1 and no lp15.0 packages, a 15.0 libzypp should not
have stayed in the system (unless no lp15.1 provided a libzypp).

As it nevertheless happened, the update testcase could have revealed why. It
contains enough information about the repos and systems content to be able to
replay 'dup's decisions.



! As there is a small chance that the old libzypp was seen due to a broken rpm
database index, you should run 'rpm --rebuilddb' (as root). Just to make sure
your database is ok.