This is almost the 'default' problem when you do a 'create_package_descr'. What you must do is a create_package_descr -d /install/suse -l german -l english -x /usr/share/autoinstall/EXTRA_PROV This will do the works! Regards Harry
-----Original Message----- From: Daniel Bertolo [SMTP:daniel.bertolo@kinderheim-buehl.ch] Sent: Wednesday, July 09, 2003 9:31 AM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Problem after creating new package db
Hi
I would like to update my repository with some updated RPMs. As described in the autoyast howto, I run "/usr/lib/YaST2/bin/create_package_descr -d /install/suse -l german -l english". The package describtions will be created and stored in "./setup/descr". But when I would like to configure the packages in autoyast, hundreds of dependencies failed, starting with "missing /bin/awk; missing /bin/bash" etc.
The only way I found to fix it was to recopy the repository from the DVDs. But then I still have the old packages.
What do I do wrong?
By the way: What is the best way in order to keep the repository up-to-date. Is there a way that the clients always boot over the network in order to check for updates? I would like the clients to do the following during boot:
- Boot over network using PXE - Check if there is a local linux installation - If no -> install - If yes -> compare the installed packages to the repository - If there are updates -> install the updated packages -> local boot - If there are no updates -> local boot
This is what the SuSE Smart Client Framework does. But how do I implant this? There is no howto and the consultants I know do not want to tell me how to do it unless they can do it.
Thanks for help. Daniel Bertolo
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com