On 19.03.22 20:11, Stefan Seyfried wrote:

I'm actually not sure if the lxc setup on the pi2 is correct, but since it does not even get a single build job scheduled, this should not yet matter. It also does not get anything with "chroot".

Can I find out anything about the problem from my side or can only the PMBS admin investigate the issue (in that case, I'd probably try to set up my own OBS instance for investigation)?

I might have found it. From a .osc/_buildconfig-openSUSE_Tumbleweed-armv7l when trying to build locally: ### from openSUSE.org:openSUSE:Factory ... %_repository ports ... # new: use kernel-obs-build from aarch64 for aarch64 armv6 and armv7 ExportFilter: ^kernel-obs-build.*\.armv6hl\.rpm$ ExportFilter: ^kernel-obs-build.*\.armv7hl\.rpm$ ExportFilter: ^kernel-obs-build.*\.aarch64\.rpm$ . armv6l armv7l # now make sure the jobs get a 64bit cpu, otherwise can not run the 64bit kernel %ifarch armv6l armv7l Constraint: hardware:cpu:flag cpuid %endif How can I remove this constraint on Packman side? Or (better) can this please be fixed in the openSUSE.org config? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

On 19.03.22 21:06, Andreas Schwab wrote:

On Mär 19 2022, Stefan Seyfried wrote:

...

How can I remove this constraint on Packman side?

I think you can remove all constraints with !*:

Constraint: !*

Ah, I see. However, I would need to manually reintroduce all the wanted/necessary constraints or things would probably break in interesting ways. I have now given up the plan to reuse the old raspberry pi2 as an OBS worker, am trying to procure some raspberry pi4 8GB machines instead (once they become available anywhere), trying to get rebuild time down so the build finishes before the next full-rebuild-triggering package is released in 15.4 or Factory ;-) thanks, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Hi Adrian, On 24.03.22 14:23, Adrian Schröter wrote:

On Donnerstag, 24. März 2022, 14:06:10 CET Stefan Seyfried wrote:

...

On 19.03.22 21:06, Andreas Schwab wrote:

...

On Mär 19 2022, Stefan Seyfried wrote:

...

How can I remove this constraint on Packman side?

I think you can remove all constraints with !*:

Constraint: !*

Ah, I see. However, I would need to manually reintroduce all the wanted/necessary constraints or things would probably break in interesting ways.

I have now given up the plan to reuse the old raspberry pi2 as an OBS worker, am trying to procure some raspberry pi4 8GB machines instead (once they become available anywhere), trying to get rebuild time down so the build finishes before the next full-rebuild-triggering package is released in 15.4 or Factory ;-)

why don't you just build using KVM as well?

This will not help, as it cannot run the 64bit aarch64 kernel, and the 32bit armv6/armv7 kernels are forbidden by the project config.

only then the constraints can be fullfilled and IMHO that should work fine with a Raspberry Pi4 8GB (not tested myself though)

It works on the raspi400 (raspberry pi4 with 4GB) and on a raspi3 (only 1GB) as well. I originally wanted to reuse a spare raspberrypi 2 (also 1GB) as explicit armv7 worker, but the projectconf constraints prevent that. IF it would be easy to get 8GB raspberry pi4's, then there would be not much need to discuss this ;-) But I've given up on the plan of reusing the raspi2 anyway for now. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman