The QT5 issue was fixed in the bug I'm cloning, but there is still the question of whether to switch upstream permanently to be addressed. +++ This bug was initially created as a clone of Bug #1328923 +++ Description of problem: The original AQEMU upstream [1] is effectively dead and has been since at least 2013. As a result downstream users and packagers, including Fedora, are carrying an increasing number of patches [2]. Tobias Gla recently contacted me indicating that he has updated AQEMU for QT5 as well as applying the various downstream fixes folks were carrying and created a fork of the project [3] that he intends to keep active. Originally in light of the dormancy of upstream I was intending to orphan the AEMU package in F25, given this new activity though I would like to instead move to packaging the new/updated repository. This bug is to track that desire, notwithstanding that I need to double check whether this is feasible from a process perspective. [1] https://sourceforge.net/projects/aqemu/ [2] https://retracile.net/blog/2014/12/29/19.00 [3] https://github.com/tobimensch/aqemu
I can definitely vote +1 for switching upstream. Mentioned reasons about dead old upstream and additional new feature from new upstream are retracable. Another obvious good reason is the support for Qt5: https://github.com/tobimensch/aqemu/blob/master/CMakeLists.txt#L194
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Just reviewing, the new upstream looks pretty dead at this point as well. I've recently applied a minor patch to ensure the SRPM will compile with GCC 10 in a future Fedora release, but at this point it's unclear what can be done to actively keep this package going.
What about retiring it? On Fedora 37 and 38, between other things, starting it lead to "Segmentation fault (core dumped)"
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Automation has figured out the package is retired in rawhide. If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement