Bug #40099
closed
build/ops: python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should
Added by Nathan Cutler almost 5 years ago.
Updated almost 5 years ago.
Description
In SUSE, nautilus and above is 100% Python 3, so when upgrading to nautilus we need to make the python3-* packages replace their Python 2 counterparts.
If we don't do this, the old python-{rados,rbd,cephfs,rgw} RPMs remain on the system and conflict with the new python3-* packages.
- Subject changed from build/ops: on SUSE as of nautilus, python3 pybind RPMs do not replace their python2 counterparts to build/ops: on SUSE as of nautilus, python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should
- Description updated (diff)
- Subject changed from build/ops: on SUSE as of nautilus, python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should to build/ops: python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should
- Status changed from New to Fix Under Review
- Pull request ID set to 28352
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #40232: nautilus: build/ops: python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF