December 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

[opensuse-buildservice] merge changes from devel project
by Olaf Hering 27 Apr '16

27 Apr '16

What is the prefered way to merge changes in the devel project? osc bco pkg cd home:user:devel:prj/pkg osc up -u edit pkg.spec osc vc osc commit now devel:prj/pkg gets changes by someone else, and home:user:devel:prj/pkg goes into state 'broken': broken: conflict in file pkg.spec Even if the changes are merged manually the pkg remains broken. I think its required to just update the _link to point to HEAD. Is there a command to do just that? osc repairlink says: BuildService API error: source link is not broken 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

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] RPMLINT report. No errors, but failed
by Kyrill Detinov 21 Feb '16

21 Feb '16

Hello. A package failed to build for Tumbleweed a week or two ago. From a log: [ 286s] RPMLINT report: [ 286s] =============== [ 290s] outwiker.noarch: W: zero-length /usr/share/outwiker/help/help_en/Page Types/Wiki Page/Wiki Commands/childlist command/page 2/__page.text [ 290s] 2 packages and 0 specfiles checked; 0 errors, 24 warnings. [ 290s] Traceback (most recent call last): [ 290s] File "rpmlint.py", line 385, in <module> [ 290s] File "rpmlint.py", line 196, in main [ 290s] File "Filter.py", line 131, in printAllReasons [ 290s] File "Filter.py", line 40, in __print [ 290s] File "/usr/lib/python2.7/codecs.py", line 357, in write [ 290s] data, consumed = self.encode(object, self.errors) [ 290s] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 65: ordinal not in range(128) [ 290s] [ 290s] [ 290s] build27 failed "build outwiker.spec" at Sat Dec 19 14:14:47 UTC 2015. [ 290s] [ 290s] ### WATCHDOG MARKER START ### [ 293s] [ 251.249718] sysrq: SysRq : Power Off [ 294s] [ 251.376272] reboot: Power down [ 296s] ### WATCHDOG MARKER END ### [ 296s] [ 296s] build27 failed "build outwiker.spec" at Sat Dec 19 14:14:53 UTC 2015. [ 296s] The latest succeeded built is: Build Time: 2015-11-29 10:31:08 +0100 The package is: https://build.opensuse.org/package/show/home:Lazy_Kent/outwiker -- WBR Kyrill

3 7

[opensuse-buildservice] force reevaluation of prjconf
by Olaf Hering 08 Feb '16

08 Feb '16

What command can be used, beside 'osc commit', to trigger a reevaluation of prjconf? If a pkg is in state "unresolvable" after commit, and the prjconf gets changed to solve the dependency no rebuild happens. A local 'osc build' works, but 'osc wipebinaries -r <repo>' or 'osc rebuild -f' will still use the previous state of prjconf. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 8

[opensuse-buildservice] combined use of _aggregate and _service in a package?
by Karl W. Schulz 08 Jan '16

08 Jan '16

Hello All, I am aware of the nice capability to copy binary build results from one project to another using the _aggregate feature. The examples I have seen thus far seem to always have the same number of repos available in the source project as are present in the destination project (although the names may be different). If that is not the case (say the destination project is introducing a new repo that wasn't present in the source project), is it possible to construct a package configuration using _aggregate to retain the binary result for the repo that existed previously, and _service to build from source for the new repository? Thanks for any tips, Karl-- 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 token use case
by Matwey V. Kornilov 08 Jan '16

08 Jan '16

Hello, I see the following when run osc token: <entry id="4" string="A" project="project" package="package"/> <entry id="133" string="B"/> As far as I understand, the first token is package specific and can be used to run /trigger/runservice?package=package&project=project Do I understand right that the second token B can be used instead of user credentials to run any command? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Question about logic in an example spec file?
by jimssupp＠rushpost.com 04 Jan '16

04 Jan '16

I'm getting started writing a spec file for use on OBS. I'm looking at some examples to help figure stuff out. In one pkg's spec file there's this piece of code %if 0%{?suse_version} >= 1210 || 0%{?fedora_version} (1) BuildRequires: systemd %{?systemd_requires} %define have_systemd 1 %else %if 0%{?suse_version} <= 1220 (2) PreReq: %fillup_prereq PreReq: %insserv_prereq %endif %if 0%{?suse_version} > 1220 (3) PreReq: %fillup_prereq Requires: /usr/sbin/service %endif %endif ------ The way I read that if the Suse version >= 1210, the (1) 'if' clause will exec, and (2) & (3) will be skipped. But (3) requires Suse version > 1220 to execute. So there's NO WAY for the (3) clause to ever be reached, right? Why's it in there? Jim -- 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] Need to know morla1 cpu type.
by Matwey V. Kornilov 28 Dec '15

28 Dec '15

Hello, I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type. >From buildlog I see: [ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015. Could I have /proc/cpuinfo of morla1? It may be really useful. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 11

[opensuse-buildservice] Repositories for SLE_12 (with or without _GA)?
by Johannes Kastl 22 Dec '15

22 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, today I added a subproject and checked the same repositories (in the webui) as I had in another one. Then I aggregated some packages from the old one into the new one, to avoid building twice. And received some "broken" packages for SLE_12. Apparently, when checking the SLE_12 repository in the webui now, one does no longer end up with a repository called SLE_12_GA, but rather one with SLE_12. So the packages can't be aggregated and are thus broken. Or rather, as I explicitly disable building these package for SLE_12_GA, they are not disabled for SLE_12, and are thus aggregated, but are not available and thus broken. Funny, eh? Diff: < <repository name="SLE_12_GA"> - --- > <repository name="SLE_12"> Question: WTF? ;-) For SLE11 there are multiple repositories, one for each service pack. For SLE12 there is only one checkbox. Is this changing at the moment, as SP1 has been released? How to avoid this in the future? What do I have to build for to always get the latest SLE_12? Seems a waste of resources to build for both... Old: home:ojkastl_buildservice:LXC_Vanilla_HEAD_git_snapshot New: home:ojkastl_buildservice:LXC_Vanilla_stable-2.0_git_snapshot Thanks in advance! Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZ4/68ACgkQzi3gQ/xETbJ97wCglRqAdd+XlYWrJIWaWpEBv7Bc bPYAnixDLzYUmQDRicwXRSD/LfLiKZ15 =voFe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

Re: [opensuse-buildservice] Building against RHEL: What is it good for, if CentOS builds work and RHEL is missing al devel packages...
by Johannes Kastl 19 Dec '15

19 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 19.12.15 schrieb Stanislav Baiduzhyi: > Yup, got the same problem. The issue is, lots of devel packages > for RHEL are coming in Supplementary or Optional subscription > channels (because they have lower level of support), so you need > actual RHEL subscription to use them . That was what I found out, but I wanted to have a confirmation if this is still the case. If no, they could be added. If no, I question the existence of RHEL on the OBS... ;-) > So I ended up building for CentOS only, if RHEL users will not be > satisfied - they are free to rebuild it on their own. I guess > that you can add those subscriptions channel when hosting your > own instance of OBS and having your own RHEL subscription, but > never actually tried that. That could actually be a valid point for the existence of RHEL on OBS. That make it easier to build for RHEL on a private OBS instance. But otherwise, if you need to import the Optional/Supplementary packages, it would not be to hard to import the RHEL base packages, I guess. So the question remains, what is RHEL build target good for? Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZ1SxMACgkQzi3gQ/xETbJa0QCfX+YcumD/LyNlanKwADsf46Zz kHkAoItxCgBhgJCTndsGH8el1nCmWC77 =cs1B -----END PGP SIGNATURE----- -- 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 product builders
by Dinar Valeev 19 Dec '15

19 Dec '15

Hi, It seems something is wrong with product builders. PowerPC ftp and dvds are stuck for 8 hours fetching cache, then simply killed by watchdog due to timeout. -- 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] Building against RHEL: What is it good for, if CentOS builds work and RHEL is missing al devel packages...
by Johannes Kastl 18 Dec '15

18 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, as I was trying around with builds for CentOS, I was naive enough to think building for RHEL should work out of the box, as CentOS and RHEL are (nearly) the same. Boy, was I wrong... ;-) I found an older mail, saying that the RHEL devel packages can not be imported on OBS. It seems this is still the case, which leads to lots and lots of missing dependencies for the builds, which build fine for CentOS. So, my question is: What is the RHEL build target good for? If the CentOS builds work out of the box on a RHEL machine, it seems like a waste of build time and space. On the other hand, if I have to build all needed devel packages (and the dependencies of these packages and the dependencies of the dependencies...) just to achieve the same results as with CentOS, it seems rather pointless to import RHEL at all. What important point am I missing? Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZ0Vn4ACgkQzi3gQ/xETbIX4wCfaVDwTDb5wsHtI8WlqYZgxWSl 7NYAnixCKYFhdTpkENTg7LaKaMuj2rBC =stlZ -----END PGP SIGNATURE----- -- 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] Stumped on build service for Leap 42.1
by Jim Henderson 15 Dec '15

15 Dec '15

I've gone in and tried to configure my home: project to build for Leap 42.1, but it stays stuck in a disabled state, even though the builds for the one project (pan-git) have the repos enabled. It's been a while since I set this up for 13.2, but that build works - can someone jog my memory as to what I'm missing to get the build to work for 42.1? Thanks, Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- 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] Creating multiple maintenance projects
by Scott Bahling 14 Dec '15

14 Dec '15

I have been able to set up a maintenance project using the OBS:MaintenanceProject attribute, and use that project with update projects using the OBS:Maintained attribute. That creates one project where all maintenance requests end up. How do I create more than one maintenance project? -Scott -- 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] 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] Building lxc for CentOS with python34
by Johannes Kastl 11 Dec '15

11 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, I am trying to build the lxc package (1.0.8 atm) for CentOS7. To get a usable output of lxc-ls, I wanted to enable building with python3, which works fine with the openSUSE version. https://build.opensuse.org/project/monitor/home:ojkastl_buildservice:L XC_Vanilla_stable-1.0 As CentOS7 only has python3 in EPEL, I created a package that pulls in the original src.rpm from EPEL. After some tweaking of the prjconf, the python34 package builds. It is called python34 on CentOS, and the version from epel installs /usr/bin/python34, not /usr/bin/python3. /usr/bin/python is still the 2.7 version. https://build.opensuse.org/project/monitor/home:ojkastl_buildservice:C entOS_Zeug_Testing:python34-EPEL Aggregating the package to my lxc project, tweaking spec and prjconf and voila, the package is built. Only, I can't install it on CentOS, as the package somehow has a dependency for /usr/bin/python3: Error: Package: lxc-1.0.8-14.2.x86_64 (home_ojkastl_buildservice_LXC_Vanilla_stable-1.0) Requires: /usr/bin/python3 In the spec file for lxc, I set a Requires for python34 or python(abi) = 3.4 or similar, but always the same. And I would have thought that using the original srpm for building should results in correct dependecies, if they are somehow automagically added. Question: Any hints? Is this a problem with building EPEL SRPMs on OBS? Error in my spec file? Wrong prjconf? Any ideas? Thanks in advance. Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZoetgACgkQzi3gQ/xETbJ+BQCeIdZbLOcDE0e0JZYdD0FIAY2a 1x0AnjvJQHATuiYHeYhhCsjalKYn90pv =dkGq -----END PGP SIGNATURE----- -- 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] openSUSE Build Service - Education/itext
by opensuse.lietuviu.kalba 11 Dec '15

11 Dec '15

Hi, Please, can someone with JAVA building skills fix or update itext package? This is extra dependency of TuxGuitar. OBS source: https://build.opensuse.org/package/show?project=Education&package=itext File not found: /home/abuild/rpmbuild/BUILDROOT/itext-1.4-0.14.1.x86_64/usr/share/maven-fragments Seems to be explained in https://lists.fedoraproject.org/pipermail/java-devel/2014-June/005269.html But its better to update; see: Latest source: https://github.com/itext/itextpdf/releases/latest Maybe Fedora sources can help: http://pkgs.fedoraproject.org/cgit/itext.git/tree/ -- Regards -- 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] fix choice for avfilter in Factory
by Olaf Hering 10 Dec '15

10 Dec '15

Please update the Prefer: tags in openSUSE:Factory for ffmpeg/libav: have choice for pkgconfig(libavfilter): libavfilter-devel libavfilter-libav-devel It should be like this: Prefer: libavcodec-devel Prefer: libavdevice-devel Prefer: libavfilter-devel Prefer: libavformat-devel Prefer: libavutil-devel Prefer: libpostproc-devel Prefer: libswresample-devel Prefer: libswscale-devel Not sure if the existing -..-libav-devel is better. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Ghost packages in my home repo
by Dave Plater 10 Dec '15

10 Dec '15

Hi, I've somehow ended up with ghost packages in my home:plater repo. When I find them via the status screen I can make them visible by osc meta pkg -e and I usually remove something from the comment lines and save then the package becomes visible again. I accidentally deleted my home:plater and then undeleted it and ended up with a host of ghost packages, prior to that I had an rpm branch floating around causing havoc with builds until I worked out the osc meta pkg -e method and was able to delete. What I would really like to do is wipe all of the packages and repositories in home:plater without affecting the sub projects below it. Is this possible . Thanks Dave -- 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] Issue with CASA 64bit rpm generation
by Rajasekhar Nukala 09 Dec '15

09 Dec '15

Hi Opensuse Build Service, I am Rajasekhar Nukala from Build Team, ZENworks(SMG). Before migrating to OBS, we were using "mbuild(10.160.0.107)" for building our CASA code to generate rpms. After moving to OBS, we are able to generate all the rpms except "CASA-32bit-1.7.1885-1.x86_64.rpm". We haven't changed any spec file. Could you please let us know how it was getting generated with mbuild and not with OBS. PFA the spec and obs link for reference https://build.opensuse.org/package/show/home:nrajasekhar/CASA With Regards, Rajasekhar

3 4

[opensuse-buildservice] Debian6.0 in OBS appliance
by Holger Freyther 05 Dec '15

05 Dec '15

Hi, I'm running a OBS appliance and still have the need to build Debian6.0 packages. By itself Debiab6.0 is supported[1] until February 2016 and I wonder if there is a way for me to build packages for it? What is the easiest option? kind regards holger [1] https://wiki.debian.org/LTS -- 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] mono-data-postgresql version mismatch
by Jacek Rużyczka 05 Dec '15

05 Dec '15

Hello, as I seem to have found a bug in the Npgsql driver supplied with mono-data-postgresql ver. 3.12.1-6.9 for openSuSE 13.2 / x86_64, I would like to update to a more recent version. rpm.pbone.net suggests me mono-data-4.0.2.4-2.1.x86_64.rpm (supplied by MihailJP) for mono-data, but the latest available version of mono-data-postgresql is 3.12.1-6.9, which is the one I currently have had on my PC since 2015-05-01, and MihailJP's latest version of mono-data-postgresql is 3.10.0-149.1. Is there some hope there will be a 4.0.2 version of mono-data-postgresql built into an RPM someday? Thank you. Kind regards Jacek Rużyczka -- 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] Building python34 for CentOS7: "make: dtrace: Command not found"
by Johannes Kastl 04 Dec '15

04 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, to be able to build lxc for CentOS7 including python3 (for a usable lxc-ls output), I tried to build python34 (imported CentOS source rpm via _service) on OBS: I got all the required dependencies, but the build fails with the following: > make: dtrace: Command not found Build log: > https://build.opensuse.org/package/live_build_log/home:ojkastl_build service:CentOS_Zeug/python34/CentOS_7/x86_64 Any > ideas? That was not what I was expecting, I was hoping it would work out of the box, once I got the depencies sorted out... Thanks in advance, Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZfU6kACgkQzi3gQ/xETbL1dwCgn54alLkV1su/G42NxymrQz+M 97oAoJsOiBczyBdvT6qTSFqxIzoZduzH =vQ7o -----END PGP SIGNATURE----- -- 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] OBS Webinterface seems to take hours?
by Johannes Kastl 04 Dec '15

04 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, is it just me, or is the OBS webinterface taking hours until I get the build results displayed? Creating packages works, after some seconds they show up in the project overview. But some of my build jobs are "finished" for about an hour now. No matter if I use "osc buildresults" or the webinterface. And it took some twenty minutes after creating them before the even showed up at all... Dropout from todays maintenance? Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlZgmFIACgkQzi3gQ/xETbLfOwCfTRWzf/O9V7G1jXwF4ZTTVe+d O2cAn0HroPjJz7hqX7AoLL2Zyl5kjVjD =8JKV -----END PGP SIGNATURE----- -- 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] 2 days and counting to create a Leap Download repo for my home project?
by Greg Freemyer 03 Dec '15

03 Dec '15

Is something wrong? I added Leap as a repo for my home project 2 days ago and still no download directory to publish packages to: http://download.opensuse.org/repositories/home:/gregfreemyer:/Tools-for-for… Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- 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] Flag to specify that project needs more RAM to build
by Stanislav Baiduzhyi 03 Dec '15

03 Dec '15

Is it possible to notify via some special flag that project needs larger amount of RAM to be built? What I see is that OBS assigns 2 types of qemu-kvm for the build, with 750 and with 6000 MB RAM. I know that NetBeans needs at least 2000, so it wastes lots of resources to try and fail on 750MB VM, while build on 6000 machine can be already finished at the same time. -- 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] some downtime tomorrow
by Adrian Schröter 03 Dec '15

03 Dec '15

JFYI, we will use our regular maintenance window tomorrow for replacing three of the binary backend servers. This will mean that we will be a bit longer down then usual. bye adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] No package 'ncurses' found
by Rusmir Duško 02 Dec '15

02 Dec '15

Hello I have in aop.spec BuildRequires: ncurses-devel https://build.opensuse.org/package/show/home:nemysis/aop All good build for openSUSE_13.2, openSUSE_Factory and openSUSE_Tumbleweed And not find ncurses for older Versions. How to fix this? -- Best regards, nemysis / Rusmir Duško <nemysis(a)openSUSE.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] OBS-server repo for opensuse 42.1?
by Martin Weber 02 Dec '15

02 Dec '15

Hi, is there a reason why http://download.opensuse.org/repositories/OBS:/Server:/2.6/ has obs-server rpm for openSUSE 13.1+13.2, but none for openSUSE 42.1? In contrast, http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_42.1/ has lots of obs-service-* rpms, but no obs-server rpm. Confused, Martin -- | Martin Weber | Razorcat Development GmbH | Witzlebenplatz 4 fon: +49-(30)-536 357 46 | 14057 Berlin fax: +49-(30)-536 357 60 | |-------------------------------------------- | Geschäftsführer: Michael Wittner | Sitz der Gesellschaft: Berlin | Amtsgericht: Berlin, HRB 65326 -- 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] 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

Re: [opensuse-buildservice] Re: pw3270 and ooRexx
by Erico Mendonca 01 Dec '15

01 Dec '15

Ah, disregard that. Greg’s answer has the link to the proper procedure. Thanks! Em [DATE], "[NAME]" <[ADDRESS]> escreveu: >I shall open a bug for each one in bugzilla then? > > > > >Em [DATE], "[NAME]" <[ADDRESS]> escreveu: > >>Erico Mendonca <Erico.Mendonca(a)suse.com> writes: >> >>> However, the proper versions are there (and have been for quite a while), >>> in devel:languages:misc and on openSUSE:Factory. I see there is an older >>> version (ooRexx-4.1.3) in openSUSE:13.1 and openSUSE:13.2 for these >>> packages, but I don’t have access to update them. If I try to request >>> access as a maintainer for both, I’m informed that I should use >>> openSUSE:Factory or openSUSE:13.2:Update and openSUSE:13.1:Update. >> >>If you want to update a package in a released product you need to go >>through the maintenance process. >> >>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." >> >N��r��y隊Z)z{.��Wlz��qﮞ˛��m�)z{.��+�:?�{Zr�az�'z��j)h��Ǜ�)]��Ǿ� ޮ�^�ˬz�

1 0

[opensuse-buildservice] pw3270 and ooRexx
by Erico Mendonca 01 Dec '15

01 Dec '15

Hello all, The builds for the package X11:terminals:pw3270 stopped for SLE12, openSUSE 13.1 and openSUSE 13.2 because the BuildRequires for ooRexx-devel (also maintained by me) is not being found. However, the proper versions are there (and have been for quite a while), in devel:languages:misc and on openSUSE:Factory. I see there is an older version (ooRexx-4.1.3) in openSUSE:13.1 and openSUSE:13.2 for these packages, but I don’t have access to update them. If I try to request access as a maintainer for both, I’m informed that I should use openSUSE:Factory or openSUSE:13.2:Update and openSUSE:13.1:Update. If I try to request the maintainer role for openSUSE:13.2:Update and openSUSE:13.1:Update, I get a 404 error. The version in openSUSE:Factory is current, as I submitted it a while ago. If I try to submit from devel:languages:misc/ooRexx to either openSUSE:13.1:Update or openSUSE:13.2:Update, I get a “unable to submit” error, with no further details. I can submit to openSUSE:Factory normally. Any ideas?

3 3

[opensuse-buildservice] pw3270 and ooRexx
by Erico Mendonca 01 Dec '15

01 Dec '15

Hello all, The builds for the package X11:terminals:pw3270 stopped for SLE12, openSUSE 13.1 and openSUSE 13.2 because the BuildRequires for ooRexx-devel (also maintained by me) is not being found. However, the proper versions are there (and have been for quite a while), in devel:languages:misc and on openSUSE:Factory. I see there is an older version (ooRexx-4.1.3) in openSUSE:13.1 and openSUSE:13.2 for these packages, but I don’t have access to update them. If I try to request access as a maintainer for both, I’m informed that I should use openSUSE:Factory or openSUSE:13.2:Update and openSUSE:13.1:Update. If I try to request the maintainer role for openSUSE:13.2:Update and openSUSE:13.1:Update, I get a 404 error. The version in openSUSE:Factory is current, as I submitted it a while ago. If I try to submit from devel:languages:misc/ooRexx to either openSUSE:13.1:Update or openSUSE:13.2:Update, I get a “unable to submit” error, with no further details. I can submit to openSUSE:Factory normally. Any ideas? N��r��y隊Z)z{.��Wlz��qﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǜ�)]��Ǿ� ޮ�^�ˬz��

1 0