Hide Forgot
"rpl" is still using python2 and besides "dstat" one of the last two packages keep pulling the python2 stack while it's an interesting question why "#!/usr/bin/env python" points to python2, but anyways, "rpl" is not working with a python3-shebang (just tried) [root@buildserver:~]$ /usr/bin/env python Python 2.7.12 (default, Sep 2 2016, 14:46:00)
It's outside my realm of knowledge to analyse why rpl doesn't work with python 3, so I would welcome any assistance.
i would say it's not about "doesn't work" but about how it's built -> see https://bugzilla.redhat.com/show_bug.cgi?id=1374925 which leaves now "rpl" as the only python2 consumer on the inbound mailserver
What, specifically, about "how it's built" can be changed to make it work correctly with python3, given that, as you said in the original report, the script itself doesn't work with a python3 shebang? The package is very open to contributions.
Frankly i am no python developer - have you considered looking at the changes of the other package or just asking on the devel-list or tried to ping the person who brought "python3 as the default implementation" or even just ask upstream Just saying dunno to a end-user that is in the meantime pissed that he have to remove the package from machines where he like to get rid of two python stacks won't change anything
or just look what debian did https://packages.debian.org/sid/utils/rpl lists python3 as dependency and has BTW a newer version (1.5.7 while we are at 1.5.5) http://rpl.sourceforge.net/ "rpl was originally written for the Debian project"
Thank you for the research & information. Interestingly the upstream website still lists 1.5.5 as the latest version which is why I've not picked up a newer one. However you are right to point out that Debian (and the upstream github) have a newer one, which supports Python 3 (and therefore resolves this issue). It looks like the maintainer (and yes, the upstream maintainer is also the Debian maintainer) may have forgotten to update it. I'll take contact.
Fixed in rawhide.
thanks! would be nice to have that at least also backported to F25 pypolicyd-spf managed the change within the F24 lifecycle
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.