[opensuse-arm] No ARM JeOS* images built due to kiwi : command not found!
No JeOS images built due to error: kiwi: command not found https://build.opensuse.org/project/monitor?arch_armv7l=1&defaults=0&failed=1&project=openSUSE%3AFactory%3AARM&repo_images=1 The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 ********** To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found ********** Any idea why? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, after a rebuild, it still fails but because iproute2 is not found. iproute2 package is unresolvable. Guillaume Le 08/06/2012 14:46, Guillaume Gardet a écrit :
No JeOS images built due to error: kiwi: command not found
The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 **********
To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found **********
Any idea why?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Could you trigger a rebuild of all JeOS* images, please? Guillaume Le 09/06/2012 14:54, Guillaume Gardet a écrit :
Hi,
after a rebuild, it still fails but because iproute2 is not found. iproute2 package is unresolvable.
Guillaume
Le 08/06/2012 14:46, Guillaume Gardet a écrit :
No JeOS images built due to error: kiwi: command not found
The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 **********
To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found **********
Any idea why?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please?
There is no need to trigger them manually. It has tried already, but perl is still broken, so kiwi can not work yet.
Guillaume
Le 09/06/2012 14:54, Guillaume Gardet a écrit :
Hi,
after a rebuild, it still fails but because iproute2 is not found. iproute2 package is unresolvable.
Guillaume
Le 08/06/2012 14:46, Guillaume Gardet a écrit :
No JeOS images built due to error: kiwi: command not found
The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 **********
To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found **********
Any idea why?
Guillaume
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 12/06/2012 09:55, Adrian Schröter a écrit :
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please? There is no need to trigger them manually.
It has tried already, but perl is still broken, so kiwi can not work yet.
Ok. I thought it was due to mkfs problem which is (now) built. JeOS is OK but JeOS-beagle and others are broken. I will try to fix perl. Any idea of the problem for perl? It seems libs are not used with the linker (no -lpthread and others). Next week, I will go to "Salon solutions Linux" (http://en.opensuse.org/openSUSE:Solutions_Linux_2012) in Paris where openSUSE will have a booth and I would like to have a proper image for my beagleboard xM and run some cool demo for this event. Guillaume
Guillaume
Le 09/06/2012 14:54, Guillaume Gardet a écrit :
Hi,
after a rebuild, it still fails but because iproute2 is not found. iproute2 package is unresolvable.
Guillaume
Le 08/06/2012 14:46, Guillaume Gardet a écrit :
No JeOS images built due to error: kiwi: command not found
The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 **********
To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found **********
Any idea why?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 12/06/2012 10:29, Guillaume Gardet a écrit :
Le 12/06/2012 09:55, Adrian Schröter a écrit :
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please? There is no need to trigger them manually.
It has tried already, but perl is still broken, so kiwi can not work yet.
Ok. I thought it was due to mkfs problem which is (now) built. JeOS is OK but JeOS-beagle and others are broken.
I really think there is a problem with mkfs.ext3. Check the error log: |Jun-12 06:06:26 <1> : EXEC [which mkfs.ext3 2>&1] Jun-12 06:06:27 <1> : warning: mkfs.ext3 not found Jun-12 06:06:27 <3> : Requested image creation with filesystem "ext3"; but tool to create the file system could not be found. failed Jun-12 06:06:27 <3> : KIWI exited with error(s) done [ 1618.461900] SysRq : Power Off [ 1620.040964] Power down. | The problem is kiwi uses "which mkfs.ext3" to know where is it but as it is in /sbin/mkfs.ext3 it is not found while installed. (normal user has no /sbin folder in PATH). Should be fixed in kiwi? Maybe I have to open a bugzilla report? Guillaume
I will try to fix perl. Any idea of the problem for perl? It seems libs are not used with the linker (no -lpthread and others).
Next week, I will go to "Salon solutions Linux" (http://en.opensuse.org/openSUSE:Solutions_Linux_2012) in Paris where openSUSE will have a booth and I would like to have a proper image for my beagleboard xM and run some cool demo for this event.
Guillaume
Guillaume
Le 09/06/2012 14:54, Guillaume Gardet a écrit :
Hi,
after a rebuild, it still fails but because iproute2 is not found. iproute2 package is unresolvable.
Guillaume
Le 08/06/2012 14:46, Guillaume Gardet a écrit :
No JeOS images built due to error: kiwi: command not found
The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 **********
To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found **********
Any idea why?
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 12. Juni 2012, 13:13:23 schrieb Guillaume Gardet:
Le 12/06/2012 10:29, Guillaume Gardet a écrit :
Le 12/06/2012 09:55, Adrian Schröter a écrit :
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please? There is no need to trigger them manually.
It has tried already, but perl is still broken, so kiwi can not work yet.
Ok. I thought it was due to mkfs problem which is (now) built. JeOS is OK but JeOS-beagle and others are broken.
I really think there is a problem with mkfs.ext3. Check the error log: |Jun-12 06:06:26 <1> : EXEC [which mkfs.ext3 2>&1] Jun-12 06:06:27 <1> : warning: mkfs.ext3 not found Jun-12 06:06:27 <3> : Requested image creation with filesystem "ext3"; but tool to create the file system could not be found. failed Jun-12 06:06:27 <3> : KIWI exited with error(s) done [ 1618.461900] SysRq : Power Off [ 1620.040964] Power down.
| The problem is kiwi uses "which mkfs.ext3" to know where is it but as it is in /sbin/mkfs.ext3 it is not found while installed. (normal user has no /sbin folder in PATH). Should be fixed in kiwi? Maybe I have to open a bugzilla report?
yet another bug in qemu-accel. Fixed, but not yet finished to build. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Adrian Schröter wrote:
Am Dienstag, 12. Juni 2012, 13:13:23 schrieb Guillaume Gardet:
Le 12/06/2012 10:29, Guillaume Gardet a écrit :
Le 12/06/2012 09:55, Adrian Schröter a écrit :
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please?
There is no need to trigger them manually.
It has tried already, but perl is still broken, so kiwi can not work yet.
Ok. I thought it was due to mkfs problem which is (now) built. JeOS is OK but JeOS-beagle and others are broken.
I really think there is a problem with mkfs.ext3. Check the error log: |Jun-12 06:06:26 <1> : EXEC [which mkfs.ext3 2>&1] Jun-12 06:06:27 <1> : warning: mkfs.ext3 not found Jun-12 06:06:27 <3> : Requested image creation with filesystem "ext3"; but tool to create the file system could not be found. failed Jun-12 06:06:27 <3> : KIWI exited with error(s) done [ 1618.461900] SysRq : Power Off [ 1620.040964] Power down.
| The problem is kiwi uses "which mkfs.ext3" to know where is it but as it is in /sbin/mkfs.ext3 it is not found while installed. (normal user has no /sbin folder in PATH). Should be fixed in kiwi? Maybe I have to open a bugzilla report?
yet another bug in qemu-accel. Fixed, but not yet finished to build.
Huh? What does mkfs.ext3 have to do with qemu-accel? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 12. Juni 2012, 15:32:10 schrieb Alexander Graf:
Adrian Schröter wrote:
Am Dienstag, 12. Juni 2012, 13:13:23 schrieb Guillaume Gardet:
Le 12/06/2012 10:29, Guillaume Gardet a écrit :
Le 12/06/2012 09:55, Adrian Schröter a écrit :
Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet:
Could you trigger a rebuild of all JeOS* images, please?
There is no need to trigger them manually.
It has tried already, but perl is still broken, so kiwi can not work yet.
Ok. I thought it was due to mkfs problem which is (now) built. JeOS is OK but JeOS-beagle and others are broken.
I really think there is a problem with mkfs.ext3. Check the error log: |Jun-12 06:06:26 <1> : EXEC [which mkfs.ext3 2>&1] Jun-12 06:06:27 <1> : warning: mkfs.ext3 not found Jun-12 06:06:27 <3> : Requested image creation with filesystem "ext3"; but tool to create the file system could not be found. failed Jun-12 06:06:27 <3> : KIWI exited with error(s) done [ 1618.461900] SysRq : Power Off [ 1620.040964] Power down.
| The problem is kiwi uses "which mkfs.ext3" to know where is it but as it is in /sbin/mkfs.ext3 it is not found while installed. (normal user has no /sbin folder in PATH). Should be fixed in kiwi? Maybe I have to open a bugzilla report?
yet another bug in qemu-accel. Fixed, but not yet finished to build.
Huh? What does mkfs.ext3 have to do with qemu-accel?
The icecream.sh profile.d file did overwrite $PATH, so /usr/sbin kicked out. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Alexander Graf -
Guillaume Gardet