|
Hello,
When exporting KIWI configuration from SuSE Studio web service the script run at the end of the building is exported to a file called build-custom under source/root. This script however is not run. Please consider this suggestion for a fix: Add the option "--edit-bootconfig" with the value of "source/root/build-custom" to "kiwi --create" command line in create_appliance.sh. Also, either the directory where "kiwi --create" must be changed for build-custom to work(e.g. "./kconfig" line in the script) or a path added in front of every file path in the build-custom script. How is the script executed in the web service? Our workaround for this issue is to define a root path variable at the start of the build-custom script and apply the variable to each path, like so: ROOT="build/root" # read in some variables . ${ROOT}/studio/profile Thank You |
|
Administrator
|
Hi there,
On 10/14/2011 01:10 PM, vqdox wrote: > Hello, > > When exporting KIWI configuration from SuSE Studio web service the script > run at the end of the building is exported to a file called build-custom > under source/root. This script however is not run. > > Please consider this suggestion for a fix: > > Add the option "--edit-bootconfig" with the value of > "source/root/build-custom" to "kiwi --create" command line in > create_appliance.sh. > > Also, either the directory where "kiwi --create" must be changed for > build-custom to work(e.g. "./kconfig" line in the script) or a path added in > front of every file path in the build-custom script. > > How is the script executed in the web service? Our workaround for this issue > is to define a root path variable at the start of the build-custom script > and apply the variable to each path, like so: > > ROOT="build/root" > > # read in some variables > . ${ROOT}/studio/profile > > Thank You Thanks for the feedback and proposed solution! We'll take a closer look at this next week and try to get it fixed soon. -- Regards, James Tan Engineering Manager, SUSE Studio Online Novell Inc. / SUSE Linux Products GmbH Maxfeldstr. 5, 90409 Nuremberg, Germany |
|
Hi! Few corrections, I was too hasty to report without taking a second look: * The build-custom script is actually run after all, as seen from prepare.log: Oct-14 22:47:46 <1> : EXEC [chroot <PATH>/build/root chown -c root:root "tmproot/build-custom" 2>&1] ... /build-custom: line 16: /studio/profile: No such file or directory So for some reason the script doesn't find the files. Is this script run in chroot environment? Also please notice that the first two commands are not added by us but are provided by SuSE Studio in the script template: # read in
some variables . ${ROOT}/studio/profile # read in KIWI utility functions . .kconfig Thank you for your answer. Our current workaround is to add the commands to source/etc/init.d/suse_studio_firstboot but this is probably not the right way, assuming that the script could contain command to alter stuff in the system before it's actually built completely. From: James Tan <[hidden email]> To: vqdox <[hidden email]> Cc: [hidden email] Sent: Friday, October 14, 2011 10:40 PM Subject: Re: [studio-users] Export KIWI configuration - build-custom is not run Hi there, On 10/14/2011 01:10 PM, vqdox wrote: > Hello, > > When exporting KIWI configuration from SuSE Studio web service the script > run at the end of the building is exported to a file called build-custom > under source/root. This script however is not run. > > Please consider this suggestion for a fix: > > Add the option "--edit-bootconfig" with the value of > "source/root/build-custom" to "kiwi --create" command line in > create_appliance.sh. > > Also, either the directory where "kiwi --create" must be changed for > build-custom to work(e.g. "./kconfig" line in the script) or a path added in > front of every file path in the build-custom script. > > How is the script executed in the web service? Our workaround for this issue > is to define a root path variable at the start of the build-custom script > and apply the variable to each path, like so: > > ROOT="build/root" > > # read in some variables > . ${ROOT}/studio/profile > > Thank You Thanks for the feedback and proposed solution! We'll take a closer look at this next week and try to get it fixed soon. -- Regards, James Tan Engineering Manager, SUSE Studio Online Novell Inc. / SUSE Linux Products GmbH Maxfeldstr. 5, 90409 Nuremberg, Germany |
| Powered by Nabble | Edit this page |
