Mock/pungi error - stumped!
mike.cloaked at gmail.com
Fri May 27 10:48:07 UTC 2011
On Mon, May 23, 2011 at 3:37 PM, James Laska <jlaska at redhat.com> wrote:
>> However I have a problem with the build that I can't resolve.
>> The machine running the build is f13 up to date, and the command I use
>> to run pungi is as follows:
>> pungi --nosource --nodebuginfo -G -C -B -I --flavor Fedora --name
>> Fedora-15 -c /usr/share/spin-kickstarts/fedora-install-f15-mc.ks
>> However the build proceeds to the point in the logfile with the last
>> few entries:
>> pylorax.yumhelper.DEBUG: removed
>> pylorax.DEBUG: fedora-15-logos ['/etc/*', '/usr/share/firstboot/*',
>> '/usr/share/gnome-screensaver/*', '/usr/share/icons/Bluecurve/*',
>> '/usr/share/icons/oxygen/*', '/usr/share/pixmaps/*',
>> pylorax.yumhelper.ERROR: cannot erase fedora-15-logos: Package not installed
>> pylorax.INFO: cleaning up python files
>> pylorax.INFO: creating the initrd
>> pylorax.images.INFO: creating required directories
>> pylorax.images.INFO: copying kernel image
>> pylorax.images.INFO: compressing the install tree
>> It seems to hang for up to 12 hours at the final compression (before I
> Hmm, no idea off-hand. You probably already did this, but double check
> the versions of pungi and lorax being used inside the chroot. They have
> changed recently, so make sure you are using the latest versions of
> each. Are you able to upload your mock root.log for review?
> I've also cc'd Martin Gracik who maintains lorax to see if he has any
> debugging tips.
Thank you for all the help (including off-list) with the key
suggestion that the build machine needs to have more than 1GiB RAM to
run the new xz compression for iso production (in lorax) - after
receiving a 1GiB RAM extension giving a total RAM of 1.5 GiB, and
starting with a clean mock chroot in my build machine running F14, a
new build of F15 today proceeded without error and produced good
Thank you for all the help. I am running gold builds again now.
More information about the test