-----Ursprüngliche Nachricht----- Von: Richard Bos [mailto:richard.bos@xs4all.nl] Gesendet: Mittwoch, 9. Juli 2003 10:39 An: Daniel Bertolo Betreff: Re: [suse-autoinstall] Problem after creating new package db
On Wednesday 09 July 2003 09:31, Daniel Bertolo wrote:
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?
What SuSE version? Did you include the EXTRA_PROV file, located in /usr/share/autoinstall/
SL 8.2. Yes, I include the EXTRA_PROV file (for a Java-RPM). This worked before. The problem I described appears if I replace an original RPM in the repository (in my case, I replaced yast2-ldap-client-2.7.6 with yast2-ldap-client-2.7.7). Afterwards, I do the create_package_descr and the new descriptions will be written to /install/suse/setup/descr/packages[.lang]. When I open yast2 and click on "add software" for the local machine, all dependencies are good and the updated packages are shown. But as soon as I run "yast2 autoyast" and configure the package selections, hundreds of dependencies fail. But the new packages are shown, too. What do I do wrong. Should I better let the original repository as is and use EXTRA_PROV also for updates?
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
Is this during installation or operation? I do this with apt. Just put "apt-rpm -y upgrade" in the boot sequence and in a crontab (n case the system is not booted) and the system will be kept up to date nicely. You can create a local apt repository with apt4rpm. As spinoff of that tool you can keep your installation package up to date keep easily as well (only a ver small additional script is needed).
I would like to put this in the boot-sequence in order to update the clients during boot. I will have a look for a apt-howto on the net. Guess there are some, aren't there? But thank you for the idea.
-- Richard Bos