Re: problem about PKGORDER !!!

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

 



On Wed Jun 19 2002 at 22:15, Michael Fratoni wrote:

> > I use anaconda-7.3-7 and anaconder-runtime-7.3-7.
> > My build source tree is /redhat/i386, and I use this,
> >
> > /usr/lib/anaconda-runtime/buildinstall  --pkgorder /redhat/pkgorder.txt
> > --comp  dist-7.3 --version 7.3 /redhat/i386
> >
> > The pkgorder.txt it generated is zero length, why?
> 
> Because the above command doesn't generate the package order, it tries to
> read it.

That is simply not true (go and read what it does).

buildinstall does run pkgorder (the version in the
anaconda-runtime-*i386.rpm it finds in the RedHat/RPMS/ directory).

By default (if --pkgorder is not specified), it creates a package
order file in a temporary build tree (i386/image-template/), but
this file is deleted when that directory is eventually blown away.

So unless --pkgorder is specified to create it elsewhere, you will
need to run pkgorder separately to create this file... it is needed
by splitdistro and genhdlist if you intend to create iso
installation images that work without constant disk-swapping.

The original problem lies elsewhere...

> > "Traceback (innermost last):
> >    File "/usr/lib/anaconda-runtime/pkgorder, line 10, in ?
> >      import whiteout
> > ImportError: No module named whiteout"

There is a module called /usr/lib/anaconda/whiteout.py, but it isn't
being found by the python interpreter...

> Try this:
> export PYTHONPATH=/usr/lib/anaconda
> /usr/lib/anaconda-runtime/pkgorder /redhat/i386 >/redhat/pkgorder.txt

Yep, that will stop the complaints.

Cheers
Tony





[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux