Bug #40099
build/ops: python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
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.
Related issues
History
#1 Updated by Nathan Cutler 10 months ago
- 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
#2 Updated by Nathan Cutler 10 months ago
- Description updated (diff)
#3 Updated by Nathan Cutler 10 months ago
- 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
#4 Updated by Nathan Cutler 10 months ago
- Status changed from New to Fix Under Review
#5 Updated by Nathan Cutler 10 months ago
- Pull request ID set to 28352
#7 Updated by Nathan Cutler 10 months ago
- Copied to Backport #40232: nautilus: build/ops: python3 pybind RPMs do not replace their python2 counterparts on upgrade even though they should added
#8 Updated by Nathan Cutler 10 months ago
- Status changed from Pending Backport to Resolved