koji-devel March 2017

koji-devel@lists.fedorahosted.org

8 participants
5 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

Code freeze for 1.12 release
by Mike McLean 30 Mar '17

30 Mar '17

We're very close to koji 1.12. We're targeting the middle of next week. I'm using this PR to cover final release details: https://pagure.io/koji/pull-request/361 We're in a code freeze until then to focus on testing. I'm only taking critical bug fixes or doc changes related to the release. If you're in a position to, now would be a great time to grab these bits and put them through their paces.

1 0

arm patches
by Dennis Gregorovic 20 Mar '17

20 Mar '17

https://bugzilla.redhat.com/show_bug.cgi?id=1420520#c11 Do we know if the patches needed here will be in the next upstream release?

2 1

request for feedback: systemd and logfiles
by Mike McLean 20 Mar '17

20 Mar '17

I was cleaning up my unmerged branches and found an addendum to the systemd support from a couple years ago. https://pagure.io/fork/mikem/koji/commits/systemd-redundant-logfiles This change: - ensures that kojid, kojivmd, and kojira have explicit --logfile options - allows this option to be specified as 'none' - adds --logfile=none to their respective systemd ExecStart commands The reason is that when systemd is in use, we're currently double logging, both in the traditional log files (e.g. kojid.log) and in the systemd journal (e.g. see journalctl -u kojid). The thing is, I'm curious how folks feel about this. Is it a good idea, or will it be to confusing for the original log files to be absent? I suppose another option to avoid double logging would be to keep the log files and turn of the logging in systemd (or at least most of it). I suppose it could also be made more configurable.

4 3

heads up: PR for mock chroot inside a chroot
by Dennis Gregorovic 02 Mar '17

02 Mar '17

https://github.com/rpm-software-management/mock/pull/51 This is something that could impact koji if there is a need to support this feature. It's worth checking out. -- Dennis

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

koji-devel March 2017