Eric,
===Option 2 -- this option involved copied the updates (which ones? all or just the main .rpm file?) This also means you must remove the 'old' package that is being replace right?
The makeCommon.sh script needs to generate a new common.pkd file. I tried this on my clean suse 8.0 tree and it generated a common.pkd file that seemed quite different from the file originally in the suse/setup/descr tree... How critical is the format of that file? The size field is different. Other things seem different as well.
Is there a 'new/improved' way to build the common.pkd file? Or is the specific not that critical? I was able to get a common.pkd file that looks mostly ok.
I prefered "Option 2". Here is my solution to update my local installation server: 1) get all rpms from a mirror with rsync, e.g. note: I do not want src-rpm's and patch-rpm's 2) filter the "latest" pacthes 3) copy the latest patches to the suse-directory-structure and save the old rpms 4) rebuild common.pkd note: the format is critical. For example the "flag-line" in section aaa_base needs "A2E". If this entry is absent then there will be an installation failure. That's all. I have written some scripts to perform these steps: You might want to have a look at: http://www.inf.uni-konstanz.de/~stoltze/projekte/autoinstall/index.html Regards CS -- Christian Stoltze Computer Science, University of Constance (Lake Constance/SW-Germany) Email: Christian.Stoltze@uni-konstanz.de Voice: +49 (0)7531 88-4448 Fax: +49 (0)7531 88-3577