I'm using koji as a python package in my scripts. Usually I develop them
inside of a virtual environment. I do not use system packages in
Currently I'm not able to install koji and it dependencies inside
virtualenv easily. Having koji in PiPy would help me. That way I can
just specify it in my requirements.txt or in install_requires of my
setup.py. I *guess* one way to do that is to have setup.py in koji
code and add some extra steps as part of the release process to publish
What do you think about this?
For some time now I use my own setup.py. I guess it is not ready for PR
so I'd love to see comments on this as well:
 Among other reasons I'd like to have environment isolated from the
system as much as possible.
 I have never maintained package on PiPy.
I tried to add packages to the "build" and "srpm-build" groups so that
they will be installed for builds. The packages were successfully added,
but they were not installed during builds. I looked in the
"group_package_listing" table and notices that the "type" field of the
new packages was "mandatory", but the type of old packages was
"default". Changing type to "default" fixed the problem.
We're using koji 1.11.0.
Is this a known issue?
Mátyás (Mat) Selmeci
Open Science Grid Software Team / Center for High-Throughput Computing
University of Wisconsin-Madison Department of Computer Sciences