koji-devel August 2017

koji-devel@lists.stg.fedorahosted.org

5 participants
4 discussions

koji in PiPy/support of setup.py
by Pavol Babincak 04 Oct '17

04 Oct '17

Hi, 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[1] in virtualenv. 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*[2] 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 it there. 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: https://pagure.io/fork/pbabinca/koji/blob/setup_WIP/f/setup.py [1] Among other reasons I'd like to have environment isolated from the system as much as possible. [2] I have never maintained package on PiPy. -- Pavol Babincak

8 12

using add-group-pkg to add to build groups does not work
by Mátyás Selmeci 23 Aug '17

23 Aug '17

Hi, 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? Thanks, -Mat -- Mátyás (Mat) Selmeci Open Science Grid Software Team / Center for High-Throughput Computing University of Wisconsin-Madison Department of Computer Sciences

2 2

dropping importBuildInPlace call in 1.15
by Michael McLean 14 Aug '17

14 Aug '17

https://pagure.io/koji/issue/553 The importBuildInPlace call is a strange artifact from long ago. I'd like to drop it in 1.15. If you are for some reason relying on this call, please speak up.

1 0

Content generator - rpm components not "linked"?
by Stanislav Ochotnicky 08 Aug '17

08 Aug '17

Hi folks, so we finally managed to enable Module Build Service as a CG. This is a first sort-of working module build: https://koji.fedoraproject.org/koji/buildinfo?buildID=950386 This is the metadata.json for it: https://kojipkgs.fedoraproject.org/packages/testmodule/master/2017080413511… The output section has a yaml file (the modulemd) which has components - all rpms that were built for that given module. As far as I can tell there should be "Installed RPMs" link here: https://koji.fedoraproject.org/koji/archiveinfo?archiveID=54563 But for some reason isn't... Any idea why that would be? Quick look through kojihub sources didn't reveal anything. Ralph did look at logs to see if there were any "UNMATCHED" log entries and nothing popped up. Thoughts? -- Stanislav Ochotnicky <sochotnicky(a)redhat.com> Software Engineer, PnT DevOps - Brno PGP: F434 2286 27DC 7D9B 2B64 0866 BCBD 752E 7B08 7241 Red Hat Inc. http://www.redhat.com

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

koji-devel August 2017