January 2017 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Arch Linux: Build for ARM (e.g. armv7l)
by Jan 10 Jan '17

10 Jan '17

Hi all, as already discussed at the openSUSE Forums[1], I would like to build some packages for Arch Linux ARM[2]. From my understanding the ARM Linux ARM repos have to be added to the OBS as a "Download on Demand" resource (like the existing one for "Arch:Core", "Arch:Extra", "Arch:Community"). So this has to be a feature request to the OBS maintainers, right? Or are there any other possibilities to reference packages from the Arch Linux ARM project/repositories? Cheers, Jan [1]: https://forums.opensuse.org/showthread.php/522205-Arch-Linux-Build-for-ARM-… [2]: https://archlinuxarm.org/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Missing build status in package result
by Andreas Schwab 09 Jan '17

09 Jan '17

There are currently five packages (blogilo, cups-pdf, python3-kiwi, python3-rnginline and u-boot-socfpgade0nanosoc) in devel:ARM:Factory:Contrib:ILP32 that are missing a build status: $ osc r --xml devel:ARM:Factory:Contrib:ILP32 python3-kiwi <resultlist state="9b5975a7bc0502b23906d92277113635"> <result project="devel:ARM:Factory:Contrib:ILP32" repository="standard" arch="aarch64" code="building" state="building" /> <result project="devel:ARM:Factory:Contrib:ILP32" repository="standard" arch="aarch64_ilp32" code="building" state="building" /> <result project="devel:ARM:Factory:Contrib:ILP32" repository="images" arch="local" code="unknown" state="unknown" /> <result project="devel:ARM:Factory:Contrib:ILP32" repository="images" arch="aarch64" code="blocked" state="blocked" /> <result project="devel:ARM:Factory:Contrib:ILP32" repository="images" arch="aarch64_ilp32" code="unpublished" state="unpublished" /> </resultlist> Note that <result> is missing the <status> element, and the packages aren't listed in the project-wide results. They have in common that they were recently added to openSUSE:Factory. Andreas. -- Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] How to deal with abandoned accounts?
by Brüns, Stefan 09 Jan '17

09 Jan '17

Hi everyone, OpenSUSE build service users come and go, and sometimes they leave a bunch of home projects around. I have seen several home projects which are a pristine link to some Factory or devel project, and thus get rebuild again and again. Normally, I would just file a delete request for the affected project, but obviously this may be just ignored by the (no longer active) account/project owner. Now, I might just send an e-mail to the OBS admins, but I am wondering if there is a better approach? Kind regards, Stefan-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] obs_worker: lxc.aa_allow_incomplete
by Matwey V. Kornilov 09 Jan '17

09 Jan '17

Hello, I am trying to deploy a worker using lxc as build VM type. I see the following at every build and all builds are failed. The question is how should I provide required lxc.aa_allow_incomplete option to lxc config? I tried /etc/lxc/default.conf, but it seems have no impact on obs started containers. I use obs-api 2.7.1 and lxc 1.1.2. Thank you. [ 27s] lxc-start: lsm/apparmor.c: apparmor_process_label_set: 169 If you really want to start this container, set [ 27s] lxc-start: lsm/apparmor.c: apparmor_process_label_set: 170 lxc.aa_allow_incomplete = 1 [ 27s] lxc-start: lsm/apparmor.c: apparmor_process_label_set: 171 in your container configuration file [ 27s] lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4 [ 27s] lxc-start: start.c: __lxc_start: 1164 failed to spawn 'obsbuild:root_1' [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/init.scope/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids/init.scope/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/hugetlb/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu,cpuacct/lxc/obsbuild:root_1-1 [ 27s] lxc-start: cgfs.c: cgroup_rmdir: 207 Device or resource busy - cgroup_rmdir: failed to delete /sys/fs/cgroup/net_cls,net_prio/lxc/obsbuild:root_1-1 [ 27s] lxc-start: lxc_start.c: main: 344 The container failed to start. [ 27s] lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] recovering from interconnect failures
by Olaf Hering 09 Jan '17

09 Jan '17

Is there a way for an ordinary, unprivileged user to "unbreak" a pkg? PMBS has a few failures like this, and 'osc rebuild -f' does not help to get such packages out of the 'broken' state: broken: openSUSE.org:multimedia:libs/flac: remote error: no socket attached Olaf

2 2

[opensuse-buildservice] Cross-architecture BuildRequires dependency
by David Adam 02 Jan '17

02 Jan '17

I'm trying to build a newer version of GCC for older versions of RHEL through OBS (so that we can ship our C++11 software). The SCL versions mostly work, with a bit of editing of the specfile, but the problem I'm left with is that the x86_64 build requires both 32- and 64-bit versions of libc. I've added a BuildRequires for "glibc(x86-32) glibc(x86-64) glibc-devel(x86-32) glibc-devel(x86-64)", as the SCL spec file has file-based dependencies, but these cannot be resolved by OBS. Is there a way to add a cross-architecture requirement? If not, I will try and find out how to build 64-bit-only GCC. Thanks, David Adam zanchey(a)ucc.gu.uwa.edu.au -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0