October 2014 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] conflict in linked foo.changes
by Brian K. White 24 Oct '14

24 Oct '14

https://build.opensuse.org/package/show/home:aljex:branches:Base:System/bash I link branched a package, and made a tiny change to .spec . Everything was fine, it built, it didn't show the errors it shows now. Then I wanted to SR the change back upstream. To do that I need to add an entry in .changes Editing the .changes, whether directly in the web ui or through osc vc & ci, results in these errors and all builds saying broken as it shows now. Why can I edit .spec without errors and not .changes? How can I work on a linked package like this where I want the package to be linked and still exist after the SR is accepted? (The SR has been accepted btw, so really, the upstream files should match mine now anyways.) Am I supposed to delete and rebranch the package every time? Or is there some osc procedure I should to to resolve this? -- bkw -- 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] 20-files-present-and-referenced parse errors
by Olaf Hering 23 Oct '14

23 Oct '14

/usr/lib/obs/service/source_validators/20-files-present-and-referenced fails if the spec file starts with a macro instead of some rpm tag. %something Version: 1.2.3 vs. Version 1.2.3 %something The first variant fails, the second succeeds. Please fix the tool. https://build.opensuse.org/request/show/258106 Olaf -- 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] Maintenance
by Stephan Kulow 22 Oct '14

22 Oct '14

Hi, In case you wonder: the current maintenance is due to updating to current master - which we haven't done for over 2 months, so there are a lot of changes to be taken into account. We should be up soon though and your packages continue to build, it's just the API. Greetings, Stephan -- 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] build.opensuse.org ppc64 servers down?
by Fritz Elfert 22 Oct '14

22 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At https://build.opensuse.org/monitor, two of the three traffic lights for ppc64 show *red* and job-states in my project don't seem to change for about several hours now. Cheers -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRFX/sACgkQboM4mAMyprBRGwCdG/CD/DcsB2TKKerbJIkHk+ki 67oAn12gxpvUqDz0U9ZDMMhTUhusR6Em =He2y -----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 1

[opensuse-buildservice] osc on Mac OSX: No CA certificates found
by Johannes Kastl 20 Oct '14

20 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, has anyone tried to use osc on Mac OSX lately? I wanted to be able to try some things on the OBS while I am working on OSX, but I can't get osc to work: > Traceback (most recent call last): File > "../OSC_Buildservice/osc/osc-wrapper.py", line 26, in <module> r = > babysitter.run(osccli) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/babysitter.py", line > 61, in run return prg.main(argv) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/cmdln.py", line 343, in > main return self.cmd(args) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/cmdln.py", line 366, in > cmd retval = self.onecmd(argv) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/cmdln.py", line 484, in > onecmd return self._dispatch_cmd(handler, argv) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/cmdln.py", line 1214, > in _dispatch_cmd return handler(argv[0], opts, *args) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/commandline.py", line > 4070, in do_checkout show_project_meta(apiurl, project) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/core.py", line 3296, in > show_project_meta f = http_GET(url) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/core.py", line 3198, in > http_GET def http_GET(*args, **kwargs): return > http_request('GET', *args, **kwargs) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/core.py", line 3142, in > http_request install_opener(conf._build_opener(url)) File > "/Users/Shared/XXX/OSC_Buildservice/osc/osc/conf.py", line 516, in > _build_opener raise Exception('No CA certificates found') > Exception: No CA certificates found My guess would be that it somehow does not find the right place, where OSX or macports keeps its certificates. I commented on github, if it's easier to keep track there: https://github.com/openSUSE/osc/issues/34 Regards, Johannes - -- Working with Unix is like wrestling a worthy opponent. Working with windows is like attacking a small whining child who is carrying a .38. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlRCvYEACgkQzi3gQ/xETbIpEgCdFTWutxcxHc5Edl+xxa9B9R6U 5RQAn3ek77M/luzi7fI1HS1uBDRhVNS3 =0Fpy -----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] One Click Install
by Frank Schreiner 20 Oct '14

20 Oct '14

Hi all, I try to figure out, how to add additional repositories to .ymp files created automatically using OBS patterns. Any Hints ? cu Frank -- 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] Endless build loop?
by Fritz Elfert 20 Oct '14

20 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can one of the OBS admins please have a look at the following Project: https://build.opensuse.org/project/show/home:ods:ppc64 There seems to happen something very strange there. OBS builds the same packages over and over again and they never show up as finished or success?! For example: libtool has just been built, but now it is shown blocked again?! why? Thanks -Fritz PS: Another question: Is it possible to disable the automatic replacement of the Release somehow? It breaks the texlive package in the above Project - which was imported from RHEL7 (CentOS7) The spec file contains multiple different Release: tags for various sub-packages which apparently can not be handled correctly by the automatic Release tag replacement. I tried the following in prjconf: Release: %%{?tl_release:%%{tl_release}}%%{?!tl_release:<CI_CNT>%%{?dist}} without success. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlREND0ACgkQboM4mAMyprDJTACgglCvv/r9MSOho6DcZwPVm4R1 nZQAoIwmjXSmSaaFDWfEE45FIGjBg3Gz =QRhZ -----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] rpc timeout configurable
by Frank Schreiner 18 Oct '14

18 Oct '14

Hi all, we are running a private instance of obs. After upgrading 2.4 to 2.5 I ran into timing issue between obs-worker and rep_server. I always got an "rpc timeout" on the worker. I figured out, that 3 seconds timeout are to short, maybe because of running obs server on a virtual machine. So I wrote a patch, to make rpc timeout configurable, which can be found here: https://build.opensuse.org/package/view_file/home:M0ses:branches:OBS:Server… I would be glad, if this patch would be included upstream or if I could get some feedback, how I could get it upstream. cu Frank -- 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] How to link to projects on remote OBS instances?
by Eric MSP Veith 16 Oct '14

16 Oct '14

Dear list, I've a software that I need to build privately, so I've (successfully) set up and linked it to https://api.opensuse.org/public. The software I'd like to package uses libraries from projects on build.opensuse.org, namely the "Application:Geo" and "KDE:Qt53" projects, so I figure I need a way to link my own project to the other two mentioned in order to get the dependencies right. This is my first endevour with OBS, so I'm unsure how to do this. Google found me a Wiki page on project linking [0], and so I added the following two lines to my project metaconfig: <link project="Application:Geo"/> <link project="KDE:Qt53"/> Still, libraries such as "libgeos-devel", "libgdal-devel" or "libQt5Core- devel" that are part of the two remote projects. Surely I'm missing something here. Could somebody point out what exactly? Any help would be really appreciated! Thanks alot in advance. --- Eric [0] https://en.opensuse.org/openSUSE:Build_Service_Concept_project_linking

4 5

[opensuse-buildservice] ScientificLinux 7 added
by Adrian Schröter 15 Oct '14

15 Oct '14

JFYI, ScientificLinux 7 got added to build.opensuse.org instance. And both (6 & 7) distributions got added to the simple list of build targets in webui. Note: SL does promise to be binary compatible with RHEL 7 afaik. So, it might be an option for you to build against SL instead of RHEL if you lack packages as build dependencies. -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, 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

1 0