On 10. 05. 20 20:48, Kevin Fenzi wrote:
Basically we are switching from 'I go and install fedora-obsolete-packages and have opted in to it' to 'I have to go explictly exclude it to keep my obsolete packges'.
As others have pointed out, this was never the case of 'I go and install fedora-obsolete-packages and have opted in to it' -- this was always the case of 'fedora-obsolete-packages obsoletes something I had installed, so it is pulled in by dep resolver'.
Is this ideal? No. But it has not been changed. (The changed part is fedora-obsolete-packages does not get installed in the process.)
A better solution to the problem fedora-obsolete-packages is trying to solve would be to use allowerasing on system-upgrade, but that is another can of worms, because it also removes packages that have broken dependencies, but were not intentionally removed.
The idea solution IMHO would be to allow erasing only the packages that do not belong to a distupgrade repository. Possibly to have that option only for the Fedora repos, so packages installed from a thrid-party would not get erased.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
