May 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Licenses
by Pavol Rusnak 07 Jun '11

07 Jun '11

Hi! I just saw the following OBS request from Ciaran: >> Correct syntax from http://spdx.org/licenses/ >> -License: BSD >> +License: BSD-3-Clause I noticed that there was licensing crossdistro summit at LinuxTag. Does that mean that all distributions agreed to use abbreviations from the mentioned document in their packages? (I recon we were using BSD3c for this particular license, also we use GPLv2+ while the document mentions GPL-2.0+). If yes, then it is really cool and you should do a blogpost about the results of the summit (which you should do anyway I guess ;-)). Also there should be a tool that fixes spec file entries in OBS automagically and we'll put the same replacement magic in our spec-cleaner ... Thanks for the clarification! -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Local installation usage problem - why perl package causes package to be blocked
by Tommi Rintala 31 May '11

31 May '11

Hi everybody! my question in short: Why buildserver blocks sometimes, package builds on some perl packages, even though they are available? And where should I look for source of these errors? Priority: low -- I just want to understand the OBS I have made a local installation of OBS on openSUSE 11.3 (x86_64), using rpm packages. (The versions of rpm's are shown below). There might be something wrong in my installation, but it has been running already several weeks without hickups and I have been able to create openSUSE and SLES packages without any problems [if spec files have been correct]. Yesterday after 'yast update' for some reason one of my packages was blocked, due to "perl-Log-Dispatch-FileRotate" -package. This was shown in web GUI. In this morning another blocker "perl-Log-Dispatch" appeared. Only clue to why this might happen is that my software requires "perl-Log-Log4perl". The perl-Log-Log4perl was assigned into spec file as "BuildRequires: perl-Log-Log4perl", since I was going to write some test cases for installation to test logging part of package. After removing this build-require -line, the compile went fine and was no more blocked. However, I was not able to find any error messages in log files... perhaps I didn't know what to look for. In the server (where OBS is running) there are installed the packages, so atleast the server it self can find the packages: perl-Log-Dispatch perl-Log-Dispatch-FileRotate perl-Log-Log4perl the project configuration is like this: 1. <project name="licmon2"> 2. <title>License Monitor</title> 3. <description/> 4. <person userid="Admin" role="maintainer"/> 5. <person userid="Admin" role="bugowner"/> 6. <person userid="t2r" role="maintainer"/> 7. <person userid="t2r" role="bugowner"/> 8. <useforbuild> 9. <disable repository="SLE_11"/> 10. </useforbuild> 11. <build> 12. <disable repository="SLE_11"/> 13. </build> 14. <publish> 15. <disable repository="SLE_11"/> 16. </publish> 17. <repository name="openSUSE_11.3"> 18. <path repository="openSUSE_11.3" project="openSUSE.org:devel:languages:perl"/> 19. <path repository="standard" project="openSUSE.org:openSUSE:11.3"/> 20. <arch>i586</arch> 21. <arch>x86_64</arch> 22. </repository> 23. </project> installed obs -packages: obs-api-2.1.11-2.1.x86_64 obs-common-2.1.0-1.1.x86_64 obsfs-0.1.git-1.1.x86_64 obs-productconverter-2.1.11-2.1.x86_64 obs-server-2.1.11-2.1.x86_64 obs-service-cpanspec-0.1-10.1.noarch obs-service-download_files-0.1-2.1.noarch obs-service-download_src_package-0.1-3.1.noarch obs-service-download_url-0.1-12.1.noarch obs-service-extract_file-0.1-6.1.noarch obs-service-recompress-0.1-7.1.noarch obs-service-set_version-0.1-4.1.noarch obs-service-tar_scm-0.2.1-3.1.noarch obs-service-verify_file-0.1-4.1.noarch obs-signd-2.1.2-1.1.x86_64 obs-source_service-2.1.11-2.1.x86_64 obs-utils-2.1.11-2.1.x86_64 obs-worker-2.1.11-2.1.noarch This happened during yast update, no error messages found at /var/log/zypper.log: <install> U_Ts_(5277)obs-service-cpanspec-0.1-10.1.noarch(download.opensuse.org-perl) <install> U_Ts_(16631)obs-api-2.1.11-2.1.x86_64(openSUSE:Tools) <install> U_Ts_(16636)obs-productconverter-2.1.11-2.1.x86_64(openSUSE:Tools) <install> U_Ts_(16639)obs-server-2.1.11-2.1.x86_64(openSUSE:Tools) <install> U_Ts_(16642)obs-service-download_files-0.1-2.1.noarch(openSUSE:Tools) <install> U_Ts_(16666)obs-source_service-2.1.11-2.1.x86_64(openSUSE:Tools) <install> U_Ts_(16668)obs-utils-2.1.11-2.1.x86_64(openSUSE:Tools) <install> U_Ts_(16669)obs-worker-2.1.11-2.1.noarch(openSUSE:Tools) <uninstall> I_TsU(39173)obs-api-2.1.10-1.4.x86_64(@System) <uninstall> I_TsU(39175)obs-productconverter-2.1.10-1.4.x86_64(@System) <uninstall> I_TsU(39176)obs-server-2.1.10-1.4.x86_64(@System) <uninstall> I_TsU(39177)obs-service-cpanspec-0.1-2.1.noarch(@System) <uninstall> I_TsU(39178)obs-service-download_files-0.1-1.1.noarch(@System) <uninstall> I_TsU(39187)obs-source_service-2.1.10-1.4.x86_64(@System) <uninstall> I_TsU(39188)obs-utils-2.1.10-1.4.x86_64(@System) <uninstall> I_TsU(39189)obs-worker-2.1.10-1.4.noarch(@System) So, where should I look for the causes for this blockage? What should I look for in the log files? Or is there something basically wrong with my project configuration? yours, Tommi Rintala -- WasaLab Oy, P.O.Box 365, FIN-65101 Vaasa t2r(a)wasalab.com, tel +358-44-767 7770 helpdesk(a)wasalab.com, tel +358-45-130 4000 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] OBS's Facebook Page
by Bryen M. Yunashko 30 May '11

30 May '11

Hi Folks, Anyone know who is the administrator for the OBS Page on Facebook? I'd like to help revive that page, but after talking to Adrian, it seems we don't know who administrates it. http://www.facebook.com/#!/buildservice Thanks! Bryen M Yunashko openSUSE Marketing Team -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

Re: [opensuse-buildservice] OBS, far more work then on Launchpad for Ubuntu
by Adrian Schröter 27 May '11

27 May '11

Am Thursday, 26. May 2011, 09:33:55 schrieb Claudio Freire: > On Thu, May 26, 2011 at 4:56 AM, Adrian Schröter <adrian(a)suse.de> wrote: > > And I lack the time to review all the packages. But if there are just a number of > > urgently needed packages, I can import just these. > > From my experience, sdl-dev, openal-dev, libbost-dev and friends are > usually missing on many debian-based distributions. > I frequently have to add them. > > In fact, in xUbuntu 11.04, I'm getting "nothing provides > libopenal-dev", even though it's supposed to be there according to > packages.ubuntu.com That are just universe packages. Since these are anyway a moving target, what about if you Debian/Ubuntu builder people found a project, let's say Debian:Support where you maintain such packages and build for all (needed) Debian and Ubuntu distros. So you can have a common pool for such packages and you do not rely on me personally. I would create such a project and hand over to you, if let's say at least three persons are willing to work on that. does this sound like a plan ? adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 14

[opensuse-buildservice] Elastic Build Service - provisioning workers flexibly to Amazon EC2
by Ville.Seppanen＠tieto.com 27 May '11

27 May '11

Hello, As my Master's Thesis project, I have been developing an elastic build service based on OBS. It is a private instance of OBS, with a simple service manager included. This service manager monitors the local build hosts and decides whether it should spawn more workers to an Infrastructure-as-a-Service provider to help out with the workload. I have been running a test environment, having one local build host with 3 workers and 0-15 build hosts in Amazon each running a single worker. The service manager runs as a script once every minute using cron. In practice, when builds are triggered, the service manager requests new machines in 1-2 minutes, depending how long it takes for the server to schedule the jobs. In total, it takes about 3-5 minutes for the build hosts to boot up in Amazon, open a VPN connection to our OBS network, start up workers and start building. Machines are launched into Amazon if there are jobs to be done in the queue and if there are no idle local workers. Idle Amazon workers are killed the next time they are about to be rebilled (Amazon bills you every full hour from instance launch time). This service manager script has been committed to the OBS repo: https://gitorious.org/opensuse/build-service/blobs/master/dist/elastic_buil… There is a catch however. The Amazon Machine Image (AMI) that I am using has been configured manually, meaning that IP addresses and other data the build host needs to connect to the server are specific to our setup, and thus cannot be shared. I have added to the script a really short summary of what you need to setup your own elastic build service, and plan to add more detailed instructions. The best solution would be to create a generic cloud worker appliance image with SUSE Studio that has all the needed packages (obs-worker, openvpn) installed. Then everyone could use the same machine image and the build hosts would be configured on boot time using Amazon's user_data (when requesting a new instance, it is possible to define arbitrary shell commands to run during boot). This is not production-ready. There is no persistent, shared cache in the cloud yet (could S3 be used or do we need to run a fileserver) and the build environment is not sandboxed into a virtual environment (OBS support for LXC needed). Please comment and share your ideas. Best Regards, Ville Seppänen Tieto Corporation -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] submitreq --supersede=SUPERSEDE
by Karl Eichwalder 27 May '11

27 May '11

I'm wondering how 'osc submitreq --supersede=SUPERSEDE' works (0.130.1). Does it actually require a parameter? If yes, should it be a to be superseded request id? If yes, this would be rather annoying for me. I just want to supersede a previous request unconditionally. Or shall I better use --yes in this case? -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] where are global build deps defined
by Ruediger Meier 26 May '11

26 May '11

Hi, Is there something like a global build dependency list used by all projects? I see buildinfo for every single project but is there a way to add a bdep to all? I am asking because I would like to file a feature request about supporting xz compression like bz2 for source tar balls without having "BuildRequires xz" in every spec file. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] static.opensuse.org caching broken
by Cristian Rodríguez 26 May '11

26 May '11

Hi: The server static.opensuse.org does not set proper expires/last-modified headers on CSS and Javascript files causing slowness in the web interface (always return code 200 and not 304 Not Modified) I suggest the person in charge to run a test on: http://pagespeed.googlelabs.com/ that will give hints and solutions to the problems. Cheers. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 8

Re: [opensuse-buildservice] OBS, far more work then on Launchpad for Ubuntu
by Adrian Schröter 26 May '11

26 May '11

Am Thursday, 26. May 2011, 13:52:54 schrieb Radoslav Dibarbora: > On 26.May.2011 13:35, Adrian Schröter wrote: > > Am Thursday, 26. May 2011, 12:45:45 schrieb peer: > >> On 05/26/2011 12:36 PM, Sascha Peilicke wrote: > >>> On Thursday 26 May 2011 12:25:23 peer wrote: > >>>> On 05/26/2011 11:18 AM, Claudio Freire wrote: > >>>>> On Thu, May 26, 2011 at 9:50 AM, Adrian Schröter<adrian(a)suse.de> wrote: > >>>>>> Since these are anyway a moving target, what about if you Debian/Ubuntu > >>>>>> builder people found a project, let's say Debian:Support where you > >>>>>> maintain such packages and build for all (needed) Debian and Ubuntu > >>>>>> distros. > >>>>>> > >>>>>> So you can have a common pool for such packages and you do not rely on > >>>>>> me personally. > >>>>>> > >>>>>> I would create such a project and hand over to you, if let's say at > >>>>>> least three persons are willing to work on that. > >>>>>> > >>>>>> does this sound like a plan ? > >>>>> Yep, that sounds perfect > >>>> Sounds like a unpractical and cumbersome solution to me. Maybe I am > >>>> missing something, but why not enable 'universe' (as an option) as default? > >>> Just as Adrian said, currently we're not allowed to host _all_ content that is > >>> in Ubuntu's universe/multiverse repositories, mainly due to license and patent > >>> issues. That's essentially the same reason why we're not hosting rpmfusion for > >>> Fedora. > >>> > >>> Until the OBS is hostet in a country where this doesn't matter we're bound to > >>> german law. > >> I understand that multiverse is a problem. But why universe, that is all > >> free software. > > The last time I checked it contained definitive some packages part of our black list > > (containg ffmpeg inside of the application and so on). > > > > ALso, it was a moving target. I will not import such a repo binary wise, because I would > > need permanently updating it. > Adrian, > > What about allowing the worker to download build requirements from > external sources? builds would not be reproducable. The value of OBS would not be given. > > Will it be also illegal if you will not provide problematic packages > just allow to build using them? since you would be also able to download them via api.o.o, yes. > This will also solve the problem with other distributions needs. I was > asking to add EPEL repositories few times but it ended in nowhere > probably for same reasons: > - legal problems > - need to maintain frequently changed binary repositories > > Regards > Rado -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] getbinarylist and Transfer-Encoding header
by Marcus Hüwe 26 May '11

26 May '11

Hi, there seems to be a problem with the getbinarylist call (view=cpio) and the "Transfer-Encoding" header (depending on the "length" of the request?). I just tried the following curl calls: curl -o out.cpio -v -sS \ "https://api.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/_rep… -e "print 'b'x3616")" and curl -o out.cpio -v -sS \ "https://api.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/_rep… -e "print 'b'x3617")" The response of the first request still includes the "Transfer-Encoding" header but the response of the second request has no "Transfer-Encoding" header. Now consider the following call: curl http://<local obs>/build/<remote project>/<repo>/<arch>/_repository?view=cpio&<long query> This leads to a "crash" in bs_srcserver (the ajax process dies because the response has neither a "Transfer-Encoding" nor a "Content-Length" header). Any ideas why the "Transfer-Encoding" header gets swallowed? Marcus Ps. is this the same bug to which a comment in "worker_getbinaries" refers? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3