With newest yum and yum-metadata-parser I got the following traceback
when starting livecd-creator:
> DeprecationWarning: Script does not end with %end. This syntax has
> been deprecated. It may be removed from future releases, which will
> result in a fatal error from kickstart. Please modify your kickstart
> file to use this updated syntax. warnings.warn(_("%s does not end
> with %%end. This syntax has been deprecated. It may be removed from
> future releases, which will result in a fatal error from kickstart.
> Please modify your kickstart file to use this updated syntax.") %
> _("Script"), DeprecationWarning) mke2fs 1.40.2 (12-Jul-2007)
> Filesystem label=F8-KDE-17 OS type: Linux Block size=4096 (log=2)
> Fragment size=4096 (log=2) 524288 inodes, 1048576 blocks 10485 blocks
> (1.00%) reserved for the super user First data block=0 Maximum
> filesystem blocks=1073741824 32 block groups 32768 blocks per group,
> 32768 fragments per group 16384 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736
> Writing inode tables: done
> Creating journal (32768 blocks): done
> Writing superblocks and filesystem accounting information: done
> This filesystem will be automatically checked every 28 mounts or
> 180 days, whichever comes first. Use tune2fs -c or -i to override.
> tune2fs 1.40.2 (12-Jul-2007)
> Setting maximal mount count to -1
> Setting interval between checks to 0 seconds
> No Repositories Available to Set Up
> No Repositories Available to Set Up
> No such package *debuginfo to remove
> Traceback (most recent call last):
> File "/usr/bin/livecd-creator", line 1383, in <module>
> File "/usr/bin/livecd-creator", line 1361, in main
> File "/usr/bin/livecd-creator", line 858, in install
> File "/usr/bin/livecd-creator", line 550, in installPackages
> File "/usr/bin/livecd-creator", line 295, in runInstall
> (res, resmsg) = self.buildTransaction()
> File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 557,
> in buildTransaction (rescode, restring) = self.resolveDeps()
> File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 701,
> in resolveDeps CheckDeps, checkremoves, checkinstalls, missing =
> self._resolveRequires(errors) File
> "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 781, in
> _resolveRequires (checkdep, missing, errormsgs) =
> self._processReq(po, dep) File
> "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 250, in
> _processReq CheckDeps, missingdep =
> self._requiringFromTransaction(po, requirement, errormsgs) File
> "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 496, in
> _requiringFromTransaction reqpkg = self.rpmdb.searchNevra(name=name,
> ver=version, rel=release) IndexError: list index out of range
The latest rawhide version I got here locally is yum-3.2.2-3.fc8 and
yum-metadata-parser-1.1.0-2.fc7. With them all is working fine.
Is this a problem with livecd-tools? If so I will file a bug against it.
# make sure debuginfo doesn't end up on the live image
In accordance to /etc/yum.repos.d/fedora-development.repo
name=Fedora - Development - Debug
could be omitted.
is it @games required on the livecd-fedora-base-desktop ?
shouldn't it rather be in the livecd-fedora-kde-desktop.ks or
I just noticed that there is apparently a /etc/statetab which allows
you to specify directory paths to load from other sources upon bootup.
So, on a liveCD,mounting /etc or mounting /var on another partition,
especially on USB keys would work pretty handily.
What am I missing?
As proposed on the -devel mailing list, I've started to work on a
livecd for "Fedora Electronic Lab". Hopefully, Jeremy's support still
with livecd-creator, I created a livecd with a kickstart file based on
The kickstart file for FEL is
I had a livecd of 741.6MB which I'll strip later on to less that 700Mb.
However, each time I created a livecd with this process:
on booting the livecd it fails on:
Unable to load SELinux Policy. Machines is in enforcing mode. Halting now.
The diff of /usr/share/livecd-tools/livedvd-fedora-kde.ks and
I'm booting on vmware server and my mirrors:
fedora7 and updates7 are a rsync of the official mirrors, but the
repodata was created with :
createrepo comps/comps-f8.xml.in to ensure groups are considered.
What could be missing or done wrong in this process ?
The 3rd pass at my overlay/persistence patch for livecd-tools, isn't
really bigger than the 2nd, but it is fairly big, and definitely not the
So if you want it, or any further updates if and as they become
Summary of changes from the last version -
- much better remount read-only teardown of overlayfs
- findoverlay script debugging cleaned up, and obeys 'quiet' kernel arg
- live script will technically work for initialization of an overlay
image file, but it is still pretty much a placeholder
- more organized, and revised todo/notes in findoverlay script.
- very ugly (but maybe a bit less than before) mechanism for patching
the halt and functions scripts to support clean shutdown. I'm _very_
open to suggestions for better ways to do it, than the
currently. Also note that to get that done I had to put the same ugly
temporary hack in 3 different config files. Maybe it is time to take
care of the TODO that suggests getting fedora-live out of the kickstart
and into a package.
Of particular note, is that at this point in time, I'm getting a bit
wary as to whether or not, short of 'fixing' problems that are probably
beyond my abilities and/or desires, that this entire devicemapper
snapshot mechanism, using overlay image files on disk, may be fatally
flawed. See notes at end of findoverlay script for exact ext3
corruption error messages, and my random musings on the subject.
I think it may well be that a vastly simpler implementation using only
raw partitions, such as Ashok's might actually work better. At least
for the short term, until I can figure out the problems I'm seeing. Or
perhaps even an implementation with unionfs/funionfs.
I would _really_ like to see my method work, but there are also other
unrelated lower hanging fruit of interest to me that I think I might
rather be working on.
That said, my code is there, and I'll be more than happy to answer
questions or brainstorm about it if anybody inquires. And maybe some
idea will hit me or someone else soon, and I'll actually be able to make
it work robustly. Or really, I may have just run into one bad failure
case that isn't even reproducable, and further testing will show that it
works pretty well.
I would like to customize the kickstart file that anaconda uses during
a liveinst install of my liveCD.
The kickstart file that is used for the install, is not the same
kickstart file that was used to create the LiveCD.
A cursory inspection of anaconda doesn't yield any clues about how
that kickstart is created, or where it comes from.
"Whereever you go, there you are"
Attached is a patch.
It could be broken into two patches for clarity. Please review and apply if
patch#1: add --container-size flag
Using this flag, one can cause the os.img that sits in the squashfs.img, to be a
larger sparse file than the filesystem contained in it. By default, the old
behavior happens. One somewhat unrealistic, but real justification for this,
would be booting a livecd on a system with 16G of ram. Without this flag, you
would be limited to only writing 2G of data (given the existing f7-livecd-i686
choice of a 4G uncompressed-size, and about 2.1G of data). With this flag and a
container of say 1T or 100G, there would be no negative consequences, but the
livecd user would be able to online resize2fs their root filesystem upward if
The more realistic usefulness comes if through a persistence implementation, the
overlay file is not a 512M file stored in tmpfs, but an 8G file stored on an
ipod. Everything mentioned above applies.
patch#2: add --cleanup-deleted flag
Using this flag, about 25% is added to the build time, but any files that were
created and deleted in the install_root during installation, will not result in
wasted space on the resulting iso. This happens because of the nature of the
filesystem living on a sparse file. Anecdotally, this could be used to respin
the fedora7-livecd-i686, from its existing 700MB, to 664MB. Or more likely, add
another 100MB or so of uncompressed software onto it.
This is of even greater importance as people spin their own livecds, and do
intensive things during the installation, that might cause even more wasted space.
Also, this somewhat lays the foundation for a 'turboinstaller' that improves
current liveinst efficiency by 10-25% (for cdrom vs usbflash respectively), as
mentioned in bug 248082 (pending efficiency tests with extra device mapper layers)
Please review. Any comments, suggestions, or criticisms are welcome. I still
consider myself a relative novice when it comes to python.
(This is for the new changes to livecd-creator from git which uses two
Is there a way to remove a group which is defined in the first config (here
livecd-config-base-desktop.ks) in the second config (here
My problem is that the language groups (e.g. @estonian-support) pulls also the
kde language files (kde-i18n-Estonian) and koffice language files
(koffice-langpack-et) in the livecd. And I am not able to remove them in the
second config (e.g. -kde-18n-* or -kde-i18n-et).
Any hint how to fix this? The language files are about 325 megs and that's to
big for the cd.