pungi used to create CD that includes a kickstart file
by Martin Steinmann
This was discussed on this list before back in June and in relation to
pungi 0.3.7 by Joel Andres Granados and others.
Using pungi I would like to create a CD that includes a kickstart file
(ks.cfg) to be used during installation of a system using this CD.
Is there a way to tell pungi to put a ks.cfg file into the root of the
CD? I am using pungi-1.1.5-1.fc8 on F8-test3.
What is the best way to modify the files in the isolinux directory?
I.e. the file isolinux.cfg needs to be modified to use the ks.cfg file
during boot. Should I create an RPM that overwrites these files already
installed by the anaconda-runtime package or is there a more elegant
way?
Without such a capability to add / modify key files pungi can only
really be used to respin distributions, but not create installation CDs
used for automated install or appliances. Is this maybe not the
intention with this tool?
--martin
15 years, 5 months
pungi problem
by Sergio Monteiro Basto
pungi are chipping 2 kdepim without any apparent reason
can someone explain why ?
thanks
INFO:yum.verbose.pungi:Checking deps of kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkcal_groupwise.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkcal_groupwise.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkpilot.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkpilot.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkcal_resourceremote.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkcal_resourceremote.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkabc_slox.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkabc_slox.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkgantt.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkgantt.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkode.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkode.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libknotes_xmlrpc.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libknotes_xmlrpc.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkitchensync.so.0
15 years, 5 months
Documentation for setting up koji?
by Tom Diehl
Hi,
I am trying to setup koji and friends but documentation for the packages seems
sparse at best. The only document I can find is at
http://fedoraproject.org/wiki/Koji/ServerHowTo and it has several holes in it
not to mention the note at the top that says "DRAFT/BETA/OH YEAH... DON'T USE"
So far the biggest issue I am having is how do I disable kerberos support?
I am sure there are others but that is what is stopping me presently.
I commented out the kerberos stuff in /etc/kojira/kojira.conf and that seems
to turn it off for kojira but I cannot find a corresponding config file for
kojid.
Suggestions??
Regards,
--
Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com
15 years, 5 months
mock improvements
by Michael E Brown
So here is the list of things that have been requested lately and I'll
be working on a few of these over the next few weeks. If anybody has any
input, I'd take it. As I start on each, I'll most likely email the
mailing list with the outline of what I'm doing.
If anybody has existing patches for these (against current mock git),
all the better... :)
1) more reliable mount/umount
several people have pointed out instances where mock exits leaving
mounts behind (specifically /dev), and the next invokation of mock
ends up 'rm -rf' the host machine's /dev. Bad....
2) caching yum downloads
several people have commented that the autocache stuff is great for
speeding up builds, others say that it can sometimes be bad for
reproducability, and that simply saving the yum cache dir would be
better.
3) ccache integration
This is a new one that I havent seen before, but should significantly
speed up builds for people who often do
rebuild-the-entire-distribution-type things. I'm told by some that
this is bad for reproducability, but good for speeding up builds when
you are just sanity checking or when that small reproducability hit
doesnt matter. I've also seen lots of empirical data that ccache
should not cause any problems. This will be have to be specifically
enabled through a commandline or config file option, so those who care
can turn it on/off.
4) distcc integration
Pretty much the same case as ccache. Has more things that need thought
than the ccache case, above, though.
--
Michael
15 years, 6 months
Patch for BZ 303791?
by Clark Williams
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Below is a patch for the $SUBJECT bz. I originally just changed the case of the
search string to match what 'yum resolvedep' was printing, but then I thought about
whether folks might not have the changed version of yum...
After I took an aspirin to deal with the dependency combinatorial explosion headache,
I looked at the code again. I didn't really want to pull in the re package just for
this one case, so I resorted to doing a case-insensitive match, which I *hope* will
deal with most cases.
What do you guys think?
Clark
diff --git a/mock.py b/mock.py
index 54b8f8c..35c3592 100644
- --- a/mock.py
+++ b/mock.py
@@ -355,9 +355,11 @@ class Root:
# pass build reqs (as strings) to installer
if arg_string != "":
(retval, output) = self.yum('resolvedep %s' % arg_string)
+ searchstr = 'no package found for'
for line in output.split('\n'):
- - if line.find('No Package found for') != -1:
- - errorpkg = line.replace('No Package found for', '')
+ idx = line.lower().find(searchstr)
+ if idx != -1:
+ errorpkg = line[idx+len(searchstr):]
error(output)
raise BuildError, "Cannot find build req %s. Exiting." % errorpkg
# nothing made us exit, so we continue
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD4DBQFHBSWXHyuj/+TTEp0RAtzCAJYy31hDn5zsGedHFM/LcWnrBbR5AKDnO10u
ou94vu8Kf369iaF/VKiE7w==
=iG5Y
-----END PGP SIGNATURE-----
15 years, 6 months