openSUSE Build Service October 2013

buildservice@lists.opensuse.org

53 participants
48 discussions

Re: [opensuse-buildservice] Stalled submit requests

by Matwey V. Kornilov

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released

by Adrian Schröter

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 years

[opensuse-buildservice] RedHat 7 rpms signed with OBS signer do not install

by Jeff_Glanz＠Dell.com

Greetings: When using the OBS signing service, we observe errors during rpm installation in Redhat 7 x86_64 builds, related to keys in the rpm headers. For example, after we build and sign the perl-Authen-NTLM rpm, we see this in a downstream project that attempts to install it: installing perl-Authen-NTLM-1.02-1.3 error: .init_b_cache/perl-Authen-NTLM.rpm: rpmReadSignature failed: sigh load: BAD Research on rpmReadSignature errors reveals rpm header corruption as the root cause. >From https://bugzilla.redhat.com/show_bug.cgi?id=822255, detailing rpm read errors: Those mono packages have a slightly malformed signature header, which rpm prior to the recent security fixes didn't notice. The exact issue is that the signature header of those packages contain alignment for data types which are not supposed to be aligned, causing the expected vs calculated size to mismatch. Is there an OpenSuse Build service fix available (or planned) for the signer service? If not, is there a workaround available that allows us to turn off signing for selected projects and Operating system configurations? Thanks. Jeff Glanz Dell | PG Release Engineering Team office + 1 512 724 9509 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 3 months

[opensuse-buildservice] mini-howto: LDAP / proxy_auth_mode / Header rewrite

by Andreas Herrmann

Hi there, finally I setup proxy_mode with Apache Header Rewrite and .htaccess against ldap. I want to share the solution: 1. Add a Header-rewrite to /etc/apache/vhost.d/obs.conf: <VirtualHost *:444> ... RewriteEngine On RewriteCond %{LA-U:REMOTE_USER} (.+) RewriteRule . - [E=RU:%1] RequestHeader set X-username "%{RU}e" env=RU ... </VirtualHost> 2. Write your own .htaccess File to authenticate against your LDAP or whatever. The file should be located in /srv/www/obs/api/public/.htaccess For LDAP you need to enable Apache modules: a2enmod ldap a2enmod authnz_ldap 3. Now you can enable proxy_auth_mode in /srv/www/obs/api/config/options.yml: proxy_auth_mode: :on Some other Hints: You should not enable proxy_auth_mode in /srv/www/obs/webui/config/options.yml because the webui is redirecting by frontend_host and frontend_port to the API on Port 444 Problems: - In proxy_auth mode you are not able to create no users! Undo step 1-3, restart Apache and login local Admin to create the users. Password doesn't matter after switching back to proxy_auth_mode because the LDAP passwords are used. Any hint's? - I wasn't able to setup native ldap_mode. Maybe a combination problem with ldap_mode/proxy_auth_mode/frontend_ldap_mode(webui). Looking at tcpdump, the OBS is sending ping reqeust to the ldap server. Our server doesn't respond to ping request but is open on 387/tcp /srv/www/obs/api/app/models/user.rb: line 1335: ping = system("ping -c 1 #{server} >/dev/null 2>/dev/null") Changeing the line to "ping = system("ping -c 1 127.0.0.1 >/dev/null 2>/dev/null")" doesn't help. tcpdump isn't seeing any traffic to the ldap server. Next I'll try ldap on localhost and reconnect through socat. Any comments? -- Andreas Herrmann Heinlein Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 45 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

7 years, 3 months

[opensuse-buildservice] building xz requires xz

by Brian K. White

Come on, building xz requires xz ? I used to build xz on a bunch of old targets so that OTHER packages that required xz would find it, but now they all fail because the Base:build/xz I branched from changed to use xz-<version>.tar.xz as it's source file. xz itself cannot sanely buildrequires xz! (wasn't any explicit buildrequires either, just an assumption that tar would handle a .tar.xz, because the failure was only in the build logs "tar: file does not appear to be a tar archive", not a requires/buildrequires resolver message.) -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 3 months

[opensuse-buildservice] stuck builds

by Brian K. White

How can I abort and restart a hung build if the web interface nor osc abortbuild works? https://build.opensuse.org/package/live_build_log/home:aljex/python-pyzmq/o… ...has been hung some hours. $ osc abortbuild home\:aljex python-pyzmq openSUSE_11.4 i586 ok $ osc rebuild home\:aljex python-pyzmq openSUSE_11.4 i586 ok $ Didn't really change anything that I can see. The abortbuild command did take 10 or so solid seconds before it says "ok" I'm unclear from the output of "osc help abortbuild" if it's even intended to operate on a local or remote build. -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 3 months

[opensuse-buildservice] WEBUI+API = ♥

by Henne Vogelsang

Hey, as Coolo "announced" the week before last in his mail about his hackweek project we're about to marry the WEBUI with the API. Adrian, Ancor, Coolo and me just had a meeting about how we go about to push forward with this unholy communion. Here are the results, but first let me explain how we came to the decision to do this: ## What's wrong? Over time the initial design decision to make the WEBUI just another API client has proven to be a huge burden for WEBUI development. Especially because it separates the WEBUI from the API database where nearly all the OBS data is stored/referenced. This separation not only introduces another layer in between (activexml) with all the overhead such a layer brings in terms of network, parsing, rendering etc. this separation also forces us to replicate a lot of the cool (database) abstraction a framework such as Ruby on Rails brings. Additionally it raises the hurdle for new (RoR) developers to contribute as they need to learn all the inner workings of this setup and it hinders the adoption of new (RoR) tools and best practices as it's so different. In the last couple of months we explored to minimize the problem by having a special WEBUI route in the API that only serves/receives data specially crafted for/by the WEBUI. This already helped a lot but is still not enough in our opinion. This is why we are going to eliminate this separation ## What we are going to do about it? Obviously we're getting rid of the separation to expose the API database to the WEBUI and ultimately converting everything to the "frontend" (name not chosen yet..) an RoR app that serves the XML API and the HTML views. In order to get there we agreed to do the following three sprints: ### Affiance - Bind what belongs together. 1. Merge Coolos hackweek progress into master (coolo) 2. Document what changes for OBS admins and hackers (henne, adrian) * Especially where all the config options are now & where they could be before. * The new structure of the app, how to hack on and how to test it. 3. Deploy master to build-test.opensuse.org and pound on it. 4. Make a milestone release 5. Inform the OBS admins we know about the change, ask them to help (adrian, henne) ### Marriage - Conflate what belongs together. 1. Organize a test coverage sprint so we can be sure that nothing breaks when we merge. 2. Re-factor all WEBUI controllers to use API models 3. Get rid of all the WEBUI models, moving things we need into the API models. 4. Setup a standardized authorization system 5. Merge WEBUI/API login ### Honeymoon - Enjoy together. 1. Come up with a new layout for the HTML views. One that's using an mobile first front-end framework (most likely getbootstrap.com) and a design pattern library (most likely pattern-lab.info) 2. Get rid of the sub-domains (build.o.o, api.o.o) for the reference server and maybe even version the API (something like /api/v1/about) 3. Who knows what? The sky is the limit. You can find the progress of these sprints online in this task list: https://github.com/openSUSE/open-build-service/issues/450 Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 4 months

[opensuse-buildservice] Object not found!

by doiggl＠velocitynet.com.au

Hello, When i click on "Go to download repository" on page [1] it shows following error [2] Will it be fixed ? Thanks Glenn [1] https://build.opensuse.org/package/binaries/openSUSE:13.1/mariadb?repositor… [2] http://download.opensuse.org/repositories/openSUSE:/13.1/standard Object not found! The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again. If you think this is a server error, please contact the webmaster. Error 404 download.opensuse.org Sat Oct 26 06:53:58 2013 Apache/2.2.12 (Linux/SUSE) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 4 months

[opensuse-buildservice] Two patches for osc: API URLs with pathname and TLS SNI.

by Oleg Girko

Hello everybody! I'm sending two patches to osc which implement the following useful features. 1. Support for API URLs with pathname. Currently osc supports API URLs without path only, like https://api.example.com (if there is pathname, it's just ignored). With this change API URLS with path, like https://example.com/api are supported correctly. This is useful for those who can't have OBS api, webui and main site on different domains and buy separate X.509 certificates for them, or just can't afford to have separate IP addresses for them (please note that currently osc doesn't support TLS SNI). You may say that OBS API doesn't work correctly if installed with non-root path. But I took care about that already. I'll prepare and send a patch little bit later. 2. Support for TLS SNI (if M2Crypto supports it). Currently osc can't access API URLs which share the same IP address with other SSL-enabled sites, complaining about certificate not matching hostname. This change solves this problem by instructing M2Crypto.SSL.Connection to send the desired hostname to https server using TLS SNI extension, thus allowing the server to present the right certificate and choose the right virtual site. This is useful for those who can't afford to have a separate IP address for OBS API. For TLS SNI to work correctly, M2Crypto should be patched: https://bugzilla.osafoundation.org/show_bug.cgi?id=13073 For unpatched M2Crypto osc degrades to operation without TLS SNI. I've tested these changes with my OBS server, which has API installed on a virtual HTTPS server with non-root path. Patches are attached to this message. Please reply with cc to me, I'm not subscribed to opensuse-buildservice mailing list. Best regards, -- Oleg Girko, http://www.infoserver.lv/~ol/

7 years, 4 months

Re: [opensuse-buildservice] libraries to be added to build environment for xUbunbu 12.x

by Dmitriy Perlow

Hello. No universe packages. Rebuild them at your project. ______________ Dmitriy Perlow via SE J10i ---- Original message ---- From: wobremer <wobremer(a)t-online.de> Sent: ‎25-Oct‎-2013 18:23 To: opensuse-buildservice(a)opensuse.org Subject: [opensuse-buildservice] libraries to be added to build environment for xUbunbu 12.x Hello Ladies and Gentlemen, when I try to build my project for xUbuntu 12.10 or 12.04 I get the following error messages: unresolvable: nothing provides libboost-system-dev, nothing provides libboost-filesystem-dev, nothing provides libboost-thread-dev As the build for xUbuntu 13.10 and 13.04 are working fine, I think, that the libraries are missing in the build environment for the 12.x versions. Can those libraries added? With kind regards Wellenreiter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service October 2013