Re: ordering not found for x.rpm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 26 Jan 2004, Taylor, ForrestX wrote:

> On Mon, 2004-01-26 at 13:19, Andy Rabagliati wrote:
> > Folks,
> > 
> >   what causes this ?
> > 
> > WARNING: ordering not found for dbh-1.0.15-2rh9.i386.rpm
> > 
> >   Even if I list packages that depend on this as default in my comps.xml, 
> >   I see this message.
> 
> IIRC, you need to run `genhdlist --withnumbers ...`, and possibly
> pkgorder and buildinstall.

Forrest, others,

My build process is as follows. (If people wish to use the Makefile, be
aware that Tabs are needed before the action lines. You could just string
together the action lines in a shell script too.)

./getfullcomps.py is the Fedora'fied version of the distributed getfullcomps.py,
per your previous suggestion. I ignore some unfulfilled dependencies at
this step - for instance dbh (as above) says it needs gcc. Maybe that is
the hangup ? If I were to add gcc, a lot of other baggage, devel- related,
would also be needed.

dbh is a part of a host of RPMs needed for xfce4 - the other
'WARNING: ordering not found' RPMs are almost all xfce4. It is a
lightweight WM I use for this LTSP install.

pkgorder is run at step3.

I think I can use the original Fedora install environment, and thus I
skip the somewhat expensive (and I find - error-prone) buildinstall step
(which would be in step3). I took Chris Rouch's suggestion in a previous
post to skip this step, and have not looked back .. (his post appended)

I get the errors for just a few RPMs at step5 - a dozen out of 600-odd.
root privs are only needed at the last step - "make disk".

It generates about 1.5 CDs.

They work nicely (via NFS), thanks, despite ' WARNING: ordering not found'.

Thanks for your attention.

Cheers,   Andy!

# Makefile for CDs #####################################################

# initial genhdlist
step1:
	/usr/lib/anaconda-runtime/genhdlist --productpath=Fedora /export/i386

# my comps file, check for errors
step2:
	cp comps-wizzy.xml /export/i386/Fedora/base/comps.xml
	./getfullcomps.py comps.xml /export i386 >/dev/null

# buildinstall should do this step, but it needs the BOOT kernel and takes too long ..
#./buildinstall  --comp comps --pkgorder /export/pkgorder.txt  --version 9.0  --release "Wizzy" --product Wizzy --prodpath Fedora /export/i386
#find /export/i386/images -name TRANS.TBL | xargs rm

step3:
	PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder /export/i386 i386 Fedora > /export/pkgorder.txt

step4:
	rm -rf /export/i386-disc?
	/usr/lib/anaconda-runtime/splittree.py --pkgorderfile=/export/pkgorder.txt  --arch=i386 --productpath=Fedora --src-discs=3 --total-discs=3 --bin-discs=3 --release-string="Fedora Core 1 Wizzy" --distdir=/export/i386 --srcdir=/export/SRPMS/

# yum-arch /export/i386/Fedora/RPMS
# ./splitdistro9 --fileorder /export/pkgorder.txt  --release "Fedora Core 1 (Wizzy)"  /export i386

step5:
	/usr/lib/anaconda-runtime/genhdlist --fileorder /export/pkgorder.txt --withnumbers --productpath=Fedora /export/i386-disc?

disk:
	pngtopnm logo3.png | ppmtolss16 \#000000=0 \#59e8e1=7 \#fefe00=2 \#ffffff=15 > splash.lss
	cp cdrom-ks.cfg /export/i386-disc1/ks.cfg
	cp syslinux.cfg /export/i386-disc1/isolinux/isolinux.cfg
	cp splash.lss /export/i386-disc1/isolinux
	mkdir -p /mnt/scratch
	mount -o loop /export/i386-disc1/images/bootdisk.img /mnt/scratch
	cp syslinux.cfg splash.lss /mnt/scratch
	umount /mnt/scratch
	mkisofs  -r  -J  -T  -V "Wizzy disc 1" -c isolinux/boot.cat  -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -o /export/test/wizzy-1.iso /export/i386-disc1
	mkisofs  -r  -J  -T  -V "Wizzy disc 2" -o /export/test/wizzy-2.iso /export/i386-disc2

############ end of Makefile ##################


> From: Chris Rouch <crouch@xxxxxxxxx>
> To: kickstart-list@xxxxxxxxxx
> Subject: buildinstall on fedora
> Date:    Tue, 23 Dec 2003 15:05:12 +0100
> Message-Id: <20031223150512.2eb24747.crouch@xxxxxxxxx>
> 
> I'm kind of confused about when I need to run buildinstall. 
> 
> I have a unified install tree with a correct comps.xml. Nfs installs
> work fine. Now I want to split it into individual CDs so I can do
> standalone installations.
> 
> For redhat 9 I did:
> 
> pkgorder /a/shrike/cdrom i386 > pkgorder.txt
> splitdistro --fileorder pkgorder.txt
> genhdlist --withnumbers --fileorder pkgorder.txt \
>     /a/shrike/i386-disc?
> 
> This works fine.
> 
> For fedora things seem to be a little different:
> 
> pkgorder /a/yarrow/cdrom i386 > /a/yarrow/cdrom/pkgorder.txt
> rm -rf /a/yarrow/cdrom-disc?
> /usr/lib/anaconda-runtime/splittree.py \
>     --pkgorderfile=/a/yarrow/cdrom/pkgorder.txt  --arch=i386
>     --productpath=Fedora --src-discs=3 \
>     --total-discs=3 --bin-discs=3 --release-string="Red Hat Linux" \
>     --distdir=/a/yarrow/cdrom/i386 --srcdir=/a/yarrow/cdrom/SRPMS/
> genhdlist --productpath Fedora --withnumbers \
>     --fileorder /a/yarrow/cdrom/pkgorder.txt /a/yarrow/cdrom-disc?
> 
> Again this seems to work. So do I need to run buildinstall at all, and
> if so, when?
> 
> Regards,
> 
> Chris




[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux