My situation is this: my build system is running Scientific Linux 4.4
(basically RHEL 4) with mock 0.6.12. It fails to build a particular RPM
when trying to compile a fortran file. The error issued is
mkscrlib.f:381: internal compiler error: Illegal instruction
When I set up mock 0.6.12 on my laptop running FC6 with all updates and
run the same script to build the RPM, it builds just fine.
The target distribution for the mock build is FC6.
SELinux is disabled on the SL 4.4 box.
When I run mock with '--debug', there is a lot of information, but I
have no idea what to look for or how to continue to troubleshoot this.
Can anyone offer any suggestions?
I'm trying to get plague set up and I'm running into compatibility
problems that lead me to think I'm starting in the wrong place.
I picked FC7 and sqlite to start with for plague's home OS and a
non-DB-server DB option. The production system will be RHEL4/5 once
I'm comfortable I know how to get things running smoothly. I tried
briefly with RHEL4 a few months back and didn't get this far.
I started with a fresh install of FC7 (incl. python-2.5,
python-sqlite2) and plague 0.4.4.1-4.fc7 RPMs. After running into
some of the first issues I switched to CVS MAIN with similar results.
Here's what I've done so far:
- import sqlite3 as sqlite
- remove encoding="utf-8" from sqlite.connect
- sqlite hack: move dbm connection into BuildMaster so
it can create one for each thread.
- set self._use_datetime = 0
- pass allow_none=False and encoding=None to
- change BaseConfig.BaseConfig.ConfigError to
I have the builder and server on the same host, w/o SSL yet. With the
0.4.4.1 RPMs and some of the changes above the server was able to talk
to the builder but I ran into the sqlite problem and switched to CVS
at that point.
CVS has the new Active/Passive builders but the default port configs
don't appear to be correct for having the builder and server on the
same machine, but I can't match up the config sections and field names
in the server and builder configs to point them at each other
correctly. At this point, the server's not seeing any builders. I
tried running 'plague-client list' anyway and get an exception "local
variable 'curs' referenced before assignment" which I'm pretty sure is
caused by my sqlite thread hack.
What OS+versions should I use to get plague up and running most
Once I'm up and running in a known-working environment I'd have a
better idea of what changes are right for FC7 or RHEL4/5.
A while I had the problem that caused Pungi/Anaconda to install a
custom RPM with a case-sensitivity problem, which caused me to finally
stop using Pungi to build my installation CD.
But, I think I now got a clue that could have caused that problem:
I found the following problem while I was using yum in a different situation:
Yum always uses the default config file in /etc/yum.conf, even if
there is another configuration file is specified on the commandline
with the -c option. It combines both repositiories, and mixes several
thinks up if there is more than repository with the same name.
I have not tested it in combination with pungi, I do not have that
build environment anymore that had this problem.
Do you know where I should post this bug?
-----BEGIN PGP SIGNED MESSAGE-----
Nice that the default is to build a minimal 1 CD but now that pungi
uses "Manifest" how does one go about building the entire media set
for FC6 on the latest version (0.2.4-1).
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.5
-----END PGP SIGNATURE-----
I hope someone can help me on this one. Probably I am doing something
wrong, but I cannot figure out what I do wrong:
I am building a customised CD based on FC6 RPMs+custom RPMs.
The problem I see is that the directory os/<prodname> contains all
RPMS including all dependencies, but the directory os-disc1/<prodname>
only contain a strange subset of the RPMs. I have 10 custom RPMs, but
the os-disc1 directory contains only 31, and I expect a total of 330
Notice that the entire RPM-collection in the os dir is about 340 MB,
which properly fits on 1 CD. After the build only 1 iso is created of
about 150 MB.
So, calculating dependencies based on my comps.xml works well, but
splitting the tree into CD's ignores a lot of RPMs.
Does anyone here has an idea of what I might have forgotten to
configure, or which error I make?
Note: even the glibc rpms are not there in the CD-image... Therefor
anaconda fails during installation (extraction phase of the RPMs), as
it cannot find some localisation files.
This is another small patch. What it does is breakup the pungi process
into different stages that can be invoked independently without going
thru all the stages. the stages are:
- Gather (-G)
- Buildinstall (-B)
- Package Order (-P)
- Splittree (-S)
- Iso Creation (-I)
If none of this switches is specified, then the default behaviour
continues (i.e, all are run one after the other), specifying *any* of
the flags will cause the stage to be run.
This split-up actually helps in scenarios when you change something, and
know what you should be doing next, but do not want to run the whole
process again. It also helps when debugging the process.
A little issue though is that, I wasn't sure which stage that
doGetRelnotes should fall under, so I put it under PackageOrdering
stage, so each time -P is run, GetRelnotes() will also be run.
I'm attaching a small patch here, that adds some new make targets to the
makefile. making it easier to modify the code and test.
Not sure if this is the right place to send it to, if its not, please
What's the idea behind the 'flavor' configuration keyword in pungi
(using lattest tip). On inspecition, It seems to be appended to the
version number and used to create directory paths. I guess I just want
to know the "why" behind it :), or more like, the domain equivalence...
basically... what the heck is a flavor :)
First off... pungi is looking fantastic so far!!!
I have a set of tools that do the same thing that pungi does... (i call
it fcdistroutils, and i've been using it since FC4). Lately, I've had
problem after problem with it, and when posting on the anaconda-devel
list, Jesse Keating suggested I look at pungi... and so far... sooo cool :)
I'm currently watching pungi run buildinstall, lets see if it works for
me first try (i really hope it does... it blows my fcdistroutils out of
Anyways, as I keep using it, I'll be sure to help out in anyway that I can.
A quick idea-type-suggestive-question-kinda anyone mulling over an
integrated system that combines pungi and pilgrim? (I just ran across
pilgrim last week too). I used to use fcdistro to build both my
Installation CD, LiveCD (based off of kadischi) and ThinClient Image(s)
(based off of kadischi). It would be nice to have a nice integrated
system that allows you to just edit config files, and generate either:
Complete dd-able thin-client image(s)
Oh.. and btw, pungi is already at: 'Creating Little endian 3.0
filesystem on /tmp/minstg2.img.11522, block size 65536.'
this may just work yet at first try :)
Thanks for the Good Work.