Supporting EPEL Builds in Koji
by Mike Bonnet
Hi. I've written up a proposal for a way to support EPEL builds in
Koji. It's not the only way we could do this, but I think it's doable
with a reasonable amount of effort, and has the side-effect of greatly
simplifying the Koji setup process for a lot of people (by removing the
need to bootstrap/import an entire distro of packages into your private
Koji instance). You can view the proposal here:
http://fedoraproject.org/wiki/Koji/EPELSupport
It's fairly detailed regarding the data model changes necessary, so if
you're not familiar with the Koji codebase you can skip those parts.
Questions and comments welcome.
Thanks,
Mike
14 years, 4 months
Cockroach task
by Bryce
(refers to koji-1.2.6-1)
-scratch head-
Koji seems to have derailed itself and created an unkillable task
Although it has built the rpms, it then seems to have done something odd
to itself because it's entered a failed state but the koji system still
believes that it is still building the package
State failed
...
Result RetryError: unable to retry call 7 (method
host.importChangelog) for session 18591
I've tried koji cancel, and a few of the less savory koji call api
commands but it refuses to accept that the task is dead
Ideas?
I assume that for some reason it's been unable to communicate with the
postgres database but I don't see a means to tell it to retry or just
plain abandon the whole task
Phil
=--=
14 years, 6 months
Re: confused about the relationship between koji and pungi (Ignacio Vazquez-Abrams)
by Chen Baozi
>> hello,
>> i'm a novice for system building and have read some articles about
>> pungi and koji recently. but i'm a little confused about the
>> relationship between the tools. in my opinion, pungi is focusing on
>> building iso while koji is focusing on building packages. and i'm
>> wondering if the koji has got some similar functions as pungi does,
>> or is it simply that we use koji to build packages and
>> then make tree/iso by pungi?
> The link that you're looking for is mash.
Thank you.
So, what do they actually work for?
Or in other way, what workflow should we follow when building the distro
with koji and pungi?
14 years, 6 months
confused about the relationship between koji and pungi
by Chen Baozi
hello,
i'm a novice for system building and have read some articles about pungi and
koji recently. but i'm a little confused about the relationship between the
tools. in my opinion, pungi is focusing on building iso while koji is
focusing on building packages. and i'm wondering if the koji has got some
similar functions as pungi does, or is it simply that we use koji to
build packages and then make tree/iso by pungi?
14 years, 6 months
[PATCH/mock] Don't disable ccache on epel-5, it is available
by Todd Zullinger
Signed-off-by: Todd Zullinger <tmz(a)pobox.com>
---
I've wondered why ccache is disabled in the epel-5 mock configs. The
ccache package is available in epel 5 now, so it seems reasonable to
leave it enabled. Unless I'm missing something obvious, that is. ;)
etc/mock/epel-5-i386.cfg | 3 ---
etc/mock/epel-5-ppc.cfg | 3 ---
etc/mock/epel-5-x86_64.cfg | 3 ---
3 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/etc/mock/epel-5-i386.cfg b/etc/mock/epel-5-i386.cfg
index 30c66ee..9b9b6ef 100644
--- a/etc/mock/epel-5-i386.cfg
+++ b/etc/mock/epel-5-i386.cfg
@@ -3,9 +3,6 @@ config_opts['target_arch'] = 'i386'
config_opts['chroot_setup_cmd'] = 'install buildsys-build'
config_opts['dist'] = 'el5' # only useful for --resultdir variable subst
-# ccache not available on epel5
-config_opts['plugin_conf']['ccache_enable'] = False
-
config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
diff --git a/etc/mock/epel-5-ppc.cfg b/etc/mock/epel-5-ppc.cfg
index b07d136..1bd72a7 100644
--- a/etc/mock/epel-5-ppc.cfg
+++ b/etc/mock/epel-5-ppc.cfg
@@ -3,9 +3,6 @@ config_opts['target_arch'] = 'ppc'
config_opts['chroot_setup_cmd'] = 'install buildsys-build'
config_opts['dist'] = 'el5' # only useful for --resultdir variable subst
-# ccache not available on epel5
-config_opts['plugin_conf']['ccache_enable'] = False
-
config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
diff --git a/etc/mock/epel-5-x86_64.cfg b/etc/mock/epel-5-x86_64.cfg
index d0a8cde..0fe89d4 100644
--- a/etc/mock/epel-5-x86_64.cfg
+++ b/etc/mock/epel-5-x86_64.cfg
@@ -3,9 +3,6 @@ config_opts['target_arch'] = 'x86_64'
config_opts['chroot_setup_cmd'] = 'install buildsys-build'
config_opts['dist'] = 'el5' # only useful for --resultdir variable subst
-# ccache not available on epel5
-config_opts['plugin_conf']['ccache_enable'] = False
-
config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
--
1.6.0.4
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lazlo's Chinese Relativity Axiom:
No matter how great your triumphs or how tragic your defeats --
approximately one billion Chinese couldn't care less.
14 years, 6 months
F10 KS file not in latest Pungi.
by William F. Acker WB2FLW +1 303 722 7209
Hi all,
Now that Cambridge has gone gold, it seems that I shouldn't be using
the rawhide KS file. pungi-2.0.8-1.fc10.noarch has a file for Rawhide and
F9, but not F10.
TIA.
--
Bill in Denver
14 years, 6 months
Trying to figure out some umask issues
by Jason L Tibbitts III
I do a large number of local mock builds as a part of the package
reviews that I do, and one problem I consistently run into is
executables and .so files coming out with mode 775, but a scratch
build in Fedora's koji instance showing the expected 755 permissions.
I thought it might be some local environment leaking into my mock
builds, but my personal umask is 022 which should be OK and changing
it doesn't alter the result anyway.
Init'ing a fresh chroot shows the default umask in it is 0002, which
would seem to explain things but wouldn't explain why the Fedora
buildsys has different results. Is there customization done there to
force the umask somehow?
- J<
14 years, 6 months
Minor bug in pungi
by "Ang Way Chuang <洪伟壮>"
Hi all,
The error message refers to wrong variable. Attached is the patch
against the latest code from git.
14 years, 6 months
new koji instance: where is the Makefile.common ?
by Frederic Beuserie
Hi,
just set up a new koji instance for our internal buildsystem (until
now, we were using mdvsys/mock/createrepo and some control scripts).
i've noticed the use of a Makefile.common in various documentation
(http://fedoraproject.org/wiki/PackageMaintainers/UsingKoji,
"Building with make targets")
i would like to have a look on that. is there any url available ? i've
looked at fedora-packager on fedorahosted but the file is not there.
another question:
i'm using right now a subversion instance for storing all the packages
stuff (all sources rpms, sources files (specs, ...) and binary rpms).
the layout it the
one used by MDVSYS perl module.
since i've quite a lot of data in this subversion repo, is there any
chance to reuse the old layout with Koji ? is koji capable of working
with various SCM layout ?
thanks.
frederic beuserie
14 years, 6 months
