November 2015 - openSUSE Build Service

[opensuse-buildservice] Link local OBS instance to openSUSE OBS Project
by Mathias Radtke 18 Nov '15

18 Nov '15

Hi, in my company we currently use the openSUSE OBS to build our packages. In the last week we also build up a local OBS instance. Now we would like to link our local OBS to our remote OpenSUSE OBS Project so our locally build packages are automaticly uploaded to the remote Project. How can we achieve this? Thanks in advance -- Mathias Radtke, uib mail m.radtke(a)uib.de uib gmbh Bonifaziusplatz 1B 55118 Mainz www.uib.de www.opsi.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Patch: drop "Suggests:" and "Recommends:" if rpm does not know them
by Stefan Seyfried 17 Nov '15

17 Nov '15

Hi, I'm running an OBS instance, used amongst others to build stuff for multiple distributions (SLES and RHEL, mostly). Now if I import packages from openSUSE OBS, I often have to patch the spec file. 95% of these patches are like this: +%if 0%{?suse_version} Recommends: not_really_necessary_thing_1 Suggests: totally_unnecessary_thing_2 +%endif I automated this task in build-recipe-spec: If the target's RPM does not know "Recommends:" or "Suggests:", just drop these lines. This is made configurable with the following prjconf Buildflags: dropunknownrpmtags here is the patch for discussion, if this would be interesting for upstream, I'll prepare a proper pull request. diff --git a/build-recipe-spec b/build-recipe-spec index d72a3b7..f92d857 100644 --- a/build-recipe-spec +++ b/build-recipe-spec @@ -85,6 +85,40 @@ recipe_prepare_spec() { test -z "$ABUILD_TARGET" || echo "build target is $ABUILD_TARGET" fi + DROP_UNKNOWN=$(queryconfig --dist "$BUILD_DIST" --configdir "$CONFIG_DIR" --archpath "$BUILD_ARCH" buildflags dropunknownrpmtags) + if [ -n "$DROP_UNKNOWN" ]; then + declare -i SUSE_VERSION=$(chroot $BUILD_ROOT rpm --eval '%{?suse_version}' 2>/dev/null) + if ! [ -e "$BUILD_ROOT/usr/bin/rpmbuild" ]; then + echo "NOTE: no /usr/bin/rpmbuild in target, no check for unnown specfile tags" + elif ((SUSE_VERSION == 0)); then # just assume that every SUSE has patched RPM... + # echo "SUSE_VERSION is zero" + for i in Suggests: Recommends:; do + # if no suggests/recommends, then we don't need to test + grep "^$i" "$BUILD_ROOT/.spec.new" >/dev/null 2>&1 || continue + rm -f "$BUILD_ROOT/.spec.test" + cat > "$BUILD_ROOT/.spec.test" <<-EOF + $i foo + Name: foo + Version: 0 + Release: 0 + Summary: foo + License: WTFPL + + %description + foo + EOF + UNKNOWN="`chroot $BUILD_ROOT /bin/rpmbuild --nobuild /.spec.test 2>&1`" + # echo "found unknown tag '$UNKNOWN'" + RES=$? + rm -f "$BUILD_ROOT/.spec.test" + test $RES = 0 && continue + # echo "nobuild result for $i $RES" + echo "WARNING: removing unknown tag on non-SUSE distro: '$i'" + sed -i -e "/^$i/d" "$BUILD_ROOT/.spec.new" + done + fi + fi + # report specfile changes if test -f $BUILD_ROOT/.spec.new ; then if ! cmp -s $BUILD_ROOT$TOPDIR/SOURCES/$RECIPEFILE $BUILD_ROOT/.spec.new ; then Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

[opensuse-buildservice] ScientificLinux_7
by Christof Hanke 17 Nov '15

17 Nov '15

Hi OBS admins, just wanted to note that something is fishy with SL7. While installing the packages on the buildhost, every package-installs throws : """ [115/235] Can't locate Digest/MD5.pm in @INC (@INC contains: /.build /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /.build/Build.pm line 24. [ 139s] BEGIN failed--compilation aborted at /.build/Build.pm line 24. [ 139s] Compilation failed in require. [ 139s] BEGIN failed--compilation aborted. """ see e.g. https://build.opensuse.org/package/live_build_log/home:hauky:branches:Base:… But is installed anyway. T/Christof -- 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] OBS package request: borgbackup
by S. 17 Nov '15

17 Nov '15

Hi everyone, I don't know if this is the proper place for this, but would it be possible to request a package? I need the Borgbackup program (https://github.com/borgbackup/borg/releases) in order to use openSUSE. I tried to package it with the OBS but I'm running into dependency errors, as it's a fairly complex Python app. Thanks for the help! Sb -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] OBS build failing in endless loop
by Nathan Cutler 16 Nov '15

16 Nov '15

We are trying to build a recent version of Ceph in the OBS and failing. The exact same code builds fine in IBS, where one can get a build worker with 8GB of memory. In order to get past the OBS scheduler, however, I have to specify 4GB of memory. We can build locally with "make -j1" and 4GB of memory (i.e. specify build-memory = 4096 in .oscrc). In OBS, however, the build chugs along for some time and then fails like this: [ 9900s] CXX osd/libosd_types_la-PGLog.lo [ 9952s] CXX osd/libosd_types_la-osd_types.lo [10050s] CXX osd/libosd_types_la-ECUtil.lo [10057s] CXXLD libosd_types.la [10057s] CXX osd/libosd_la-PG.lo [10170s] /var/run/obs/worker/1/build/build-vm-kvm: line 191: 11733 Killed "$@" [10170s] ### WATCHDOG MARKER END ### [10171s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [10171s] or the build host has a kernel or hardware problem... The result is unhappy: the builds get retriggered and fail in the same way, over and over . . . and over. . . and over . . . The package in question, where you can see this endless loop in action right now: https://build.opensuse.org/package/show/filesystems:ceph:Unstable/ceph Any ideas? We would really like to get this package to build in OBS. Regards, Nathan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 7

[opensuse-buildservice] SUSE:SLE-12:Update: unresolvable: nothing provides ceph = 0.80.8-2.3 needed by ceph-devel
by Jörg Steffens 16 Nov '15

16 Nov '15

I'm trying to build a package for SLES12 with a build dependency to ceph-devel. My project configuration looks like this: <repository name="SLE_12"> <path project="SUSE:SLE-12:Update" repository="standard"/> <path project="SUSE:SLE-12:GA" repository="standard"/> <arch>x86_64</arch> </repository> However, I get the error: $ osc build Building dasscm.spec for SLE_12/x86_64 ... buildinfo is broken... it says: unresolvable: nothing provides ceph = 0.80.8-2.3 needed by ceph-devel Building only against "SUSE:SLE-12:GA" does not change the situation. Building on a SLES12 system (without OBS) with SLES12 SDK included, does work. Am I using the wrong project configuration or are there packages missing in OBS for SLES12? regards, Jörg -- Jörg Steffens joerg.steffens(a)dass-it.de dass IT GmbH http://www.dass-IT.de Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRB52500 Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- 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] Which repository for current tumbleweed kernel?
by Lorenz 15 Nov '15

15 Nov '15

Hi there, I noticed that the "Tumbleweed" repository has already kernel 4.3.0 available since Nov 6th. See http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/ kernel-default-4.3.0-1.1.x86_64.rpm Despite this, some kernel modules of my home repository home:lorenz:filesystems are still compiled for version 4.2.4 and have not yet since been scheduled for a new build. There seems to be quite some delay until the new kernel is "noticed". Is such a delay normal or did I specify the wrong repository? I specified Tumbleweed as <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>x86_64</arch> </repository> Is this the repository that ends up at http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/ ? I don't care too much about some delay, however I would like to have a consistent set of repositories. Now, with the two repos http://download.opensuse.org/tumbleweed/repo/src-oss http://download.opensuse.org/repositories/home:/lorenz:/filesystems/openSUS… a zypper dup complains about an unfulfilled dependency for zfs-kmp-default, as the old kernel is no longer available. Can I do something to change this? Is the slightly older Tumbleweed repo available somewhere? Or can I change the repository definition of my home project to point to the project that represents the current stuff in http://download.opensuse.org/tumbleweed/repo/oss ? Sorry for my confusion, Lorenz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 10

[opensuse-buildservice] Branched package is immediately out of date
by Jan Engelhardt 15 Nov '15

15 Nov '15

10:08 ares40:../Factory/librcd > sosc bco Note: The branch has been created of a different project, devel:libraries:c_c++, which is the primary location of where development for that package takes place. That's also where you would normally make changes against. A direct branch of the specified package can be forced with the --nodevelproject option. A home/jengelh/branches/devel/libraries/c_c++ A home/jengelh/branches/devel/libraries/c_c++/librcd A home/jengelh/branches/devel/libraries/c_c++/librcd/baselibs.conf A home/jengelh/branches/devel/libraries/c_c++/librcd/librcd-0.1.14.tar.bz2 A home/jengelh/branches/devel/libraries/c_c++/librcd/librcd.changes A home/jengelh/branches/devel/libraries/c_c++/librcd/librcd.spec At revision e6098240fb4b5a8babdf7e6c4af34a30. Note: You can use "osc delete" or "osc submitpac" when done. 10:08 ares40:../Factory/librcd > cd home/jengelh/branches/devel/libraries/c_c++/librcd/ 10:08 ares40:../c_c++/librcd > l total 316 drwxr-xr-x 3 jengelh users 133 Nov 15 10:08 . drwxr-xr-x 4 jengelh users 44 Nov 15 10:08 .. drwxr-xr-x 2 jengelh users 238 Nov 15 10:08 .osc -rw-r--r-- 1 jengelh users 8 Jun 18 2012 baselibs.conf -rw-r--r-- 1 jengelh users 308041 Dec 6 2013 librcd-0.1.14.tar.bz2 -rw-r--r-- 1 jengelh users 1983 Dec 6 2013 librcd.changes -rw-r--r-- 1 jengelh users 2320 Dec 6 2013 librcd.spec 10:08 ares40:../c_c++/librcd > osc ci -m. Working copy '/home/jengelh/obs/zu/openSUSE/Factory/librcd/home/jengelh/branches/devel/libraries/c_c++/librcd' is out of date (rev e6098240fb4b5a8babdf7e6c4af34a30 vs rev 525c137470bd0298e91306af96cf56c5). Looks as if you need to update it first. This appears to me as new behavior, but what is causing it? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 5

[opensuse-buildservice] OOM on build.opensuse.org / worker
by Jan Engelhardt 14 Nov '15

14 Nov '15

13:11 ares40:../science/ntl > osc r openSUSE_Tumbleweed i586 disabled openSUSE_Tumbleweed x86_64 disabled openSUSE_Leap_42.1 x86_64 succeeded* openSUSE_Factory x86_64 succeeded* openSUSE_Factory i586 succeeded* openSUSE_13.2 i586 succeeded* openSUSE_13.2 x86_64 succeeded* openSUSE_13.1 i586 succeeded* openSUSE_13.1 x86_64 failed SLE_12 x86_64 succeeded* SLE_11_SP3 i586 succeeded* SLE_11_SP3 x86_64 succeeded* 13:11 ares40:../science/ntl > sosc bl openSUSE_13.1 x86_64 fork: Cannot allocate memory Maybe the recent build failures in Ceph are linked to this. -- 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] build and docker
by Stanislav Baiduzhyi 13 Nov '15

13 Nov '15

Quick question: osc is preparing chroot under /var/tmp/build-root/openSUSE_Leap_42.1-x86_64 and deletes/reinstalls packages for different spec files. Is it possible to use docker image which contains all the needed dependencies instead or the chroot for build? If yes - any tutorials/links/ideas are appreciated. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1