Hi,
this is a known OBS bug, asked the admins to deploy a fix shortly.
Greetings, Dirk
On Dienstag, 31. März 2015, 22:32:53 wrote Dirk Müller:
Hi,
this is a known OBS bug, asked the admins to deploy a fix shortly.
it is deployed now
01.04.2015 12:54, Adrian Schröter пишет:
On Dienstag, 31. März 2015, 22:32:53 wrote Dirk Müller:
Hi,
this is a known OBS bug, asked the admins to deploy a fix shortly.
it is deployed now
Dirk, could you please explain how to fix it? I am facing the same at my private OBS instance while trying to build JeOS for 42.2:Ports.
Hi Matwey,
2017-04-08 21:29 GMT+02:00 Matwey V. Kornilov matwey.kornilov@gmail.com:
01.04.2015 12:54, Adrian Schröter пишет:
Dirk, could you please explain how to fix it? I am facing the same at my private OBS instance while trying to build JeOS for 42.2:Ports.
Well, I don't really remember anymore what was the issue two years ago. but in any case "armv8l" means that it is running in aarch32 mode on a aarch64 guest kernel. The solution we're using I think here is that we're using kernel-obs-build from armv7 for those image builds and boot them inside kvm on a aarch64 host with aarch64=0. That way the kiwi environment sees armv7l as architecture and continues building.
So IMHO the error is most likely that you're not using kernel-obs-build or it is from the wrong architecture.
Greetings, Dirk
-
Adrian Schröter -
Dirk Müller -
Matwey V. Kornilov