Bugzilla – Bug 1106693
python2-pyliblzma does not conflict with python-pyliblzma
Last modified: 2018-08-31 13:35:05 UTC
When doing zypper dup on a tumbleweed-20180723 system, it reported this error:
from install of
conflicts with file from package
> rpm -qp --obsoletes /var/cache/zypp/packages/repo-oss/x86_64/python2-pyliblzma-0.5.3-4.2.x86_64.rpm
python-pyliblzma < 0.5.3-4.2
> rpm -qp --conflicts /var/cache/zypp/packages/repo-oss/x86_64/python2-pyliblzma-0.5.3-4.2.x86_64.rpm
Why don't our single-spec macros add the Obsoletes automatically?
Err: macros should add the Conflicts automatically
In my case the old package was from
devel:languages:python / openSUSE_Tumbleweed
but I think, official packages would have had the same trouble
because of the rename.
So an Obsolete indeed includes a Conflict, but here, the version numbers were inverted, because it switched from the dlp to repo-oss version
and thus no package conflict was considered.
The 'no-vendor-change' did not apply,
because python2-pyliblzma was a new package.