February 2017 - openSUSE Build Service

[opensuse-buildservice] How to maintain user accounts on own obs instance
by Christian 20 Feb '17

20 Feb '17

Hi, read through http://openbuildservice.org/help/manuals but it is not very helpful. trying to 'enable' a new registered account ? How can I do that ? thank you -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- http://www.sc24.de - Sportbekleidung ----------------------------------------------------

2 6

[opensuse-buildservice] OBS 2.7: Packages are unresolvable 'Have choice for i586' or 'Nothing provides'
by Till Dörges 17 Feb '17

17 Feb '17

Hello all, I just upgraded a private OBS instance from 2.6 to 2.7. The openSUSE 13.1 update repository was a local repository under 2.6 and was converted to a download on demand repository for 2.7. I have configured a project, roughly like so: --- snip --- <project name="P"> <title>T</title> [...] <repository name="openSUSE_13.1"> <path project="openSUSE.org:13.1" repository="standard"/> <path project="openSUSE.org:13.1:Update" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> --- snap --- Unfortunately I get 'unresolvable' for all i586 packages. The tool tip shows something like "Have choice for libelf.so.1 needed bei rpm: libelf1 libelf1-32-bit, ...." x86_64 is building fine. If I change the order of the <path> entries the state still stays 'unresolvable' for all i586 packages. But the tool tips change to "Nothing provides libpopt.so.0()(64bit) needed by rpm-build, ...." Again, x86_64 is building fine. The repositories openSUSE.org:13.1 and openSUSE.org:13.1:Update look like this: --- snip --- <project name="openSUSE.org:13.1"> <title>openSUSE 13.1 (lokal)</title> <description>D</description> <person userid="Admin" role="bugowner"/> <person userid="Admin" role="maintainer"/> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> <project name="openSUSE.org:13.1:Update" kind="maintenance_release"> <title>openSUSE 13.1 Updates (DoD)</title> <description>D</description> <link project="openSUSE.org:13.1"/> <person userid="Admin" role="bugowner"/> <person userid="Admin" role="maintainer"/> <publish> <disable/> </publish> <repository name="standard"> <download arch="x86_64" url="http://internal.host/opensuse/live/update/13.1/" repotype="rpmmd"/> <download arch="i586" url="http://internal.host/opensuse/live/update/13.1/" repotype="rpmmd"/> <arch>x86_64</arch> <arch>i586</arch> </repository> </project> --- snap --- Obviously something is wrong but I have no idea what and where to debug next. Any hint would be greatly appreciated! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- 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] CentOS-7 repository
by Adrian Schröter 17 Feb '17

17 Feb '17

JFYI, the CentOS-7 repository got changed upstream. I did turn the repository therefore into a download-on-demand repository. Things like Qt5 exists now. However, I have not found a way how to validated the repository information. The rpmmd meta data is not signed with GPG, neither exists an authorative https server delivering the data. So these packages are not validated atm :/ It would be great if anyone has a hint for me how I can validate the repository meta data. thanks 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 3

[opensuse-buildservice] JFYI, build.o.o is switching to createrepo_c
by Adrian Schröter 17 Feb '17

17 Feb '17

JFYI, We are switching to use createrepo_c (and modifyrepo_c) for published repositories. Nobody should notice a difference, but just in case you are wondering about some change :) 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 1

[opensuse-buildservice] Questions about build workers (with some answers)
by Greg Ward 17 Feb '17

17 Feb '17

Hi all, after my question the other day about builds in state "broken", I realized I have a bunch of questions about build workers. Background: I'm working on a private OBS instance that was setup by a colleague. He's moving on, so I don't want to go running to him every time I have an OBS question. Instead, I'm digging into the docs and the config files and the source code, and running here when I get stumped. Here are the questions I have come up with. (Incidentally, I have already answered some of these myself by reading source code. I have not found any answers in the manuals or with Google.) Q1) What defines a build worker? A config file? Something in the database? It just shows up, announces itself, and starts building? (A: from reading /etc/init.d/obsworker, it looks like a variety of config files in /etc, mostly /etc/sysconfig/obs-server, define the build workers *on this host*.) Q2) I have 4 build workers defined on my OBS server: are they interchangeable, or do they all build for different targets? (A: from /etc/init.d/obsworker plus config files, it looks very much like they are interchangeable.) Q3) How do I know which build targets (operating systems, architectures, etc.) a given build worker -- or perhaps I should say, all the build workers on a certain host -- can handle? IOW, why are my build workers capable of building for Oracle Linux 7 and CentOS 7, but not Scientific Linux 6.7? They are all on an openSUSE host, the OBS appliance. Q4) How do I find out if I have any build workers that can handle a given target, e.g. Scientific Linux 6.7? Q5) Can I run i586 builds on an x86_64 machine? Or do I need a 32-bit build host? (I only care about i586 and x86_64, so I should not need anything fancier than a chroot for builds.) Q6) How do I add a new build worker that can handle builds for Scientific Linux 6.7? Q7) How do I add new build workers on a separate host? Does that host have to be running openSUSE, or will the worker run on any sufficiently compatible OS? (Like, say, CentOS 7.) (A: oops, I just discovered the Admin Guide. It was not very well hidden at all. I guess I'm just blind. I'm hoping I will find the answer in there.) Thanks! Greg -- 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] What to do about "broken" state
by Greg Ward 16 Feb '17

16 Feb '17

Hi all, I'm working on setting up a private OBS to replace an old version that has been running for many years. I need to build packages for *at least* CentOS 7 and Scientific Linux 6.x (x = 7, 8, whatever is latest). I successfully added a project "CentOS:C7" as a binary import. We already have local mirrors of all upstream OS packages, so IMHO there's no point in using download-on-demand. Anyways, after I added the CentOS:C7 project and configured my home:gward project to build for CentOS 7 using that project, packages in my project were in state "broken" for a little while. I poked around trying to figure things out, but did not succeed. After a while, I noticed that the packages had built -- apparently *something* cleared the "broken" state, but I have no idea what. So I carried on and added a project ScientificLinux:SL6.7. To the best of my knowledge and memory, I repeated the same steps that I did to create CentOS:C7. And it half worked: packages in home:gward now want to build for SL 6.7, i586 and x86_64. But it half didn't work: those packages have been stuck in state "broken" for ~30 min now, and they do not appear to be magically getting unbroken. Any idea what is going on here? How do I investigate when a package is "broken"? How do I unbreak it? Thanks! Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6

[opensuse-buildservice] Starting gpg agent
by Mathias Homann 15 Feb '17

15 Feb '17

Hi, what do i need in a build to be able to start a gpg-agent during build? or in other words, why does home:lemmy04:branches:KDE:Frameworks5/gpgme build ok for Factory, and fails for Leap 42.2? In the build log i only see "failed to start gpg agent" for Leap 42.2, but not why it failed. Cheers MH -- 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] stale kconfigwidgets in Backports_SLE-12-SP2
by Olaf Hering 14 Feb '17

14 Feb '17

It seems openSUSE:Maintenance:6338 contains a bunch of KDE packages for Backports:SP2. But they are appearently not in the openSUSE:Backports:.. hierarchy. Still, a package that has kconfigwidgets-devel in BuildRequires in a project that has openSUSE:Backports:SLE-12-SP2 as base project does not build: unresolvable: nothing provides kwidgetsaddons-devel >= 5.26 needed by kconfigwidgets-devel nothing provides kauth-devel >= 5.26 needed by kconfigwidgets-devel With 'osc ls -lbv' I found no such package beside the update to 5.20 in openSUSE:Backports:SLE-12-SP1/kconfigwidgets.5214. How do I find where it is stored? Olaf

2 3

[opensuse-buildservice] missing error reporting in osc ls
by Olaf Hering 13 Feb '17

13 Feb '17

Is the lack of error reporting a bug in osc or OBS? I expect return code 1. # obs ls -u openSUSE:Factory osc _link ; echo $? file '_link' does not exist 0 Olaf

2 1

[opensuse-buildservice] Problem building packages relying on ncurses
by Olav Reinert 11 Feb '17

11 Feb '17

Hi, I'm the maintainer of the BATS package (Bash Automated Testing System): https://build.opensuse.org/package/show/devel:tools/bats Lately, the build on OBS has started to fail for Factory-like distros. The build errors can be reproduced when building locally using "osc build". The problem is that the "tput" command (from the ncurses-utils package) doesn't work properly within the chroot'ed build environment used by OBS. BATS relies on running "tput cols" to figure out the console width. When building the package for Leap 42.2, for example, it works fine, but building for a Factory-like target fails with the error tput: terminal attributes: No such device or address I'm not an expert on how the terminal system works, so I can't tell if this a bug in the chroot'ed build environment, or if I just need to add extra BuildRequires declarations to make it work (if so, which ones?). I hope someone out there can enlighten me on this issue? Regards, Olav -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0