Updates to remove python2 subpackages
sudo dnf upgrade --advisory=FEDORA-2018-5537c09e6d
This update has been submitted for testing by swt2c.
This update has been pushed to testing.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for batched by swt2c.
This update has been submitted for stable by swt2c.
These don't seem to have added obsoletes. This causes trouble on update, e.g.:
- package python2-libconcord-1.3-3.fc29.noarch requires libconcord = 1.3-3.fc29, but none of the providers can be installed
- cannot install both libconcord-1.3-5.fc29.x86_64 and libconcord-1.3-3.fc29.x86_64
- cannot install both libconcord-1.3-3.fc29.x86_64 and libconcord-1.3-5.fc29.x86_64
- cannot install the best update candidate for package python2-libconcord-1.3-3.fc29.noarch
- cannot install the best update candidate for package libconcord-1.3-3.fc29.x86_64
I'm gonna fix libconcord, but you might want to fix the others too...
adamwill edited this update.
Karma has been reset.
This update has been submitted for testing by adamwill.
They are supposed to have been obsoleted by fedora-obsolete-packages...
I'm going to revert what you did and add the fedora-obsoleted-packages build to this update, any objections?
swt2c edited this update.
churchyard edited this update.
This update has been submitted for testing by churchyard.
Maybe a bit, because fedora-obsolete-packages is meant as a sort of backstop if there's no better option. You can't really rely on all systems having fedora-obsolete-packages installed; old long-upgraded systems don't, minimal installs may not.
i think having python3-libconcord do the obsolete is much more robust in this case, as anyone who had python2-libconcord installed in the past likely had it installed because congruity required it, and now congruity requires python3-libconcord. So it seems pretty safe to believe that people upgrading will get python3-libconcord installed, and it'll obsolete python2-libconcord.
Heck, I don't think there's any reason we can't have both of them carry the Obsoletes. That doesn't hurt anything, I don't think.
(We kinda really need an RPM Replaces: tag to mean "this package should replace this other retired package on upgrade, but doesn't exactly Provide it, strictly speaking...")
no package update issues
This update has been submitted for stable by pwalter.
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.