Arthur Rodrigo Sawazachi Valadares wrote:
Hi Joel, I was doing something just like that. But this is what I'm
still getting, after using your method as well:
I created the image with $./mkimage /tmp yuminstall.py
and I copied the /tmp/ud.img to the http server.
Then I booted RHEL with updates=HTTPPATH/ud.img.
Got this after setting the NFS path on installer:
Traceback (most recent call last):
File "/usr/bin/anaconda", line 895, in ?
from yuminstall import YumBackend
File "/tmp/updates/yuminstall.py", line 21, in ?
from errors import *
^^^ it tell you that the error is in your yuminstall.py in line 21. This means that the updates thing is working but your file has something fishy in it.
Comments:
- be sure not to mix different files from different anacondas. if your working with a rhel5 anaconda use the yuminstall from rhel5.
even the subversion is important.
- do a pylint check before anything.
- add all the files that you changed.
Hope it helps.
On Thu, 2008-08-07 at 11:12 +0200, Joel Andres Granados wrote:
The best way to test stuff with anaconda is to pass the updates image on the command line.
1. create an updates image. Go to (http://jgranado.fedorapeople.org/anaconda/scripts/createUpdates). There has been lots of scripts to do this but this is what I use.
2. Put the image on the network somewhere (http server)
3. start install and pass "updates=http://server/path/to/updates.img";
this should work for all anaconda py files and should also work for the libraries that anaconda uses.
Hope it helps.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
--
Joel Andres Granados
Red Hat / Brno, Czech Republic
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
