please answer to the list, not to me personally:
Am Donnerstag, 29. Juli 2021, 09:02:59 CEST schrieb 山田ハヤオ:
> I have already read the guidelines.
> But it's a simple Arch Linux link to the WIki, nothing about the Open Build
Looks like the documentation needs some love....
> I want to migrate the packages I post to AUR to Open Build
> There are various files in the osc package.
> Which of them do you need for Arch Linux?
osc as I can see from PKGBUILD.
There are additional dependencies (python-m2crypto) where OBS takes care
I 'm trying to build my Arch Linux repository using Open Build Service.
I created an account and posted my home project PKGBUILD.
But the wiki and documentation only has documentation for Spec files, not
for Arch Linux.
Even if I upload PKGBUILD from the web client, the build fails.
My repository and the package that has a problem is here
Please tell me how to
Looking at other people's repositories, it looks like the repositories need
files other than PKGBUILD, but I couldn't find any documentation about them.
My ARM-64 server has been churning out ARM-32 builds happily for some
time, until today (it worked fine as recently as last week.) The 32-bit
builds are failing with "no compliant workers (constraints mismatch
hint: hardware:cpu)", and osc checkconstraints shows that there are 0
armv7l workers (whereas our x86_64 machine is also providing the i586
workers.) However, osc workerinfo shows that the ARM-64 worker does not
have the "nativeonly" tag which would exclude it from 32-bit builds.
Our OBS server is pushing a hacked version of bs_worker which backports
confirmed that this hacked bs_worker is still present in
/usr/lib/obs/server, and that the worker has it in its
/run/obs/worker/<num>/worker directory. Any ideas on why ARM-32 builds
are suddenly not working?
I am running a private OBS instance with an ARM worker based on
Worker version is
Everything worked fine until today I found that the worker is broken. It
cannot boot the KVM machine. I see the silence after:
[ 32s] /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic
-vga none -cpu host,aarch64=off -enable-kvm -M virt,gic-version=host
-object rng-random,filename=/dev/random,id=rng0 -device
virtio-rng-device,rng=rng0 -runas qemu -net none -kernel
root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime
ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock
elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc
console=ttyAMA0 init=/.build/build -m 3072 -drive
-device virtio-blk-device,drive=disk,serial=0 -drive
-device virtio-blk-device,drive=swap,serial=1 -serial stdio -chardev
-mon chardev=monitor,mode=readline -smp 4
Then I've found that kernel and initrd images are for aarch64
architecture in spite of -cpu host,aarch64=off argument. This is a case
of my qemu failure. I suppose this is somehow connected to the new
upstream OBS ARM workers, which are not able to run armv7 kernels inside
Is it a known issue? How could I recover service operation?
With best regards,
Matwey V. Kornilov
I ran into a strange problem while trying to enable the "SUSE
SLE-15-SP3" repository in a project. As soon as I clicked on it,
"openSUSE Leap 15.3" got disabled. It seems as if the two buttons were
somehow linked. How can I enable both, like I have it in other projects?
We want to build our CODE12 based products ("_product" package) on CODE15. I
have been following the way openSUSE Leap 15.x and SLE15 products are being
built, but I am not sure which "00X..." packages should contain which files.
The Product Definition wiki page still refers to "_product" details:
I couldn't find any documentation in either the OBS User or Administrator guide.
I also searched the KIWI-ng documentation. I found 2 mentions of building
products, but I can't find any useful content:
I installed and ran the "obs-service-product_converter" service script locally
on our existing "_product" package. After making a few changes to the My.product
file, I was able to run the script. It generated following files:
* A _multibuild file.
* KIWI files for each media.
* Keywords (KWD) files for each media.
* Release package spec and changes files.
* Where shall I place these files? In a package called 000product?
* How do we use 000package-groups, 000release-packages, and 000update-repos
* How were these packages created for the first time in openSUSE:Leap:15.1
xUbuntu_21.04 builds using the qtbase5-private-dev package are unresolvable because of the following error:
unresolvable: have choice for libfontconfig1-dev needed by qtbase5-private-dev: libfontconfig-dev libfontconfig1-dev
For a sample project triggering this error see https://build.opensuse.org/package/show/home:tumic:GPXSee/gpxsee