Additional package not in ISO-image, updated also
Hi, I found a strange behaviour of AutoInstall regarding addition and update of RPMs, which have not been in the original distribution. Completing what I wrote below, packages are not prepared for CD-image-creation, when: - I copy a freshly downloaded and updated package, deleting the original one (happened to autoyast2-installation) - I add any new RPM to the respective architecture folder (e.g. i386) Of course the create_package_descr is run after every change. Does anybody know how AutoInst compiles the list of files to prepare for CD-creation and if any, where the (temporary) file is located? I would like to learn more how AutoInst works, to understamd why it is unable to behave the expected way. Silvério Santos ----- Forwarded by Silverio SANTOS/Germany/Equant on 19.08.2003 10:16 ----- To: suse-autoinstall@suse.com Silverio SANTOS cc: 28.07.2003 11:46 bcc: Subject: Additional package not in ISO-image Hi, I added an additional package into a newly created i386-folder and have run the create_package_descr as described. The package identifies itself as i386-arch. The problem is that the file is not added to the ISO-image, from which I would like to install the target-system. I found that an earlier version of the package that I created (compiled and packaged) on this system is found in every packages-file that has been created by create_package_descr. That means that there is the same package with 2 different version numbers in the packages files. Is this the cause for the malfunction? How can I get the additional package integrated into the ISO-file? Thanks Silvério Santos
Op dinsdag 19 augustus 2003 10:27, schreef silverio.santos@equant.com:
Hi,
I found a strange behaviour of AutoInstall regarding addition and update of RPMs, which have not been in the original distribution.
Completing what I wrote below, packages are not prepared for CD-image-creation, when: - I copy a freshly downloaded and updated package, deleting the original one (happened to autoyast2-installation) - I add any new RPM to the respective architecture folder (e.g. i386) Of course the create_package_descr is run after every change.
Does anybody know how AutoInst compiles the list of files to prepare for CD-creation and if any, where the (temporary) file is located? I would like to learn more how AutoInst works, to understamd why it is unable to behave the expected way.
Silvério Santos
What happens if you remove and re-add the Software source (in yast). Normally yast uses some kind of caching... -- Richard Bos Without a home the journey is endless
participants (2)
-
Richard Bos
-
silverio.santos@equant.com