November 2015 - openSUSE Build Service

[opensuse-buildservice] enabling networking for workers
by Darin Perusich 19 Dec '17

19 Dec '17

Hello All, I'm running a private instance and I'd like to enable networking on my workers so they can build some java apps, via maven, which need to download pom's/war's from the net. I ask google but he wasn't much help so I'm hoping someone here can help;-) How can I go about doing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 10

[opensuse-buildservice] broken mirror tux.rainside.sk
by Olaf Hering 16 Jan '17

16 Jan '17

Not sure what the correct list is to report mirror issues, but http://tux.rainside.sk/opensuse/ is empty. laf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Leap in OBS
by Stanislav Baiduzhyi 06 Oct '16

06 Oct '16

I can see that some projects are already building for Leap_42.1, but it is not in the checkboxes on Repositories tab on OBS project page, and in advanced repo UI there are so many of them that it is quite confusing. Will it be added to the checkboxes eventually, to make some packages "Leap ready"? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

Re: [opensuse-buildservice] usernames with dots
by Carsten Höger 01 Mar '16

01 Mar '16

Hi Johannes, > On 26 Aug 2015, at 14:01 , Johannes Lahti <johannes(a)nomasi.com> wrote: > > Hi! > > > "Is that really the case or am I hitting a bug here?" > > That seems to be the case. You can try fixing this in routes.rb. I took a stab at it before, but gave up and instead instructed people to avoid dots in the usernames. Henne was so kind to help making it work: using this patch https://gist.github.com/hennevogel/c85750f514c454d60aaf it is now working for me. There might be more places with these problems, though I opened another issue for that, btw.: https://github.com/openSUSE/open-build-service/issues/1064 -- mit freundlichen Gruessen/with best regards, Carsten Hoeger Open-Xchange GmbH -------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nürnberg, Amtsgericht Nürnberg HRB 24738 Vorstand: Rafael Laguna de la Vera, Carsten Dirks Aufsichtsratsvorsitzender: Richard Seibt European Office: Open-Xchange GmbH, Martinstr. 41, D-57462 Olpe, Germany Amtsgericht Siegen, HRB 8718, Geschäftsführer: Frank Hoberg, Martin Kauss US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA --------------------------------------------------------------------------------

1 1

[opensuse-buildservice] SLE_12: build host kernel problems
by Ruediger Meier 01 Mar '16

01 Mar '16

Hi, I get kernel oopses very often for SLE_12 builds on x86_64 and ppc64le. Is this a known problem? Here one example for SLE_12 x86_64: [ 205.213153] BUG: unable to handle kernel paging request at ffffffffa01fae60 [ 205.214124] IP: [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.214914] PGD 1a0d067 PUD 1a0e063 PMD 1f99fd067 PTE 0 [ 205.215738] Oops: 0010 [#1] SMP [ 205.216239] Modules linked in: sd_mod raid1 raid0 md_mod cramfs ext4 crc16 mbcache jbd2 sr_mod cdrom ata_generic virtio_blk ata_piix ahci libahci libata scsi_mod virtio_pci virtio_ring virtio binfmt_misc loop autofs4 [last unloaded: scsi_debug] [ 205.217089] Supported: Yes [ 205.217089] CPU: 2 PID: 24652 Comm: systemd-udevd Not tainted 3.12.28-4-default #1 [ 205.217089] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20150318_003745-cloud117 04/01/2014 [ 205.217089] task: ffff8800bad38040 ti: ffff8800bad32000 task.ti: ffff8800bad32000 [ 205.217089] RIP: 0010:[<ffffffffa01fae60>] [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.224409] RSP: 0018:ffff8800bad33d50 EFLAGS: 00010286 [ 205.225280] RAX: ffffffffa01fae60 RBX: ffff8801f9b39028 RCX: 0000000000000286 [ 205.226668] RDX: ffff8801f9b39260 RSI: 0000000000000286 RDI: ffff8801f9b39018 [ 205.227561] RBP: ffff8801f9b39018 R08: ffff8800bad32000 R09: 0000000000000000 [ 205.227561] R10: ffffffff81f7b558 R11: 0000000000000000 R12: ffff8801a8f56180 [ 205.227561] R13: ffff8801f9439bd8 R14: 000000000000005d R15: 0000000000000000 [ 205.227561] FS: 00007f434c12c880(0000) GS:ffff880204f00000(0000) knlGS:0000000000000000 [ 205.227561] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 205.227561] CR2: ffffffffa01fae60 CR3: 00000000bad72000 CR4: 00000000000407e0 [ 205.232887] Stack: [ 205.232887] ffffffff81393a7d ffff8801f9b39028 ffffffff81ae4d40 ffff8801f8c63a80 [ 205.232887] ffffffff8129a352 ffff8800bb46c800 ffff8801f9b39018 ffff8801a8f56300 [ 205.232887] ffffffffa003be21 ffff8800bb46c9a0 ffff8800bb46c990 ffff8801a8f56300 [ 205.232887] Call Trace: [ 205.232887] Inexact backtrace: [ 205.232887] [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffffa003be21>] ? scsi_host_dev_release+0xc1/0xe0 [scsi_mod] [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffff8106db07>] ? execute_in_process_context+0x67/0x70 [ 205.232887] [<ffffffff81393a7d>] ? device_release+0x2d/0xa0 [ 205.232887] [<ffffffff8129a352>] ? kobject_cleanup+0x72/0x1a0 [ 205.232887] [<ffffffffa021077b>] ? scsi_disk_put+0x2b/0x40 [sd_mod] [ 205.232887] [<ffffffff811d55bd>] ? __blkdev_put+0x15d/0x1a0 [ 205.232887] [<ffffffff811d6011>] ? blkdev_close+0x21/0x30 [ 205.248034] [<ffffffff811a0382>] ? __fput+0xc2/0x240 [ 205.248034] [<ffffffff81073947>] ? task_work_run+0x97/0xd0 [ 205.248034] [<ffffffff81002929>] ? do_notify_resume+0x69/0xa0 [ 205.248034] [<ffffffff81519603>] ? int_signal+0x12/0x17 [ 205.248034] Code: Bad RIP value. [ 205.248034] RIP [<ffffffffa01fae60>] 0xffffffffa01fae60 [ 205.248034] RSP <ffff8800bad33d50> [ 205.248034] CR2: ffffffffa01fae60 [ 205.248034] ---[ end trace ec1ae60827e0b798 ]--- [ 205.254616] systemd-udevd[1223]: worker [24652] terminated by signal 9 (Killed) [ 205.255711] systemd-udevd[1223]: worker [24652] failed while handling '/devices/pseudo_0/adapter0/host10/target10:0:0/10:0:0:0/block/sda/sda1' [ 205.454695] scsi_debug: host protection [ 205.455316] scsi11 : scsi_debug, version 1.82 [20100324], dev_size_mb=50, opts=0x0 [ 205.456558] scsi 11:0:0:0: Direct-Access Linux scsi_debug 0004 PQ: 0 ANSI: 5 [ 205.460037] sd 11:0:0:0: [sda] 102400 512-byte logical blocks: (52.4 MB/50.0 MiB) [ 205.464032] sd 11:0:0:0: [sda] Write Protect is off [ 205.464732] sd 11:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 205.472036] sd 11:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA qemu: terminating on signal 15 from pid 25397 Killed Job ### WATCHDOG MARKER END ### No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) or the build host has a kernel or hardware problem... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 18

[opensuse-buildservice] Ghost package
by trcs＠gmx.com 14 Dec '15

14 Dec '15

Hi. There is a ghost package in my OBS home project. I'm using the web interface, not the command line one. If you go to https://build.opensuse.org/project/show/home:jcsl:LXDE you can see the real 10 packages in the Packages box on left side, but if you look in the Build Results box, on the right side, you see 11 next to the "succeeded" text. If you then click the succeeded link you find the pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package "pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It even appears in the scheduled and building states when something I'm building triggers its build (I don't know how can this be). Any hints? Greetings. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] nothing provides libecpg6 = 8.3.23 needed by postgresql-devel
by Christian 02 Dec '15

02 Dec '15

This happens for 'SLE_4' project. when building a package which 'BuildRequires: postgesql-devel' then I get different info from buildservice: on SLE_11_SP3 projects I get: have choice for postgresql-devel needed by SOPE-devel: postgresql91-devel postgresql-devel on SLE_11_SP4 projects I get: nothing provides libecpg6 = 8.3.23 needed by postgresql-devel, nothing provides libpq5 = 8.3.23 needed by postgresql-devel on project SLE_11_SP4 I would have expected to get: have choice for postgresql-devel needed by SOPE-devel: postgresql94-devel postgresql-devel Can someone please fix the 'postgresql-devel' package on SLE_11_SP4 that way, that it is possible to add to 'project config': Prefer: postgresql91-devel or Prefer: postgresql94-devel Thanks in any advance -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- 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] Onion Service
by Malte 30 Nov '15

30 Nov '15

Hi, a post [1] from Jos (Poortvliet) on the ownCloud mailing list brought up the topic of censorship circumvention, I suggested setting up a Tor Onion Service [2] and was directed here(ish). So, if the maintainers of OBS would not mind setting up such an onion service, I (and hopefully others) would appreciate it. Sincerely, Malte [1] https://mailman.owncloud.org/pipermail/devel/2015-November/001758.html [2] https://mailman.owncloud.org/pipermail/devel/2015-November/001761.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Most ARM v7 workers are broken
by Guillaume Gardet 30 Nov '15

30 Nov '15

Hi, Sorry for cross post (-arm and -buildservice) but not sure who should fix this problem. Some ARM v7 workers are broken. They start to boot and then fail. Thus, lots of packages go to building state but return quickly to scheduled state. armbuild numbers 13, 16, 17, 18 and 19 are failing workers. armbuild15 does not seem to be ok but it seems to be a slightly different bug. Guillaume -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 20

[opensuse-buildservice] osb build icecream and qemu-binfmt
by Matwey V. Kornilov 28 Nov '15

28 Nov '15

Hello, I am running icecream installation which works well. Is the following supposed to work? osc build --clean --alternative-project openSUSE:Factory:ARM qemu armv7l --icecream=4 I have x86_64 environments everywhere, so I suppose I need somehow supply ICECC_VERSION with cross backend. Or it won't use cross? Or it won't work at all? -- 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] 'kvm_rng_device' is not a valid device model name
by Dinar Valeev 28 Nov '15

28 Nov '15

Hi, We have Power workers failing constantly with 'kvm_rng_device' is not a valid device model name, this is a result of part of qemu command: -object rng-random,filename=/dev/hwrng,id=rng0 -device kv m_rng_device,rng=rng0 I wonder why $kvm_rng_device [1] is not expanded here? [1] https://github.com/openSUSE/obs-build/blob/master/build-vm-kvm#L196 Dinar, -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] files become part of a package, although not in the filelist
by scalpel4k 26 Nov '15

26 Nov '15

Hi, I have the feeling that something weird is going on. It's about some build output that can be found here: https://build.opensuse.org/package/live_build_log/home:scalpel4k/cross-arm-… The thing is, I'm trying to map files into different sub packages with the help of filelists. But, at the end of the build the rpm linter is complaining that identical files exist in 2 different packages. However, when I look at the contents of the respective filelists I cannot find any duplicates in there. If you look, for istance, at the filelist_newlib (find echo "=== NEWLIB FILES ===" in the output) there are absolutely no files with .*nano.* or any duplicates in there. Yet, the linter tells a different story. Can someone be so kind and have a look at the output and help me understand what I'm doing wrong? thx Michi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Publish broken?
by Guillaume Gardet 26 Nov '15

26 Nov '15

Hi, on my home project (home:Guillaume_G:branches:Application:Geo) packages are not published. Is there anything wrong on OBS setup? Guillaume -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 9

[opensuse-buildservice] Is there a way to preserve checkin_count and build_count moving to a new server?
by Joshua Plautz 24 Nov '15

24 Nov '15

We've got a locally installed OBS instance a would like to switch over to using nosharedtrees=1 which the documentation says only works on a new installation (which would be nice to do regardless to get rid of accumulated cruft from this install originating with 1.x) Is there any good way to preserve the existing checkin_count/build_count values from the current server when re-importing everything on the new one so the new RPMs don't suddenly look older? Thanks, Josh -- 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] product_flavor example
by Eric Jackson 24 Nov '15

24 Nov '15

Hello, I am attempting to build a vagrant box for Leap in OBS. I have an unresolvable dependency telling me to set the product_flavor(openSUSE) to openSUSE-release-mini, openSUSE-release-dvd or openSUSE-release-ftp. My project is home:swiftgist/leap-42.1_vagrant_box. I have no idea whether this is a project conf variable, kiwi setting or something else. Is there an example that I could follow? Thanks, Eric

2 1

[opensuse-buildservice] Set maximum number of processors in _constraints?
by Nathan Cutler 23 Nov '15

23 Nov '15

I see that I can set the minimum number of processors in _constraints, but I don't see how I could set the _maximum_ number of processors. Is this even possible? Background: the problem with Ceph builds running out of memory is due to {%_smp_mflags} expanding to -j16 on many of the OBS build workers (thanks to Tim Serong for debugging this). -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] x86_64 13.1 gfxboot-4.5.1-4.1.3 requires glibc-32bit...
by Felix Miata 20 Nov '15

20 Nov '15

...but not 13.2's gfxboot, nor the currently installed 13.1 gfxboot-4.5.1-3.15. Is this an expected difference? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] SUSE:SLE-12:Update: unresolvable: nothing provides ceph = 0.80.8-2.3 needed by ceph-devel
by Jörg Steffens 19 Nov '15

19 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 ... 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)bareos.com Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz, M. v. Wieringen -- 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 problem with 32-bit version of VirtualBox
by Larry Finger 18 Nov '15

18 Nov '15

I have recently taken on the duties of maintainer for the VirtualBox code in openSUSE. Mostly things are going OK, but I have run into a problem that I have not been able to solve. I am doing a version bump of VB to 5.0.10. Both 32- and 64-bit versions build without problems using local "osc build" commands. When I commit the changes, the 64-bit builds are successful, but there is a failure for 32 bits. The last few lines in the build failure message from OBS Notification are as follows: ===================================== [29821s] qemu: terminating on signal 15 from pid 29812 Job seems to be stuck here, killed. (after 28800 seconds of inactivity) [29821s] ### WATCHDOG MARKER END ### [29821s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [29821s] or the build host has a kernel or hardware problem... ===================================== The line indicating what component was building is [ 1012s] kBuild: Compiling VirtualBox - /home/abuild/rpmbuild/BUILD/VirtualBox-5.0.10/src/VBox/Frontends/VirtualBox/src/runtime/UIDnDHandler.cpp => /home/abuild/rpmbuild/BUILD/VirtualBox-5.0.10/out/linux.x86/release/obj/VirtualBox/src/runtime/UIDnDHandler.o There is nothing special about file UIDnDHandler.cpp. I would appreciate any help in solving this problem. Thanks, Larry -- 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] Installation step on ScientificLinux_7
by Christof Hanke 18 Nov '15

18 Nov '15

Hi OBS admins, just wanted to note that something is fishy with the workers and 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 the packages are 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

2 5

[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

[opensuse-buildservice] OBS only building one half of my KIWI images
by Stefan Seyfried 10 Nov '15

10 Nov '15

Hi, I am running obs 2.6.6 Trying to build a kiwi image. The config has <preferences> <type ... installiso="true" installpxe="true" image="oem> which works fine with plain KIWI (it creates both an .install.iso and a .tar.xz for pxe-deployment) But when building the image in OBS, only an ISO is produced. If I edit the config and remove installiso=true, then it builds the .tar.xz I need both. I know I can work around this by creating two kiwi configs and linking the package, but the question is if this behaviour is "working as intended" or if it is a bug. Best regards, 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

1 1

[opensuse-buildservice] api.opensuse.org down since ~1h ?
by Thomas Bechtold 10 Nov '15

10 Nov '15

Hi, see $subject Cheers, Tom -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Open Build Service (OBS) 2.6.7 released
by Christian Bruckmayer 09 Nov '15

09 Nov '15

OBS 2.6.7 released ================== This release is fixing in first place two XSS security issue. The leak exists in the webui search and on the project site which can be misused to steal passwords or to gain access to projects. Furthermore we fixed several minor bugs (see the release notes). Please note that we upgraded passenger to version 5.0.15. OBS 2.5 is also affected, but not yet fixed. OBS 2.4 and before are not affected. Updaters from any OBS 2.6 release can just ugrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. OBS update are available from the following projects: https://build.opensuse.org/project/show/OBS:Server:2.6 The appliance can be downloaded from http://openbuildservice.org/download Details from the Release Notes of 2.6.7: ======================================== Feature backports: ================== * none Changes: ======== * [backend] compability support with Download-on-Demand definitions from OBS 2.7 Bugfixes: ========= * [webui] drop hardcoded opensuse email adress and link * [webui] fix XSS attack vector via User.realname (bnc#950932) * [webui] fix XSS attack vector via Projec.title (bnc#950932) * [webui] add spec & changes file code highlighting * [webui] fix saving files with code highlights (e.g. .js, .kiwi) * [webui] fix order of packages/projects for the 'Involved Projects' table on the user home page -- 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] Fedora 23 interconnect error
by Dmitry Kolin 09 Nov '15

09 Nov '15

Hello, I'm using standalone OBS instance to build my packages, everything works fine! But recently I added Fedora 23 repository, which now displays "broken" status. >From logs I found the following error message: 2015-11-07 06:25:48 [27857]: POST /notify/REPO_PUBLISH_STATEproject=myproject&repo=Fedora_23&state=publishing2015-11-07 06:25:48 [27858]: GET /getprojpack?withrepos&expandedrepos&withsrcmd5nopackages&project=myproject&repository=Fedora_23 fetching remote project data for openSUSE.org:Fedora:23 127.0.0.1: interconnect error: unknown element: download Is it a known issue? Maybe I could help you with debugging? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Fedora 23 treats empty debugfiles.list as an error
by Fred Kiefer 09 Nov '15

09 Nov '15

Hi, it looks like the Fedora 23 repository has some differences to the rest of the repositories I am building against. There missing debug files in a project get reported as an error and building stops: error: Empty %files file /home/abuild/rpmbuild/BUILD/gnustep-make-2.6.7/debugfiles.list On all other repositories this only gets reported as a warning. Some background, the gnustep-make package (https://build.opensuse.org/package/show/X11:GNUstep/gnustep-make) is actually a noarch package, but we cannot build it as such, as this also provides the folder structure for the rest of the GNUstep packages and here we either build up a folder hierarchy in /usr/lib or in /usr/lib64 depending on the architecture. This means we have a package that is not flagged as "noarch" but it doesn't include actual executables and for that reason no debug information files. This never caused any problems until I added Fedora 23 support this week. Is there a way to work around this (eg not to create the debug package?) or would it be possible to bring the behaviour of Fedora 23 in line with the rest of the repositories? Cheers, Fred -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] The repository setup is broken, build or publish not possible
by Lorenz 08 Nov '15

08 Nov '15

Hi there, one of my home-projects, home:lorenz:CAM, shows big red exclamation marks with The repository setup is broken, build or publish not possible as tooltips. I have no idea what is wrong or how to fix it. What exactly constitues "the repository setup"? I tried removing the affected repos, without effect. Also, when I add a new repo (like "openSUSE_Leap_42.1"), it ends up in the same state. What can I do? Kind regards, Lorenz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] releases without release?
by Stefan Seyfried 08 Nov '15

08 Nov '15

Hi all, is it intentional, that OBS:Server:2.6 gets new releases everyday without an updated changelog or even version number? I think it is really bad practice to just update the tarball: Index: open-build-service-2.6.7.tar.xz =================================================================== Binary files open-build-service-2.6.7.tar.xz (revision 31) and open-build-service-2.6.7.tar.xz (revision 32) differ If you need to do so, please at least include the git commit of the latest commit in the tarball somewhere (the package changelog would be a suitable place). In case you don't know how to do that: ask the SUSE kernel guys, they obviously do :-P Best regards, 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

2 2

[opensuse-buildservice] tar_scm service seemingly not fetching latest src
by Karl W Schulz 04 Nov '15

04 Nov '15

Hello fine obs folks, I have a standalone obs server and a number of packages using _service files that use “tar_scm” + “extract_file” + “recompress” services to fetch their inputs. I have been unable to put my finger on the condition that leads to this, but periodically I encounter situations where the latest SCM changes are not included, even after a rebuild is forced with “osc service remoterun”. This can be easily confirmed by examining the files presented in obs UI (and the final build rpms) vs the committed files in git. I have seen this now when interfacing with both external repositories (github) and internal repositories. When I am fortunate enough to detect that obs is building from older src versions, the “fix” I have stumbled upon is to make a noop change to the package _service file (I generally just append a newline). Then, after a commit, the latest contents will be ingested. I detect this fairly infrequently, but it just happened again and the noop change to _service file resolved it. Obviously it’s disconcerting to think other builds might be using older SCM contents and I was wondering if folks might have debug suggestions the next time it happens? The current issue was observed running obs 2.6.4 on opensuse 13.2. Thanks, Karl-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Purchase part via Postal Order?
by Malcolm 02 Nov '15

02 Nov '15

Hi I'm after a 'silver' top case trackpad cable for an A1181, but can I purchase if I send you a postal order for; SKU: GS72402 @ $6.75 Postage to: Cleveland Mississippi 38732 @ $2.74 Total: $9.49 If so, please confirm and will send shipping details and postal order today. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) Mac OS X Lion | Release: 10.7.5 | Darwin Kernel Version 11.4.2 up 4 days, 1:46, 4 users, load averages: 0.18 0.26 0.25 CPU Intel® Core 2 Duo T7300 @ 2.0GHz | GPU Intel® GMA X3100 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] pesign on SLE_11_SP4 broken ?
by Christof Hanke 01 Nov '15

01 Nov '15

Hi OBS-admins, it seems that the pesign step on SLES 11 SP 4 is somewhat broken. I have a branch-project https://build.opensuse.org/package/show/home:hauky:branches:filesystems/ope… which I use to test changes before pushing them onto https://build.opensuse.org/package/show/filesystems/openafs16 In the branch-project, the build fails for x86_64 with [ 236s] RPMLINT report: [ 236s] =============== [ 247s] Traceback (most recent call last): [ 247s] File "rpmlint.py", line 312, in <module> [ 247s] File "rpmlint.py", line 101, in main [ 247s] File "rpmlint.py", line 185, in runChecks [ 247s] File "SpecCheck.py", line 184, in check [ 247s] File "Pkg.py", line 167, in readlines [ 247s] IOError: [Errno 2] No such file or directory: '/tmp/pesign- repackage-1.0-72.1.src.rpm.4587/pesign-repackage.spec' [ 247s] 13 packages and 0 specfiles checked; 0 errors, 21 warnings. Same error for the arch i586 : [ 709s] RPMLINT report: [ 709s] =============== [ 732s] Traceback (most recent call last): [ 732s] File "rpmlint.py", line 312, in <module> [ 732s] File "rpmlint.py", line 101, in main [ 732s] File "rpmlint.py", line 185, in runChecks [ 732s] File "SpecCheck.py", line 184, in check [ 732s] File "Pkg.py", line 167, in readlines [ 732s] IOError: [Errno 2] No such file or directory: '/tmp/pesign- repackage-1.0-72.1.src.rpm.5087/pesign-repackage.spec' [ 732s] 14 packages and 0 specfiles checked; 0 errors, 24 warnings. [ 732s] When pushing the changes to filesystems/openafs16, even SLE_11_SP4 builds without errors. I have seen this before, but only on this package. Many thanks, 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] buildlog lacks info about diskspace
by Olaf Hering 01 Nov '15

01 Nov '15

The buildlog of a package which failed due to ENOSPC has no info how much diskspace was actually available. This makes it cumbersome to create a _constraints file. How much diskspace has a VM? The docs do not list default values: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_… Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3