My Fedora Rawhide Wine builds are failing with:
/var/tmp/rpm-tmp.Bmdtkq: line 88: /opt/wine-devel/bin/find-debuginfo.sh: No such file or directory
It should be looking in /usr/lib/rpm for find-debuginfo.sh (as it used to until a few weeks ago), not /opt/wine-devel/bin. Any idea why this suddenly changed, and more importantly, is there a way I can work around this?
Rosanne DiMesio <dimesio(a)earthlink.net>
We've got some updates regarding OBS and GitHub/GitLab integration.
Please, have a look and let us know what you think!
Daniel Donisa - daniel.donisa(a)suse.com
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
I wonder about the following build failure report:
[ 22s] linux64 /usr/bin/qemu-system-aarch64 […]
[ 329s] [ 329s] ### WATCHDOG TRIGGERED, KILLING VM ###
[ 329s] /var/cache/obs/worker/root_2/root: 61042
[ 329s] qemu-system-aarch64: terminating on signal 15 from pid 41534
[ 329s] ### VM INTERACTION END ###
[ 329s] /var/run/obs/worker/2/build/build-vm: line 498: kill: (61004) -
No such process
[ 329s] No buildstatus set, either the base system is broken
[ 329s] or the build host has a kernel or hardware problem...
gave up after 9 failed build attempts...
First question I have is what should I as package maintainer do about
that. Isn't this much more a problem for the infrastructure admins? And
second, what can *I* do about it?
I was tracking down a package fix and found this related request, but I
can't see it via webui, either logged in or anonymous.
returns 500 - server error
Works fine by osc / api, and other requests are fine over webui. Can
anyone else verify?
Is there a problem with this request, or other server issue?
I'm trying to build hivex from Fedora 34 in a private OBS appliance
(running version 2.10.5), and I'm getting a weird failure:
> package build was not possible:
> no compliant workers (constraints mismatch hint: hostlabel)
> Please adapt your constraints.
What's frustrating here is that there are no constraints defined as
far as I can tell. I've copied the package from my internal instance
to the openSUSE Build Service to test there, and it seems to start
(though it fails for a second reason that I don't understand).
I did some spelunking in the logs, and nothing in particular seems to
indicate any kind of constraints evaluation too.
Anyone have any idea what's going on?
真実はいつも一つ！/ Always, there's only one truth!
I have read docs and slides and googled like crazy and this exact scenario still eludes me.
Given these two packages in the same project:
1. contains some helpful scripts
2. has no deps and nothing to compile
3. takes about 5 minutes for OSB to build
1. contains binaries and other stuff
2. specfile `Requires: pkg-a` so that if you install pkg-b you also get pkg-a
3. Takes hours to build because lots of things need rebuilt when it is
Due to that `Requires:` in item 2.2 ➜ when pkg-a is built pkg-b is rebuilt. That’s just silly, nothing in pkg-a affects pkg-b, pkg-b just wants to ensure pkg-a is installed at runtime.
Is there a way to make OBS not do that and still ensure pkg-b comes in when you install pkg-a?
Like “when this package is being built do not try to auto-rebuild anything else”, was hoping for prjconf but nothing seems to fit exactly.
The reasons why its important is:
1. It makes an urgent release take hours longer than it should (or a normal release tediously slow)
2. it uses up resources other things need for no reason
3. all of the unnecessary builds can pile up and break when doing API calls to build.opensuse.org