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:
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.
Can pungi put packages/groups in the iso that are not installed?
Context: I'm building spin using pungi that includes packages that get
installed in a second pass in a manner similar to firstboot. The
packages require a number of services to be running to properly
configure themselves and can't be grouped in the initial install.
I want to include the packages in the repo, but not install them until
the system has more services running.
On Thu, 18 Dec 2008, Karsten Wade wrote:
> On Tue, Dec 16, 2008 at 11:45:19AM -0600, Dennis Gilmore wrote:
> > We do need to get out of the business of running two buildsystems. we really
> > do need to be able to build EPEL in koji. I have scheduled a koji hackfest
> > for fudcon. so if your there and interested then come help. there is always
> > #koji on freenode for discussion on koji, so if you cant make it in person
> > you can be there virtually :)
> Is there somewhere I can get an overview of the challenge and process
> of moving EPEL to koji? If not, can we take some time and write up
> such a thing?
I've been talking with some of the SuSE guys and we agree there's some
overlap or at least coordination between their buildsystem and ours. The
first obvious low hanging fruit is common macros. For those who wonder
"why would we help OpenSuSE?" the answer is common goals, and better user
The problem is time and coordination. So on a whim I thought I'd send
this email out. Do we have any contributors out there who are both
members of Fedora and SuSE who would be willing to lead this charge, find
similarities and places for coordination?
Are there any plans to bring 2.0 back into F9? I am working on an
appliance building tool which sits on top of pungi, appliance-creator,
EC2, and some other tools. I have it working on F10... but the API is
readically different then from F9.
i have rebuilt a fedora 9 distribution with pungi in Fedora 9. but it seems
that there is something wrong with the font in the anaconda graphic mode
while installing. no characters can be seen during installation except the
unknown "□". here is the error message below:
15:10:33 WARNING: step installtype does not exist
15:10:33 WARNING: step confirminstall does not exist
15:10:33 WARNING: setup complete does not exist
15:10:34 WARNING: /usr/lib/anaconda/gui.py:1460: PangoWarning: No fonts
This probably means that the fontconfig
library is not correctly configured. you may need to
edit the fonts.conf configuration files. More information about fontconfig
can be found in the fontconfig(3) manual
page and on http://fontconfig.org
15:10:34 WARNING: /usr/lib/anaconda/gui.py:1460: PangoWarning: failed to
shape engine, expect ugly output. enginetype="PangoRender", script='latin'
15:10:34 INFO : moving (1) to step welcome
and i have checked the stage2.img. it seems there is no /usr/share/fonts/
directory. i think it is something wrong with anaconda-runtime, but i don't
(refers to koji-1.2.6-1)
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
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
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