openSUSE Build Service November 2013

buildservice@lists.opensuse.org

50 participants
55 discussions

[opensuse-buildservice] private OBS and certificates

by Axel Theilmann

moin, here's something i stumbled upon when setting up a private OBS instance. SSL-connections failed because the CA-certificates were not present on the system. after installing ca-certificates-mozilla it worked. maybe it would be useful to add that package as a dependency to the OBS RPMs. the only other thing i encountered (when setting up OBS according to this description https://github.com/openSUSE/open-build-service/blob/master/dist/README.SETUP) was that i had to edit the setting in frontend_host in /srv/www/obs/webui/config/options.yml (instead of FRONTEND_HOST in production.rb as documented in section 5.1). I didnt try adding that setting in production.rb, though... apart from that the setup went pretty smooth... tt, axel -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 2 months

[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, 2 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, 2 months

[opensuse-buildservice] image builds for hours to reach size 279494M (+) and doesn't end

by Ralf Lang

Hi, last night I triggered this build: https://build.opensuse.org/package/live_build_log/isv:B1-Systems:Horde5:rol… It still runs and the image has grown (according to log) to 279494M by now, still growing in 10M chunks. I did not intend this and I do not see why it does this or when it eventually would end. There is a cyclic mentioning of a Perl error: Use of uninitialized value $pdev in concatenation (.) or string at /usr/share/kiwi/modules/KIWIBoot.pm line 5907. I know I could simply stop it but that wouldn't make me none the wiser what's missing and if it will eventually be finished by the server. Any pointers how to fix this appreciated. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

7 years, 2 months

[opensuse-buildservice] Automatic SRs from devel to factory?

by Greg Freemyer

I'm confused by SR#205883 <https://build.opensuse.org/request/show/205883> Is there an automated process that runs around pushing devel packages into factory? Or does Coolo run around looking for slackers (like me) and pushes their packages for them? == background I had pushed a package (libwrc) to it's devel project a couple weeks ago. It broke another package in the devel project that was at the same rev level as factory. I fixed the other package and pushed it to factory 4 or 5 days ago. <https://build.opensuse.org/request/show/205738> Today I went to push the first package (libwrc), and to my surprise it was pushed 3 days ago! <https://build.opensuse.org/request/show/205883> Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 2 months

[opensuse-buildservice] %make_install in prjconfig

by Brian K. White

I want to build tmux for many older versions of suse. The current .spec from factory uses %{make_install} OS versions before 11.2 do not have that macro. I got it working by making this change to the .spec from the current version 1.8 in factory: - %{?make_install} + %{?make_install} %{!?make_install:%%{__make} install DESTDIR=%{buildroot}} I have had other packages with the same problem, and I would like my branched copies of packages to stay clean of differences as possible so they keep tracking the devel packages instead of going stale or breaking when the devel package changes. And a lot of package maintainers are not interested in accepting SR's that add support for old targets like that, they would rather have the .spec file be small and pretty than functional. So now I want to move the fix from all the individual .spec files to my prjconfig, so the spec files can stay as upstream has them. I put this in my prjconfig %{!?make_install: %define make_install %{__make} install DESTDIR=%{buildroot}} And restored the .spec file to just assuming %{make_install} will always exist. It didn't work. OS 11.2 and up built fine as normal, 11.1 and below failed as normal. What did I do wrong? Can I actually centralize this this way? Is there a problem with trying to resolve %buildroot maybe? Can I escape the % in buildroot to cause it to be expanded later or something? Thanks -- 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, 2 months

[opensuse-buildservice] how to enable selinux

by Ruediger Meier

Hi, is it possible to enable selinux for the build machine? I want "make check" to also test selinux features. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 2 months

[opensuse-buildservice] often recurring problem with project/repository "bad config"

by Stefan Botter

Hi all, recently I quite often see certein repo's in projects in the state "The repository setup is broken, build not possible.". In the scheduler_* log I see for instance ==== vdrdevel/openSUSE_12.3: bad config (openSUSE.org:openSUSE:12.3:Update) ==== I see that on private build instances, which are using the OBS-repos using interconnect. Henne suggested on IRC, that this may be caused by network (connection) problems. I see that on three OBS instances, one of them uses a completely different path to build.openSUSE.org, yet I see the problems appearing around the same time (just some minutes apart). That hints, that - if this is caused by connection problems - the cause origins at the opensuse-end of the connection. I do not think that this is actually caused by "network" problems, but is caused by the load put on b.o.o. As this can be seen as an expected problem, I would like to have a solution for this problem. To overcome the blockade I usually restart the scheduler. I have seen the symptom disappearing by doing a submitrequest also, but I have several projects with packages linked to b.o.o and just having local patches, so I rather seldom submit packages. The scheduler should clear this "bad config" condition by retrying to retrieve the repo config after a certain time. My first question: does my observation make sense? How can I debug that behavior, or how can I be of help? The second: if my observation is correct, can there be a mechanism, which "self-heals" the system? If I can supply additional information, I am happy to supply everything needed. Thank you for your time, Stefan -- Stefan Botter Network Manager Jacobs University Bremen gGmbH Campus Ring 1 | 28759 Bremen | Germany Commercial registry: Amtsgericht Bremen, HRB 18117 President & Geschäftsführer: Prof. Dr. Heinz-Otto Peitgen Provost & Geschäftsführerin: Prof. Dr.-Ing. Katja Windt Chair Board of Governors: Prof. Dr. Karin Lochte

7 years, 2 months

[opensuse-buildservice] DNS problem on OBS

by Archie Cobbs

FYI... Bad Gateway! The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /project/monitor. Reason: DNS lookup failure for: build-opensuse.suse.de If you think this is a server error, please contact the webmaster. Error 502 build.opensuse.org Wed Nov 6 20:51:48 2013 Apache/2.2.12 (Linux/SUSE) $ host build-opensuse.suse.de Host build-opensuse.suse.de not found: 3(NXDOMAIN) -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 2 months

[opensuse-buildservice] f19: ruby: Command not found

by Christoph Dwertmann

Hi! My package has ‘ruby’ as build dependency, and it gets installed on the OBS f19 VM, but then ruby is not found. This works on f17 and f18, but is broken on f19 only. [...] [ 130s] [272/313] installing ruby-2.0.0.195-8.fc19 [...] [ 164s] checking for ruby... no [ 164s] configure: WARNING: could not find the ruby interpreter [ 164s] configure: WARNING: No Ruby>=1.8.7 found; some tests will be skipped [...] [ 174s] make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/oml2-2.11.0rc/ruby' [ 174s] make[2]: Nothing to be done for `all'. [ 174s] make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/oml2-2.11.0rc/ruby' [ 174s] Making all in server [ 174s] make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/oml2-2.11.0rc/server' [ 174s] VER=`echo 2.11.0rc | /bin/sed "s/.*+oml//;s/-dirty//;s/$[0-9]\{1,\}\(\.[0-9]\{1,\}$\{1,2\}\).*/\1/;s/\./, /g"`; \ [ 174s] /bin/sed -e 's|@bindir[@]|/usr/bin|g' \ [ 174s] -e "/app\.path/s/oml2-server/`echo 'oml2' | /bin/sed 's&^&&'`/" \ [ 174s] -e "s/app\.version.*/app.version($VER)/" \ [ 174s] oml2-server.rb.in > oml2-server.rb [ 174s] ruby ../ruby/oml2-scaffold --oml oml2-server.rb [ 174s] make[2]: ruby: Command not found [ 174s] make[2]: *** [oml2-server_oml.h] Error 127 [ 174s] make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/oml2-2.11.0rc/server' [ 174s] make[1]: *** [all-recursive] Error 1 [ 174s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/oml2-2.11.0rc' [ 174s] make: *** [all] Error 2 [ 174s] error: Bad exit status from /var/tmp/rpm-tmp.aEZFdA (%build) [ 174s] [ 174s] [ 174s] RPM build errors: [ 174s] Bad exit status from /var/tmp/rpm-tmp.aEZFdA (%build) [ 175s] Powering off. [ 175s] [ 145.215197] Power down. Cheers, Christoph ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2013