Previously if you wanted to use an HTTP proxy server with a builder, you
had to either specify the proxy in the pkgurl, or use iptables to
intercept HTTP and route it through a transparent proxy.
There is a better way: yum has proxy support built in. When a URL is
specified in the "proxy" option in yum.conf, yum will use this URL as a
proxy server.
Add a "yum_proxy" option in kojid.conf. Kojid will pass it back to mock
during genMockConfig(). Mock will write it into yum.conf in the chroot.
After the koji.conf 'pkgurl' attribute was enabled (sigul wants this;
I'll submit a patch for that too, later), one of my scripts broke
because the "Warning: the pkgurl option is obsolete" message is printed
to stdout instead of stderr. Here's a little patch to print the warning
with the warn() function instead.
I realize some warnings from the cli might be best printed to stdout,
but for ones that might appear when using a computer-readable type of
command like 'list-* --quiet', stderr seems like the better choice.
Thanks-
John
- mod_python still supported, but deprecated
- mod_wsgi is the default
- koji-web now configured via web.conf
- new wsgi-friendly publisher for koji-web
- koji-web now has logging
When a builder parses an SCM URL, the daemon module's _parse_url() does
a sanity check that it has properly understood all the necessary
elements of the URL string before returning them. When this check fails,
a "Invalid URL" message is raised, but this error message does not
provide information about what portion of the URL was missing.
Break this sanity check into multiple statements, so that we present a
more detailed error message to the user.