In line with the Mass Python 2 Package Removal [0], the following (sub)packages of libemu were marked for removal: * python2-libemu According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query. Please remove them from your package. As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here. We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0]. [0] https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
The removal seems nontrivial, there are Python related hacks, could you please take a look?
The beta freeze is at 2019-03-05. Are you responsive?
Consider this a nonresponsive BZ This the first reminder. Are you responsive? https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
Hello, as there is not working python3 binding for libemu, I would rather keep the python2 package for it. Michal Ambroz
Thanks for reaching back. The general idea behind https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal is that we get rid of leaf packages. python2-libemu is a leaf package, nothing in Fedora uses it. If we'd keep python2 packages around because they are not ported to python3 yet, we would never get rid of Python 2. Is there an upstream plan for Python 3? If so we might keep it around for a while knowing it will be ported soon. However if there is no plan, I'd rather remove it.
Hello, I understand you want to get rid of the leaf packages, but being leaf doesn't mean that nobody is not running related code to it. as I said, if python2 is going to be in Fedora 30, personally I would rather for this time keep the python2 binding as well as I am using it. Currently the libemu doesn't have python3 binding to switch to. I hope the upstream will come with python3 binding as the end-of-life of python2 is approaching.
We are after Fedora 30 beta freeze anyway, so i don't mind keeping it there. Yet this will eventually need to go away.
Hey, any update on the upstream situation?
https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages 1) What are the upstream plans/timelines regarding Python 3?
Could you please provide the requested information?
This package was retired.
I thought you were up to remove just the sub-package of the python2-libemu binding to libemu not whole libemu. Now related build of dionaea is failing because of that. Please can we get the libemu back? Michal Ambroz
libemu was retired 3 months ago because it was orphaned for 6+ weeks at the time. it was orphaned based on the procedure described in https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages after trying to get an answer since May. I'm sorry, but I cannot just get libemu back, there https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package - this would require package re-review without python2. Can provide a spec that builds libemu-devel without python2-libemu? If so, I'll gladly review it and help you get it back.
Hello > Can provide a spec that builds libemu-devel without python2-libemu? If so, I'll gladly review it and help you get it back. Sure - here it is building for rawhide - https://koji.fedoraproject.org/koji/taskinfo?taskID=38297118 Its simply having condition to build python2 only up till f30/rhel7 - no big deal about that. I still do not have working python3 binding, but I keep trying. > libemu was retired 3 months ago because it was orphaned for 6+ weeks at the time. Yes .. sorry my fault - I thought we already have agreement on this bug report. The libemu library is useful and AGAIN as with impacket - it has binary /usr/bin tools useful for analyzing binary shellcodes. This time binary tools working even without the python2 binding. In my opinion it should not have become victim of the python2 witch-hunt in the first place. Simple removing the subpackage python2-libemu would do what you wanted to do. Instead you guys removed the package with tools and break other package depending on that without trying reaching me directly - congrats. I guess you guys are missing the point that we packagers work on the packages as volunteers over nights next to the day-jobs, there is just so much free time I can spend as volunteer contributing to Fedora. It is frustrating to me ending fixing the packages on one end and starting on the other end. I believe this python2 witch-hunt really is not building the community. This is exactly reason why people are rather building their own separate repositories as for example https://forensics.cert.org/ rather than contributing directly back to Fedora. Best regards Michal Ambroz
> Simple removing the subpackage python2-libemu would do what you wanted to do. I've asked for exactly that: https://bugzilla.redhat.com/show_bug.cgi?id=1634370#c1 > Instead you guys removed the package with tools and break other package depending on that without trying reaching me directly - congrats No need to get sarcastic here, we've tried to reach you, you haven't responded, the package got orphaned, you haven't reasoned, the package got retired. I'm sorry that your Fedora time is limited, but there were months of no response. We have a task to do and we are always open to communication and compromises. But when the other site remains silent for months, we must assume they are not interested. And when we remove a package, we are always glad to offer assistance bringing it back in case the maintainer actually responds, like it happened here. If the Package maintainer responsibilities [1] are impossible to keep for volunteer contributors, I suggest you rise that concern on the devel mailing list. The python2 "witch hunt" is a long term Fedora change approved by the Fedora Engineering Steering Committee, not my own whim. Anyway, discussing this won't get us anywhere. If you want my help with bringing back libemu, please meet me half way and open a package review request with the package from https://koji.fedoraproject.org/koji/taskinfo?taskID=38297118 [1] https://fedoraproject.org/wiki/Package_maintainer_responsibilities#Deal_with_reported_bugs_in_a_timely_manner
Package review request raised on https://bugzilla.redhat.com/show_bug.cgi?id=1762026
FEDORA-2019-2f434e991d has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2f434e991d
Trying to get single libemu spec working for all suppoted platforms before recompiling the dionaea for f32/f31.
Sorry, I have only read your comment after I've already built dionaea for F32.
libemu-0.2.0-12.20130410gitab48695.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2f434e991d
libemu-0.2.0-12.20130410gitab48695.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.