Are there plans for the upcoming Fedora 17 koji daemons (koji-builder,
kojira) to be build with systemd support?
Thanks. -A
--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
While following this guide:
http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testin…,
I've received an interesting error:
$ mock -r goose-sketchy-x86_64 --shell
INFO: mock.py version 1.1.18 starting...
State Changed: init plugins
INFO: selinux disabled
State Changed: start
State Changed: lock buildroot
State Changed: shell
<mock-chroot>[root@pilgrim /]# pungi -G -C -B --flavor=GoOSe
--ver=sketchy -c /root/pungi-x86_64.ks
Warning: Reusing existing destination directory.
Traceback (most recent call last):
File "/usr/bin/pungi", line 216, in <module>
main()
File "/usr/bin/pungi", line 86, in main
mypungi._inityum() # initialize the yum object for things that need it
File "/usr/lib/python2.6/site-packages/pypungi/__init__.py", line
166, in _inityum
del self.ayum.prerepoconf
AttributeError: prerepoconf
A couple things to note:
pungi was built by me from the latest that seemed to work with
something equivalent to CentOS6.0 on our koji server -
pungi-2.0.22-1.gl6.noarch.
Here are the mock and yum versions as well:
mock-1.1.18-1.el6.noarch
yum-3.2.29-22.el6.centos.noarch
I did have a look through the mock logs to no avail.
Any thoughts?
Anything else I can provide, please just let me know.
Thanks,
Clint
I've got a few patches lined up for Koji, and I'd love to see them get
reviewed and merged. I'm happy to answer any questions about them.
(Please also let me know if there is a more appropriate avenue to get
these reviewed and merged.)
https://fedorahosted.org/koji/ticket/224 Avoid pgdb's _quoteparams()
https://fedorahosted.org/koji/ticket/227 fix pkgorigins.gz file creation in F16
These two are necessary to make Koji work on Fedora 16.
https://fedorahosted.org/koji/ticket/225 better examples for Kerberos
auth options
This is essentially a doc fix, should be really simple.
https://fedorahosted.org/koji/ticket/229 make SCM URL validity check
more verbose
This is an attempt to make the errors more helpful when Koji can't
understand the user's SCM URL. As a Koji newbie it was difficult for
me to figure out the precise SCM string format that Koji expects;
these error messages helped me troubleshoot my way through the fog.
The next two are "bigger" logic changes.
https://fedorahosted.org/koji/ticket/226 Don't rewrite HTTPS URLs as HTTP
This is a tweak to Koji-web so that I don't get kicked back to an HTTP
URL when I click "logout".
https://fedorahosted.org/koji/ticket/230 add HTTP "proxy" option to builder
This is a feature that implements an HTTP proxy option for the
builders. It allows me to easily use my Squid box as a cache so I
don't have to hit a mirror over the internet each time. This mailing
list thread from 2008 was the inspiration:
https://lists.fedoraproject.org/pipermail/buildsys/2008-November/002271.html
- Ken
