In line with the Mass Python 2 Package Removal [0], the following (sub)packages of python-aexpect were marked for removal: * python2-aexpect 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. If you do the change yourself, it would help us a lot by reducing the amount of packages we need to mass change. 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
python2-aexpect is still needed by the python-avocado package within the avocado:stable and avocado:latest module streams--which are not yet ready to fully abandon Python 2.
Modules are something our automation is not aware of and given the state of modules I'm honestly not eager to change that. Can we put python2-aexpect to that module and drop it form rawhide?
(In reply to Miro Hrončok from comment #2) > Modules are something our automation is not aware of and given the state of > modules I'm honestly not eager to change that. Well, your automation is ignoring valid dependencies... > Can we put python2-aexpect to that module and drop it form rawhide? Thank you for the excellent suggestion. I've already started the ball rolling on that.
> Well, your automation is ignoring valid dependencies... IMHO what a module needs shall be in that module (unless a handful of modules needs it). In that aspect, the automation is correct, except that there's still a human intervention needed like in this case. Thanks for that. > I've already started the ball rolling on that. \o/
> Well, your automation is ignoring valid dependencies... I think I need to chime in as co-author of that automation. AFAIK, the last discussion on these matters in fedora-devel was https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QEVS32O2LP7DFFIFXSC7IBQ7FNVGYMLY/ Read the thread for full context, but basically, automation for checking module contents is very hard to write – and even more so for people who don't deal with modularity regularly. But Modularity WG is working on making these things easier, so I don't want to spend time now to learn about all the pieces and try to pull them together. I'm sorry that all this puts some of the burden on you.
Package retired from rawhide. I guess we'll deal with the modular one day.
(In reply to Miro Hrončok from comment #6) > Package retired from rawhide. I guess we'll deal with the modular one day. "stable" and "latest" branches of the package were created and added to the corresponding "stable" and "latest" streams of the "avocado" module. Note: the package temporarily appeared to completely disappear from Rawhide for a few days due to a combination of compose problems in combination with poor timing of the package retirement.