pungi ignores a lot of RPMs when building CD image
by Remy Bohmer
Hello all,
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
RPMs.
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.
Kind Regards,
Remy Bohmer
17 years, 1 month
pungi error
by Stephanos Manos
Hi
First sorry if posting in the wrong list.
Trying to respond to the QA call for test 1 i followed the instructions
posted to build using pungi inside mock (i am currently ruuning FC6)
using a locally mirrored repo.
When the building process finished with the ok message i did a sha1sum
check on the output with sha1sum -c SHA1SUM and all except the rescue
cd fail.
[root@ghost iso]# cat SHA1SUM
0cb6c915cd932fb3d096a15110d746b1267295e8 FD-6.90-i386-disc1.iso
e0c1b387eb0755726698e6da4e1a1bf5858fbd5a FD-6.90-i386-disc2.iso
2f2f18d366f62812746f9d779e7b4efa77c6fde6 FD-6.90-i386-disc3.iso
99d2733ed1ee1da6c0d78541b2672418d374fb63 FD-6.90-i386-DVD.iso
c2c4434fbf976f7a8f4673903d5e74ea9e79e040 FD-6.90-i386-rescuecd.iso
[root@ghost iso]# sha1sum *.iso
65e3ed52628e3f20cd0eb364f28e864f3afa445e FD-6.90-i386-disc1.iso
dbf3fa3f6cd09025ae89c45ed760bd77c21973d5 FD-6.90-i386-disc2.iso
87da6d5d6a20c1f10ad82b9702952f2240054657 FD-6.90-i386-disc3.iso
b66c7d8826aa52c1a3c5efab53c1f174cb230446 FD-6.90-i386-DVD.iso
c2c4434fbf976f7a8f4673903d5e74ea9e79e040 FD-6.90-i386-rescuecd.iso
inside mock
Executing /usr/sbin/mock-helper
chroot /var/lib/mock/fedora-development-i386-core/root /sbin/runuser -
root -c "cd /srv/pungi/f7-test1/6.90/Desktop/i386/iso ; /usr/bin/sha1sum
*.iso"
b66c7d8826aa52c1a3c5efab53c1f174cb230446 FD-6.90-i386-DVD.iso
65e3ed52628e3f20cd0eb364f28e864f3afa445e FD-6.90-i386-disc1.iso
dbf3fa3f6cd09025ae89c45ed760bd77c21973d5 FD-6.90-i386-disc2.iso
87da6d5d6a20c1f10ad82b9702952f2240054657 FD-6.90-i386-disc3.iso
c2c4434fbf976f7a8f4673903d5e74ea9e79e040 FD-6.90-i386-rescuecd.iso
regardless the error output when booting with the dvd disk and running
the media check option it passes.
due to time restrictions and missing a spare HD to install i haven't
tested more thoroughly
is it a known problem/regression of pungi or a problem on my side?
should i open a BZ ticket?
Stephanos Manos
17 years, 1 month
Mock "Could not find useradd in chroot, maybe the install failed?"
by Jeroen Janssen
Hi,
I have been trying to build F7Test1 for a couple of days now, but I
seem to be doing something wrong. Since I'm running a FC6 (latest
updates) system, I need to run pungi within mock in order to generate
the F7Test1 installation media.
However, I can't seem to get mock to work, so I cannot build the
installation media.
As a test, I'm running the following:
mock --debug -r fedora-6-i386-core init
and the latest part of the output is:
DEBUG: Executing /usr/sbin/mock-helper yum --installroot
/var/lib/mock/fedora-6-i386-core/root update
Could not find useradd in chroot, maybe the install failed?
ending
I get the same error when trying to setup a mock for fedora-devel.
This is with mock 0.6.10-1.fc6, with the default mock configfiles.
Anyone here having the same problem, or is it just me?
Best regards,
Jeroen Janssen
17 years, 1 month
Hi list
by "Guillermo Gómez S."
Hi, im new to this list and i would like to contribute with it.
Where should i start ?
kind regards
--
Gomix
Guillermo Gómez S.
cms fedora-ve http://www.fedora-ve.org
blog http://blog.gomix.org
soporte fedora-ve en irc.freenode.net, canal fedora-ve
lista email fedora-ve(a)googlegroups.com
Key fingerprint = 3143 8BDB 48A2 3241 E62A B743 D177 CAD7 3205 A464
17 years, 1 month
missing binaries during installation from CD built with pungi
by Remy Bohmer
Hello Jesse,
I have discovered a new problem with building a CD image with pungi. I
hope you have an idea what can be the cause:
* During installation and executing the pre-scripts, the binary called
'basename' lacks in the environment.(Notice that my scripts and
kickstart configuration work properly while doing a network
installation with default FC6 boot.iso and diskboot.img, while doing
network installations, basename is there...)
* During partitioning the installer cannot find the binary '/usr/sbin/mkfs.xfs'
* Somewhere during the build I got a message 'unable to stat busybox.anaconda'.
Are these problems related? And what could cause the lack of these binaries?
Any suggestions?
Thanks in advance...
Kind Regards,
Remy Bohmer
17 years, 1 month
using pungi for custom installations
by Remy Bohmer
Hello Jesse,
I am thankful for that you have built pungi, but while using it I ran into
the following questions. I hope you can answer them:
I am using pungi to be able to build a custom distribution based on FC6 for
an embedded target. Currently I have achieved to build a minimal CD-image of
about 400 MB by specifying a smaller comps.xml file. But the size is still
too big as there is a lot of unneeded stuff in it...
1. The generated ISO image contains xorg RPM packages which I do not need. I
want a text-only installation method (by using the serial console option of
Anaconda), as we do not have a VGA display on our target. Is there an easy
way to get rid of these xorg packages?
2. Currently only 1 ISO image is built with all packages in it. What I
actually want is that 2 ISO's are being built: the 1st ISO containing the
core installation (which almost never changes) with all boot and Anaconda
stuff on it, and a 2nd ISO containing the frequently changing
applications.(a predefined set of RPMs)
Is there a way to split up the list of RPM's in a predefined way (not
related to disc size) and that Anaconda during installation asks for the 2nd
disc?
3. Is there a easy way to get my own build kickstart file on the 1st ISO
through the pungi framework, without the need of rebuilding the ISO files
myself. (And to modify the isolinux configuration file to default load this
kickstart file?)
I hope you can help me by answering these questions...
Kind Regards,
Remy Bohmer
17 years, 1 month
openSUSE build service?
by Jeroen Janssen
Hi,
I just noticed the official release of the openSUSE build service (
http://lwn.net/Articles/218886/ ).
I haven't had a detailed look at it, but they provide both
client(worker) and server rpm packages for Fedora Core 6.
If I understand correctly, this means one can setup a FC6 based build
system for building RPM packages for FC6 (maybe one could build the
entire fedora core/extras repositories out of the box with this
system?).
I assume (but I do not have any detailed knowledge of this), that it's
possible to build FC6 based RPMs, without modifying the spec files for
this build service.
They seem to have some mechanism that allows for cross-distribution
RPMs, but I'm not sure if that is a requirement for being able to
build (I sure hope not, since that would make it less useable).
Is there any updated info on the brew/plague status?
Best regards,
Jeroen Janssen
17 years, 1 month
via-rhine problems with FC6 respins containing 2.6.19 kernel?
by Jeroen Janssen
Hi,
I was wondering if anyone has made a FC6 respin yet that contains the
2.6.19 kernel (the one that was recently released in FC6-updates).
I'm having some problems with networking on a via epia board, which
claims that the network on eth0 (using via-rhine) is down, but if I
boot from an original FC6 CD (containing the 2.6.18 kernel),
networking detection & dhcp works without any problems.
I'll try to rebuild the FC6 respin without the 2.6.19 kernel and see
if that solves my problem.
Best regards,
Jeroen Janssen
17 years, 1 month
pungi & nrofdiscs?
by Jeroen Janssen
Hi,
I just was wondering about the discs option in pungi.
Wouldn't it make more sense to just specify the size of disc(s)?
I mean, specifying the nr of discs implies that you know beforehand
the total discsize needed. What if I specify discs=5 and somehow the
needed discspace exceeds 5 discs?
If we just could specify the size of the discs, that means you
automaticly end up with the amount of CDs needed for everything you
want.
Anyway, this way if you want to generate a DVD you just specify
discsize to be of a DVD, or if you want multiple DVDs (think about
CORE + EXTRAS) that's also solved aswell then.
The only 'downside' is that you probably need multiple runs of pungi
if you want to generate both DVD and CDs.
Any other thoughts on this?
Best regards,
Jeroen Janssen
17 years, 2 months
disc0 & pungi 0.1.2-2?
by Jeroen Janssen
Hello,
Yesterday I installed a fresh FC6 machine, upgraded to the latest
software (incl pungi 0.1.2-2), mirrored Fedora Core 6, Updates and
Extras locally and performed a pungi run.
The result failed with the following messages:
du: cannot access `/files/pungi/srv/6.89/i386/os-disc0': No such file
or directory
Traceback (most recent call last):
File "/usr/bin/pungi", line 164, in ?
main()
File "/usr/bin/pungi", line 100, in main
mypungi.doSplittree()
File "/usr/lib/python2.4/site-packages/pypungi/pungi.py", line 108,
in doSplittree
output = timber.main()
File "/usr/lib/python2.4/site-packages/pypungi/splittree.py", line
394, in main
self.splitRPMS()
File "/usr/lib/python2.4/site-packages/pypungi/splittree.py", line
301, in splitRPMS
curused = self.getSize("%s-disc%s" % (self.dist_dir, disc), blocksize=1)
File "/usr/lib/python2.4/site-packages/pypungi/splittree.py", line
113, in getSize
thesize = long(string.split(thesize)[0])
IndexError: list index out of range
I'm on a i386 system building a i386 dvd.
I used all the pungi config files 'as-is' from /etc/pungi (pungi.conf,
yum.conf.i386, comps-fc6.xml). The only thing I changed was the
location of the repositories (which are local).
I thought this bug was already fixed in recent pungi.
Best regards,
Jeroen Janssen
17 years, 2 months