On Sun, May 10, 2020 at 09:30:26PM +0200, Fabio Valentini wrote:
On Sun, May 10, 2020 at 8:49 PM Kevin Fenzi kevin@scrye.com wrote:
On Sun, May 10, 2020 at 08:20:52PM +0200, Miro Hrončok wrote:
On 10. 05. 20 18:37, Scott Talbert wrote:
On Sun, 10 May 2020, Barry Scott wrote:
I know that python2 is a dead language, but I have a need to use some python 2 code on one of my servers. It's clearly on me to maintain the old code if I choose to use it.
I use MoinMoin via mon_wsgi.
After upgrading to fedora 32 I took the trouble to install moin using the F31 package. And all was good.
But I just did my first dnf update and was surprised to find these lines in the log of the dnf update:
---> Package moin.noarch 1.9.10-3.fc31 will be erased ---> Package python2-mod_wsgi.x86_64 4.6.6-2.fc32 will be erased
What is forcing the erase? I need to workaround this.
Probably fedora-obsolete-packages: https://src.fedoraproject.org/rpms/fedora-obsolete-packages/blob/f32/f/fedor...
I don't know how to workaround it though as the f-o-p package doesn't actually get installed anymore - it's work happens through some dnf tricks now.
You should still be able to exclude the package in the dnf config:
$ cat /etc/dnf/dnf.conf [main] ... exclude=fedora-obsolete-packages
We really should have made this better announced/documented.
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'.
Huh? I don't think how fedora-obsolete-packages works, at least not for a while ... I have never manually installed fedora-obsolete-packages, it was only ever automatically pulled in and installed because it "Obsoletes: something-I-had-installed" before a system upgrade.
Yeah, it wasn't necessary to request f-o-p explictly. Packages that were added to f-o-p in the past were added when they broke upgrades. So without f-o-p, the upgrade wouldn't go through because of broken deps, and dnf would pull in f-o-p automatically to make the transaction viable.
We now add some packages more proactively, even when they don't block an upgrade, but f-o-p is still used for many packages that would block an upgrade and f-o-p would still be required to satisfy deps for any fedora-version upgrade and would still be pulled in. So the magic trick that makes f-o-p non-installable doesn't change much.
Zbyszek