October 2015 - openSUSE Build Service - openSUSE Mailing Lists

[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] 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] 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

[opensuse-buildservice] sudo inside worker
by Matwey V. Kornilov 31 Oct '15

31 Oct '15

Hello, What is the recommended way to obtain root privileges when package is being build? A unit-test in bedup (btrfs deduplication tool) package needs to mount image using loop device and this requires sudo. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 7