I'm starting to wonder where the better
value is: sticking closer to upstream or preserving the
imagefactory functionality (in this particular case). I haven't
diligently kept notes, but it seems that whenever I deploy kojid
on a newer Fedora release there is always trouble in getting
things working. Installing yum, which wasn't a Requires got me to
where simple buildArch tasks would succeed but livemedia tasks
aren't working because of similar missing Requires on pycdio and
python2-kickstart.
To be clear, I'm not faulting anybody's
decisions. I'm just having more troubles with Koji packaging than
most things on offer in Fedora. Maybe that's just the nature of
something that is so flexible where many features are considered
optional. Mix in a little py2->py3 evolution and it's even
more of a dark and twisty path.
On 5/13/19 3:45 PM, Michael McLean
wrote:
Note that the koji.spec that Koji ships with should
use python3 for kojid on Fedora >= 30. Fedora uses a
different spec, and as Neil points out, imagefactory
functionality is currently unavailable under py3.
_______________________________________________
koji-devel mailing list -- koji-devel@lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/koji-devel@lists.fedorahosted.org