openSUSE Build Service December 2015

buildservice@lists.opensuse.org

35 participants
37 discussions

[opensuse-buildservice] Question about logic in an example spec file?

by jimssupp＠rushpost.com

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

5 years

[opensuse-buildservice] Need to know morla1 cpu type.

by Matwey V. Kornilov

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

5 years

[opensuse-buildservice] Repositories for SLE_12 (with or without _GA)?

by Johannes Kastl

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

5 years

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

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

5 years

[opensuse-buildservice] OBS product builders

by Dinar Valeev

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

5 years

[opensuse-buildservice] Building against RHEL: What is it good for, if CentOS builds work and RHEL is missing al devel packages...

by Johannes Kastl

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

5 years

[opensuse-buildservice] Stumped on build service for Leap 42.1

by Jim Henderson

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

5 years, 1 month

[opensuse-buildservice] Creating multiple maintenance projects

by Scott Bahling

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

5 years, 1 month

[opensuse-buildservice] Ghost package

by trcs＠gmx.com

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

5 years, 1 month

[opensuse-buildservice] Building lxc for CentOS with python34

by Johannes Kastl

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

5 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service December 2015