buildsys January 2007

buildsys@lists.fedoraproject.org

12 participants
15 discussions

pungi ignores a lot of RPMs when building CD image
by Remy Bohmer 18 Feb '07

18 Feb '07

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

3 16

pungi error
by Stephanos Manos 03 Feb '07

03 Feb '07

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

2 7

Mock "Could not find useradd in chroot, maybe the install failed?"
by Jeroen Janssen 31 Jan '07

31 Jan '07

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

2 2

Hi list
by "Guillermo Gómez S." 31 Jan '07

31 Jan '07

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

1 0

missing binaries during installation from CD built with pungi
by Remy Bohmer 29 Jan '07

29 Jan '07

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

2 1

using pungi for custom installations
by Remy Bohmer 26 Jan '07

26 Jan '07

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

3 5

openSUSE build service?
by Jeroen Janssen 24 Jan '07

24 Jan '07

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

1 0

via-rhine problems with FC6 respins containing 2.6.19 kernel?
by Jeroen Janssen 24 Jan '07

24 Jan '07

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

2 1

pungi & nrofdiscs?
by Jeroen Janssen 22 Jan '07

22 Jan '07

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

2 1

disc0 & pungi 0.1.2-2?
by Jeroen Janssen 20 Jan '07

20 Jan '07

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

2 1

pungi on ia64 machine
by Zhang, Yanmin 14 Jan '07

14 Jan '07

I used pungi on ia64 to try to build CD/DVD images for the FC development tree, and ran into a couple of issues. 1) I used the mirrors/fedora/linux/core/development/ia64/os/repodata/comps.xml. Got below error: /mnt/tmp2/soft/pungi-0.1.0/work/iso/FedoraCore-test/ia64/os/buildinstall.tree.1229 /mnt/tmp2/soft/pungi-0.1 .0/work rpm2cpio: /mnt/tmp2/soft/pungi-0.1.0/work/iso/FedoraCore-test/ia64/os/Fedora/anaconda-runtime-[0-9]*: No su ch file or directory cpio: premature end of archive /mnt/tmp2/soft/pungi-0.1.0/work So anaconda and anaconda-runtime were missed. I changed the comps.xml manually by adding anaconda and anaconda-runtime into base group. The issue disappeared. 2) Then, restarted pungi, but got below error: Wrote /mnt/tmp2/soft/pungi-0.1.0/work/iso/FedoraCore-test/ia64/os/images/stage2.img (94676k) Writing .discinfo file timestamp not specified; using the current time ** Message: sqlite cache needs updating, reading in metadata ** Message: sqlite cache needs updating, reading in metadata du: cannot access `/mnt/tmp2/soft/pungi-0.1.0/work/iso/FedoraCore-test/ia64/os-disc0': No such file or directory Traceback (most recent call last): File "/usr/bin/pungi", line 100, in ? main() File "/usr/bin/pungi", line 47, in main mypungi.doSplittree() File "/usr/lib/python2.4/site-packages/pypungi/pungi.py", line 54, 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 Yanmin

4 21

RFC: new mock: strategy, selinux, etc.
by Clark Williams 12 Jan '07

12 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, It's been some number of months (six+) since we decided to change the way mock works. We (Michael Brown and I, with input from skvidal and others) came up with a change in how mock launches, manages permissions and runs privileged commands. Old mock (mock-0.6 and previous) is a python script that does some sanity checking (insures that the person running mock is not root and is in the mock group) and then processes the input commands. Whenever it needed to do something that required root privileges, old mock ran a setuid root program named mock-helper. Mock-helper is a C program that knows how to do a limited number of things (mount/unmount, run chroot, etc.). The new mock (mock-0.7 and beyond) turns things around a bit. In new mock, the program /usr/bin/mock is a setuid:root, setgid:mock C program that does one thing only: launches the command "python /usr/libexec/mock.py <args>" in it's own kernel namespace. The mock.py logic still sanity checks that the user is in the mock group and drops privileges to the actual uid while keeping the gid of the process the mock group. As long as we're careful to maintain proper group ownership and permissions of created file and directories, this should go a long way toward fixing the issues we're having with multiple users on a single machine. New mock will no longer use mock-helper. When it needs to do something that requires root privileges, it will elevate it's privilege level to root (using os.setreuid()), execute the command and then drop privileges back to the normal user. All of this is working, although it has not been extensively testing (hello rawhide!). I've merged the BZ bugfixes from the mock-0.6 branch of CVS into the head (which is the new mock) and would like to push the new mock out to rawhide for testing. What I'm looking for from the readership of this list is: 1. Review of strategy and code for security issues 2. Help in formulating an SELinux plan/policy for mock We had some discussion on this issue back in June 2006, but I'd like to look at it one more time before inflicting the new mock on the rawhide faithful. With regard to SELinux, I'm not sure where we need to go with mock. I want mock to function properly and securely on a system running SELinux, but I'm just not sure how to go about that. I've looked at the steps mentioned on: http://fedoraproject.org/wiki/Extras/MockTricks But I'm too SELinux ignorant to be able to make an informed judgment on whether that's the right thing to do. Help on this would be greatly appreciated. Thanks, Clark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFnS0vHyuj/+TTEp0RAtmUAJ0X6axpPl9UNA8JeSYBeiT++OBtQwCg1/Vj 3NGUFzEmfw5b10NJq3LhxT0= =sIYO -----END PGP SIGNATURE-----

5 15

make tag weirdness
by Gianluca Sforna 09 Jan '07

09 Jan '07

Is it just me, or the "make tag" command behaved strangely in this case ? [giallu@hal9001 devel]$ make tag cvs tag -c mantis-1_0_6-2_fc7 ? clog ? mantis-1.0.6 ? mantis-1.0.6-1.fc7.src.rpm ? mantis-1.0.6-2.fc7.src.rpm cvs tag: mantis-httpd.conf is locally modified cvs [tag aborted]: correct the above errors first! make: *** [tag] Error 1 [giallu@hal9001 devel]$ mv mantis-httpd.conf mantis-httpd.conf.new [giallu@hal9001 devel]$ cvs update ? clog ? mantis-1.0.6 ? mantis-1.0.6-1.fc7.src.rpm ? mantis-1.0.6-2.fc7.src.rpm ? mantis-httpd.conf.new cvs update: Updating . cvs update: warning: mantis-httpd.conf was lost U mantis-httpd.conf [giallu@hal9001 devel]$ make tag build cvs tag -c mantis-1_0_6-2_fc7 ? clog ? mantis-1.0.6 ? mantis-1.0.6-1.fc7.src.rpm ? mantis-1.0.6-2.fc7.src.rpm ? mantis-httpd.conf.new ERROR: Tag mantis-1_0_6-2_fc7 has been already created. The following tags have been created so far mantis-1_0_0-0_1_a3_fc5:devel:ensc:1119711001 mantis-0_19_2-2_fc4:FC-4:ensc:1119711469 mantis-0_19_3-1_fc4:FC-4:ensc:1130434051 mantis-1_0_0-0_1_rc4_fc5:devel:ensc:1135352863 mantis-0_19_4-1_fc4:FC-4:ensc:1135352893 mantis-1_0_0-1_fc5:devel:ensc:1140260422 mantis-1_0_1-1_fc5:devel:ensc:1141846123 mantis-1_0_3-1_fc6:devel:ensc:1148279495 mantis-1_0_5-1_fc6:devel:giallu:1160481046 mantis-1_0_5-1_fc5:FC-5:giallu:1161039528 mantis-1_0_5-1_fc5:FC-5:giallu:1161039915 mantis-1_0_5-1_fc5_1:FC-5:giallu:1161076958 mantis-0_19_4-2_fc4:FC-4:giallu:1161388633 mantis-1_0_6-1_fc7:devel:giallu:1162505136 mantis-1_0_6-1_fc6:FC-6:giallu:1162506434 mantis-1_0_6-1_fc5:FC-5:giallu:1162506806 mantis-1_0_6-2_fc7:devel:giallu:1168344682 I mean, the tag is NOT there, since the pre tag check failed, but it seems that now "make tag" believes otherwise. What am I missing?

2 2

Failed to buildup new images on ia64
by Zhang, Yanmin 04 Jan '07

04 Jan '07

I installed Fedora Core 6 on my ia64 machine. Then, after getting the new rpms from the latest ia64 development tree, I tried to buildup new iso images by pungi. The buildup failed. Pls. see below log. The new development tree uses python 2.5, but my distribution on machine installs python 2.4. If I replace it with 2.5, lots of other tools will be erased. The iso buildup also needs python 2.5 and the latest anaconda and yum. In the other hand, it looks like only with the new iso image, I could install python 2.5. Is it a chicken-egg issue? Is there any walkaround to install the latest python 2.5/anaconda/yum? Yanmin *************************************************pungi log******************************* Downloading eclipse-pde-3.2.1-23.fc7.ia64.rpm Running buildinstall... /mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438 /mnt/tmp2/soft/work_pungi rpm2cpio: /mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/Fedora/anaconda-runtime-[0-9]*: No such file or directory cpio: premature end of archive /mnt/tmp2/soft/work_pungi cp: cannot stat `/mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/usr/lib/anaconda-runtime/./upd-instroot*': No such file or directory cp: cannot stat `/mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/usr/lib/anaconda-runtime/./mk-images*': No such file or directory cp: cannot stat `/mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/usr/lib/anaconda-runtime/./makestamp.py*': No such file or directory cp: cannot stat `/mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/usr/lib/anaconda-runtime/./buildinstall*': No such file or directory Building images... /usr/lib/anaconda-runtime/buildinstall: line 134: /mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/upd-instroot: No such file or directory Creating repository metadata... Making images... /usr/lib/anaconda-runtime/buildinstall: line 146: /mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/mk-images: No such file or directory Writing .discinfo file /usr/lib/anaconda-runtime/buildinstall: line 149: /mnt/tmp2/soft/work_pungi/pungi/7.01/ia64/os/buildinstall.tree.8438/makestamp.py: No such file or directory /mnt/tmp2/soft/work_pungi/pungi/work/ia64/docs /mnt/tmp2/soft/work_pungi 126 blocks /mnt/tmp2/soft/work_pungi /mnt/tmp2/soft/work_pungi/pungi/work/ia64/docs /mnt/tmp2/soft/work_pungi 4766 blocks /mnt/tmp2/soft/work_pungi Copying release note file RPM-GPG-KEY Copying release note file RPM-GPG-KEY-beta Copying release note file RPM-GPG-KEY-fedora Copying release note file RPM-GPG-KEY-fedora-extras Copying release note file RPM-GPG-KEY-fedora-legacy Copying release note file RPM-GPG-KEY-fedora-rawhide Copying release note file RPM-GPG-KEY-fedora-test Copying release note file RPM-GPG-KEY-rawhide Copying release note file GPL Copying release note file eula.txt Copying release note file README-BURNING-ISOS-en_US.txt Copying release note file RELEASE-NOTES-en_US.html Copying release note file fedora.css Copying release note dir stylesheet-images 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 393, in main self.createSplitDirs() File "/usr/lib/python2.4/site-packages/pypungi/splittree.py", line 236, in createSplitDirs self.createDiscInfo(i) File "/usr/lib/python2.4/site-packages/pypungi/splittree.py", line 141, in createDiscInfo raise RuntimeError, "CRITICAL ERROR : .discinfo doesn't exist in the unified tree, not splitting" RuntimeError: CRITICAL ERROR : .discinfo doesn't exist in the unified tree, not splitting

2 1

pungi issues
by Phil Meyer 02 Jan '07

02 Jan '07

First when building: ... Building images... Assembling package list... Expanding text packages... Expanding graphical packages... retrieving timezones ln: creating symbolic link `/tmp/treedir.29220/instimage/etc/joe/picorc' to `jpicorc': No such file or directory ln: creating symbolic link `/tmp/treedir.29220/instimage/etc/joe/jnanorc' to `jpicorc': No such file or directory ln: creating symbolic link `/tmp/treedir.29220/instimage/etc/joe/nanorc' to `jpicorc': No such file or directory ln: creating symbolic link `/tmp/treedir.29220/instimage/etc/joe/emacsrc' to `jmacsrc': No such file or directory ... I assume that this is harmless Then: ... mv: cannot stat `/tmp/treedir.29220/instimage/etc/man.config': No such file or directory cat: /tmp/treedir.29220/instimage/etc/man.config-old: No such file or directory Running mkfontdir... ... No big deal since I don't want man pages, nor did I specify them in the the comps.xml ... Scrubbing trees... /tmp/treedir.29220/instimage cp: cannot stat `/tmp/treedir.29220/instimage/boot/memtest*': No such file or directory mv: cannot stat `/tmp/treedir.29220/instimage/usr/sbin/busybox.anaconda': No such file or directory ... These might be an issue ... Found keymap override, using it unpacking /big/pungi/6.89/i386/os/Fedora/kernel-2.6.18-1.2868.fc6.i586.rpm.i586 Building initrd.img Wrote /tmp/makebootdisk.initrdimage.7258 (5796k compressed) Building isolinux directory 192000 pixels, 9629 bytes, (89.97% compression) Unknown file type (unallocated) /big/pungi/6.89/i386/os/images/isopath/.. - ignoring and continuing. mkdosfs 2.11 (12 Mar 2005) cannot find package kernel-xen in path /big/pungi/6.89/i386/os/Fedora No i586 kernel, trying i686... unpacking /big/pungi/6.89/i386/os/Fedora/kernel-xen-2.6.18-1.2868.fc6.i686.rpm.i686 Building i686 guest initrd.img Wrote /tmp/makebootdisk.initrdimage.7258 (5808k compressed) Building minstg.img ... Why is the i586 image here?? The result is ALWAYS: ERROR : failed to mount loop: Invalid argument ERROR : Error mounting /dev/loop0 on /mnt/runtime (Invalid Argument) This happens when using the stock /etc/pungi as shipped from extras, and any incarnation of comps.xml that I can put together. For reference: -> cat pungi.conf # Pungi config file # [default] product_name = Fedora Core product_path = Fedora iso_basename = FC comps = /etc/pungi/comps.xml yumconf = /etc/pungi/yum.conf.fc6.i386 destdir = /big/pungi cachedir = /big/pungi/cache arch = i386 version = 6.89 discs = 1 getsource = No -> cat comps.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE newcomps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd"> <comps> <group> <id>base</id> <name>Base</name> <description>This is the base group.</description> <default>true</default> <uservisible>true</uservisible> <packagelist> <packagereq type="optional">anaconda-runtime</packagereq> <packagereq type="mandatory">authconfig</packagereq> <packagereq type="optional">busybox</packagereq> <packagereq type="optional">dejavu-lgc-fonts</packagereq> <packagereq type="optional">gnome-python2-gtkhtml2</packagereq> <packagereq type="default">grub</packagereq> <packagereq type="optional">kernel</packagereq> <packagereq type="optional">libuser</packagereq> <packagereq type="optional">policycoreutils</packagereq> <packagereq type="optional">selinux-policy</packagereq> <packagereq type="optional">selinux-policy-targeted</packagereq> <packagereq type="optional">xorg-x11-drivers</packagereq> <packagereq type="optional">xorg-x11-fonts-base</packagereq> <packagereq type="optional">xorg-x11-fonts-ISO8859-1-75dpi</packagereq> <packagereq type="mandatory">yum</packagereq> <packagereq type="mandatory">postgresql</packagereq> <packagereq type="optional">postgresql-contrib</packagereq> <packagereq type="optional">postgresql-docs</packagereq> <packagereq type="optional">postgresql-jdbc</packagereq> <packagereq type="optional">postgresql-odbc</packagereq> <packagereq type="optional">postgresql-pl</packagereq> <packagereq type="default">postgresql-python</packagereq> <packagereq type="default">postgresql-server</packagereq> <packagereq type="optional">postgresql-tcl</packagereq> <packagereq type="optional">postgresql-test</packagereq> <packagereq type="default">crypto-utils</packagereq> <packagereq type="default">distcache</packagereq> <packagereq type="mandatory">httpd</packagereq> <packagereq type="default">httpd-manual</packagereq> <packagereq type="default">mod_auth_kerb</packagereq> <packagereq type="default">mod_auth_mysql</packagereq> <packagereq type="default">mod_auth_pgsql</packagereq> <packagereq type="default">mod_authz_ldap</packagereq> <packagereq type="default">mod_perl</packagereq> <packagereq type="default">mod_python</packagereq> <packagereq type="default">mod_ssl</packagereq> <packagereq type="default">php</packagereq> <packagereq type="default">php-ldap</packagereq> <packagereq type="default">php-mysql</packagereq> <packagereq type="default">php-odbc</packagereq> <packagereq type="default">php-pgsql</packagereq> <packagereq type="default">squid</packagereq> <packagereq type="default">tux</packagereq> <packagereq type="default">webalizer</packagereq> </packagelist> </group> </comps>

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys January 2007