I'm tasked with building a custom kickstart ISO for Red Hat 5 update 2.
This is using
anaconda-11.1.2.113-1
anaconda-runtime-11.1.2.113-1
I've been successful for months, but today, ran into a weird symptom.
Our ISO boots, and installs our RPMs, but out of order, and does
not preserve the dependancies. (_Mostly_ does, but some critical
misses.)
During the creation of the ISO, I direct the build to:
- copy our RPMs into the approriate directory for mkisofs
- generate a test RPM database, and from that, generate a list of installed
packages
rpm --dbpath ${pkg_db_dir} -qa --queryformat='%{NAME}\n' >> all_packages.txt
- And I supply that text file in my ks.cfg file
%include /mnt/source/all_packages.txt
- I create the on-disk repo:
createrepo -p -q ${RPMBASE}
I observe:
- comparing the messages in /var/log/anaconda.log makes it seem
that the packages 'seen' by anaconda are in the right order. That
is to say, this command:
awk '/Adding/ {print $6}' /var/log/anaconda.log
yeilds a list that is in the same order as all_packages.txt from the ISO.
- but those lists are not the same order as anaconda installed:
awk '/Installing/ {print $2}' /root/install.log
Some of those are out-of-order, and breakage occurs. :/
Does anyone have any suggestions as to how to debug this?
I can provide logs (or snippets thereof), if that would help in the
diagnosis...
--
Brian Reichert <reichert@xxxxxxxxxxx>
55 Crystal Ave. #286 Daytime number: (603) 434-6842
Derry NH 03038-1725 USA BSD admin/developer at large
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
