So I've moved on RHEL 5. This is what installed on my system:
rpm-4.4.2-33.el5
yum-3.1.4
pungi-0.2.8
anaconda-11.1.2.16 (from centos)
Well first run of pungi ends with this message:
<===============================8=<
File "/usr/bin/pungi", line 17, in ?
import pypungi.pungi
File "/usr/lib/python2.4/site-packages/pypungi/pungi.py", line 20, in ?
import splittree
File "/usr/lib/anaconda-runtime/splittree.py", line 238
if (self.src_discs != 0):
^
TabError: inconsistent use of tabs and spaces in indentation
<+==============================8=<
Nice, very nice. In /usr/lib/anaconda-runtime/splittree.py on line 238,
392 and 465 tabs are used instead of plain spaces. Ok, simple 's,^\t,
,g' has fixed that problem.
Next stop is almost at the end:
<===============================8=<
File "/usr/bin/pungi", line 182, in ?
main()
File "/usr/bin/pungi", line 118, in main
mypungi.doSplittree()
File "/usr/lib/python2.4/site-packages/pypungi/pungi.py", line 209, in
doSplittree
output = timber.main()
File "/usr/lib/anaconda-runtime/splittree.py", line 391, in main
self.splitRPMS()
File "/usr/lib/anaconda-runtime/splittree.py", line 333, in splitRPMS
"%s-disc%d/%s/%s" % (self.dist_dir, disc, pkgdir, file_name))
OSError: [Errno 17] File exists
<===============================8=<
This is odd because I have cleaned up directory /srv/pungi.
Any ideas? May be this is because I've specified 1 as number of disks:
[default]
product_name = test
product_path = test
iso_basename = test
comps = /etc/pungi/comps-fc6.xml
yumconf = /etc/pungi/yum.conf.test.i386
destdir = /srv/pungi
cachedir = /srv/pungi/cache
arch = i386
version = 1
discs = 1
getsource = No
manifest = /etc/pungi/minimal-manifest
Ok this is splitRPMS step so `os' directory exists. So I've just
created iso image out of it. It boots, even checks disk but fails to
start anaconda with message:
exec of anaconda failed: No such file or directory
How come? I've explored image `stage2.img' from boot disk and have
found: /usr/bin/python, /usr/bin/python2.4 and /usr/bin/anaconda.
Most annoying thing is that during this stage shell is not available!!!
Any help here?
--
With Best Regards,
Anatoly Konukhov,