Some newer subvariants / loadouts, and 'Rawhide' for some
reason, were missing from the substitution list. This updates
it, alphabetizes it, adjusts the indentation to match how it
is in pungi-fedora for ease of comparison, and also tweaks the
way the list is applied to match
https://pagure.io/pungi/pull-request/857 , the correct way to
ensure longer substitutions are applied before shorter ones.
Note 'Alpha' and 'TC' are removed because we don't do Alphas or
TCs any more.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Koji now uses ssl via python-requests
- use_old_ssl option is removed
- koji.ssl library removed
- compatrequests dropped
Related: https://pagure.io/koji/issue/467
While the current code will always provide it, the older code did
not. When a Koji system is updated to this version, we could have
a restarted build task read the result of a previously finished
buildSRPMFromSCM task that ran with the old code.
Git HEAD commit hash is now stored in build.info field. this field is
currently used by content generators, but not by other builds. Also
original checked out url is stored in build.extra.url field.
Fixes: https://pagure.io/koji/issue/550
The semantics of "relative" here are atypical of common expectations.
While the method does return a "related" path, it's still absolute.
Hopefully this new name is less confusing.
This adds two new options (--lorax_url and --lorax_dir) to the Koji CLI
so that it's now possible to use custom lorax templates for livemedia
tasks. The custom templates must come from a supported, allowed SCM,
which makes it trivial to inject the whole directory structure of
template files that lorax expects.
In addition to the CLI changes, kojid's LiveMediaTask handler recognizes
these new options and acts accordingly by extending the
livemedia-creator call via its --lorax-templates option.
This patch only enabled xz threads -T0, and maximum compresion -9.
This patch removed the -f (--force) in previous patch.
Koji PR #380
Signed-off-by: jdisnard <jdisnard@redhat.com>
kojid in koji 1.12.0 fails to start when not using ssl cert auth
Traceback (most recent call last):
File "/usr/sbin/kojid", line 5627, in <module>
if os.path.isfile(options.cert):
File "/usr/lib64/python2.7/genericpath.py", line 37, in isfile
st = os.stat(path)
TypeError: coercing to Unicode: need string or buffer, NoneType found
if you do not have a cert option defined we should move on. so add
to the if statement a check that the option is actually defined
Signed-off-by: Dennis Gilmore <dennis@ausil.us>