Project

General

Profile

Bug #5151

OBS armv7 builds fail with "could not autodetect package type"

Added by osmith about 1 month ago. Updated 7 days ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
05/12/2021
Due date:
% Done:

100%

Spec Reference:

Description

Some armv7 builds are failing with the following:

[    1s] 
[    1s] armbuild04 started "build open5gs_2.2.8.202105110026.dsc" at Tue May 11 17:22:37 UTC 2021.
[    1s] 
[    1s] Building open5gs for project 'network:osmocom:nightly' repository 'Debian_10' arch 'armv7l' srcmd5 '043932919ec53053d14455bc4d0f5119'
[    1s] 
[    1s] processing recipe /var/cache/obs/worker/root_2/.build-srcdir/open5gs_2.2.8.202105110026.dsc ...
[    1s] running changelog2spec --target debian --file /var/cache/obs/worker/root_2/.build-srcdir/open5gs_2.2.8.202105110026.dsc
[    1s] init_buildsystem --configdir /var/run/obs/worker/2/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /var/cache/obs/worker/root_2/.build.rpmlist /var/cache/obs/worker/root_2/.build-srcdir/open5gs_2.2.8.202105110026.dsc build ...
[    1s] unknown keyword in config: 
[    1s] could not autodetect package type
[    1s] 
[    1s] armbuild04 failed "build open5gs_2.2.8.202105110026.dsc" at Tue May 11 17:22:37 UTC 2021.
[    1s] 

This appears to be a problem with the "armbuild04" node. The same packages build fine with e.g. "armbuild21".

This is an upstream issue, I have reported it in #opensuse-buildservice, and got the suggestion to add "binarytype: deb" to the prjconf as workaround, while this is being looked into. I did add the following, but the result is the same:

%if 0%{?debian_version}
binarytype: deb
%endif

History

#1 Updated by laforge 29 days ago

It has been one week and we're still suffering this issue. Osmocom users on ARM platforms as a result have a broken package feed for one week.

If we look at https://build.opensuse.org/project/monitor/network:osmocom:nightly we see that this affects
  • Debian 10 / armv7l
  • Debian 9 / armv7l
  • Raspbian 10 / armv7l

They all fail due to the last successful osmo-gsm-manuals build is 20210818 while osmocom-nightly is already 20210819.

#2 Updated by osmith 7 days ago

  • Status changed from Stalled to Resolved
  • % Done changed from 0 to 100

We did not receive e-mails with that build failure anymore. However, the armv7l builders were always behind, and could not finish building packages before the next nightly sources were pushed. As discussed, I've disabled armv7l for debian 9 and 10 for the nightly feed.

See also: #5165

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)