October 2013 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] List All Projects: Application error 500
by Andreas Herrmann 18 Oct '13

18 Oct '13

Hi there, after updating OBS 2.4 (zypper ref; zypper up) I just get an application error 500, when I want to list all projects in the webui. 'osc list' still works ==> /srv/www/obs/api/log/production.log <== [INFO |# 3196] Processing by WebuiController#all_projects as XML [INFO |# 3196] iChain user extracted from header: adm_ahe [INFO |# 3196] Completed 500 Internal Server Error in 57ms [FATAL|# 3196] NoMethodError (undefined method `id' for nil:NilClass): app/controllers/webui_controller.rb:270:in `all_projects' config/initializers/wrap_parameters.rb:35:in `call' ==> /srv/www/obs/webui/log/production.log <== [FATAL|# 2680] ActiveXML::Transport::Error (#<Net::HTTPInternalServerError:0x000000059b46f0>): lib/activexml/transport.rb:461:in `handle_response' lib/activexml/transport.rb:400:in `http_do' app/models/api_details.rb:26:in `find' app/controllers/project_controller.rb:39:in `list' app/controllers/project_controller.rb:35:in `list_public' Any ideas? -- 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

2 5

[opensuse-buildservice] Open Build Service blog, 2013-42
by Nathan Cutler 18 Oct '13

18 Oct '13

Open Build Service blog, 2013-42 Here is a summary of activity on the opensuse-buildservice mailing list during week 42: * Ladislav Slezak announced his successful Hack Week project designed to speed up appliance builds in the Build Service by reducing the number of packages that are downloaded. See https://hackweek.suse.com/projects/143 * Fadi Kelajian asked about upgrading an existing OBS Server instance from 2.3 to 2.4 -- he would like to upgrade without losing existing data (projects, packages). Adrian advised him to read https://github.com/openSUSE/open-build-service/blob/master/dist/README.UPDA… and, of course, take a backup first. * Ruediger Meier expressed displeasure over multiple requests like https://build.opensuse.org/request/show/188119 to remove "deleted" repositories from projects. These requests got auto-accepted even before he returned from vacation. - Jan Engelhardt noted that certain types of requests are not delivered via email: https://bugzilla.novell.com/show_bug.cgi?id=739335 - Coolo responded that it's time to implement that email notification mechanism. - Adrian explained that, in this case, a "deleted" repository is one that got moved somewhere else. Such a configuration will never build until the path list of the "deleted" repository is fixed. * Andreas Baumann asked a question regarding a project failing to link to the Fedora_17 build target, to which Kanstantsin Shautsou noted that, since Fedora 17 is EOL, the problem will probably never get fixed. * Darin Perusich complained about a problem where, after doing a local build, he couldn't open a new Konsole window. He traced this to a permissions issue, where running "obs build openSUSE_12.3" caused the mount options of devpts to change. Marcus Meissner replied that, last week, he released a new build package that fixes the permissions for 12.2 and 12.3. * Boris Manojlovic complained that the OBS web UI is sluggish on slower links. He posted a Firebug analysis on: http://paste.opensuse.org/29484148 As ways to address the problem, he suggested: JavaScript "minification", CSS "minification", gzip/deflate encoding/content type, and Etag support. * Brian K. White expressed amazement that the 'xz' package "requires" itself to build. This is not an explicit BuildRequires, but just the fact that the build process assumes tar will handle a .tar.xz file. - Ruediger Meier noted that there are precedents for this: for example, gcc requires gcc, coreutils requires coreutils. - Michal Vyskocil posted a link to his Request 203465 on openSUSE Build Service: https://build.opensuse.org/request/show/203465 (which has since been accepted) - Adrian responded to Ruediger's comment by saying that bootstrapping is unavoidable in 'gcc' case, but should be avoided wherever possible. - Michal Vyskocil also noted that upstream provides tarballs compressed using other technologies than xz, like gzip and bzip2, and his request addresses the issue. * Guillermo Amat wrote about a bug that results in a "Failed to add project or repository: unable to walk on path" error when he tries to add an additional apth to his project's repository. Martin Koegler replied that it's probably due to a JavaScript implementation issue in some browsers, so perhaps switching to a different browser is in order. * Coolo posted an in-depth report about his Hack Week project, "Start the engine", designed to fix an internal problem with the OBS web UI http://lists.opensuse.org/opensuse-buildservice/2013-10/msg00086.html * Andreas Herrmann posted a mini-HOWTO for setting up proxy_mode with Apache Header Rewrite and .htaccess against LDAP http://lists.opensuse.org/opensuse-buildservice/2013-10/msg00099.html * Andreas Herrmann wrote about getting an error 500 when he tried to list all projects in the web UI, after upgdating OBS 2.4 Stefan Botter responded with his analysis of a similar problem he ran into after upgrading from 2.3 to 2.4: http://lists.opensuse.org/opensuse-buildservice/2013-09/msg00084.html Andreas replied that his update was within 2.4, so the issue might bite everyone doing "zypper ref; zypper up" -- 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] Installing OBS_Server on SLE11-SP3 using "zypper"
by Nathan Cutler 18 Oct '13

18 Oct '13

Hi. I'm trying to install the OBS_Server pattern on SLES11-SP3. Here is my repo file: czbs:/etc/zypp/repos.d # cat OBS_Server_2.4.repo [OBS_Server_2.4] name=OBS 2.4 Server (SLE_11_SP3) enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/repositories/OBS:/Server:/2.4/SLE_11_S… type=rpm-md gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/OBS:/Server:/2.4/SLE_11_SP… I do 'zypper ref' - OK. Then I do: # zypper in -t pattern OBS_Server Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides obs-api needed by pattern:OBS_Server-.noarch Solution 1: do not install pattern:OBS_Server-.noarch Solution 2: break pattern:OBS_Server-.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Any ideas where to go from here? Nathan -- 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] My hackweek project: start the engine
by Stephan Kulow 18 Oct '13

18 Oct '13

Hi, For years everyone having to touch the webui gets frustrated that he can't access the DB as good rails applications do. So we introduced new routes in the API to dump raw .json for things the webui needed and similiar nasty things that always meant having 2-3 places to change if you wanted to have a new feature in the webui. So Ancor and me did some research how to make the webui access the API models in the most sane way and I went ahead during hackweek (where I was home sick, but that's another story :) and made the webui a rails engine as part of the API. You can read about rails engines at http://guides.rubyonrails.org/engines.html - engines are basically rack apps within rack apps and the magic is in config/routes.rb of API: mount Webui::Engine, at: "/webui2", as: 'webui_engine' Webui::Engine is a 'gem' that lives in src/api/webui and looks very familiar to everyone who knows the old src/webui. The main difference is that everything is in a namespace to avoid clashes between API and Webui code. E.g. src/webui/app/controller/home_controller moved to src/api/webui/app/controllers/webui/home_controller.rb (i.e. one more /webui in the path). This makes it possible to use API models directly in the Webui code, but it needs to be done with care as the permissions handling is right now done purely in API controllers. So there are quite some things we can cleanup, but first I want to finish the merge. So if you now `rails s` in API, you get a /webui2 route that should look very familiar. As the webui code still calls into the $api, I switched development rails server to unicorn and it starts 4 "workers", one will be the webui and one the API, but for some reason 2 workers stalled at times, so I went for 4 :) For testing it's even more complex as the test case can't call into itself, so I still start a webrick "test API" and this had some fun consequences as there are now 2 API processes during testing, one being the test case and the other the test API. To make caching work (i.e. one process being able to delete the cache when things become inconsistent) I had to switch testing to memcached store, which is rather sad. And I also had to switch away from transactional fixtures for the webui tests as this required a transaction in both of the above processes and I was unable to make one process reading the INSERTS of the other reliable (in case someone thinks 'transaction isolation level' now - it's not reliable :). So after a lot of hair pulling (and people knowing me know how hard *that* is for me), I went for database cleaner truncating the tables after each test case and refilling the fixtures. This is fortunately not as slow as it sounds. I already started to move code out of the webui controllers currently in the API "back" into the webui. As I said, it needs to be done with care, but it feels to good to sanitize the code. I also started to deploy the code on build-test.opensuse.org, but they show some problems with the deployment, that I need to fix before we can go on. Greetings, Stephan -- 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] Bootstrapping a new OBS instance
by Nathan Cutler 17 Oct '13

17 Oct '13

Hi all, please advise. I'm bootstrapping a new OBS instance. I would like it to run on SLES11-SP3. After reading the available docs, I'm supposing the best way to install is to do this on a vanilla SLES11-SP3 system: # zypper ar -f http://download.opensuse.org/repositories/OBS:/Server:/2.4/SLE_11_SP3/OBS:S… # zypper in -t pattern OBS_Server For the time being this will just be a testing/learning environment, so server and workers will be in a single VM. However, it would be nice if there is a possibility to split off the workers to dedicated hardware later. Any suggestions, advice, caveats, things to be aware of? Especially I am interested in the 'OBS' and 'server' LVM volume groups. I should create those _before_ running the above commands, right? Thanks, Nathan -- 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] Prjconf Prefer
by Darin Perusich 17 Oct '13

17 Oct '13

Hello All, I'm trying to work around an issue in devel:lang:perl for SLE_SP3 where perl provides an old version of perl(version) which is causing numerous build failures. The prjconf documentation says you can use Prefer to choose a different package for a dependency, but I've set the below Prefer value but I'm still getting "provider perl-version is obsoleted by installed perl". Can someone provide some guidance on this? %if 0%{?suse_version} <= 1110 Prefer: perl:perl-version %endif http://en.opensuse.org/openSUSE:Build_Service_prjconf#Prefer -- Later, Darin -- 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] optimization of OBS experience
by Boris Manojlovic 15 Oct '13

15 Oct '13

Dear all, after looking into results of simple load of page on main OBS (request view but all pages suffer from this) i have come to conclusion that simplest things are not implemented to lower bandwidth usage nor load speed of pages. I understand that most of the time people wait for api.o.o response but really do we need to wait for 70% more time because as can be seen here http://paste.opensuse.org/29484148 Most of "issues" i would list here as: - No javascript "minification", - No css "minification", - No gzip/deflate encoding/content type at all and as such high bandwidth usage, - Etag support is non existent Not everyone have 40/MBs :) Boris -- 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] obs build changing devpts mount opts
by Darin Perusich 15 Oct '13

15 Oct '13

Hello All, I was building some packages locally afterward/during I started having this problem where when I'd open a new konsole it would just be blank and it seemed like the only way to get my system back in order was to reboot. After some digging I've determined that after running "obs build openSUSE_12.3" the mount opts of devpts are changing to "rw,relatime,mode=600,ptmxmode=000" from "rw,relatime,gid=5,mode=620,ptmxmode=000" This appears to be related to a glibc update released the other day and how "osc build" does it's chroot, "mount -n -tdevpts none $BUILD_ROOT/dev/pts". A quick work around is to "mount -oremount /dev/pts" should anyone else get hit by this. I haven't filed a bug yet but it's coming. http://sourceware.org/ml/libc-alpha/2013-08/msg00454.html http://lists.opensuse.org/opensuse-updates/2013-09/msg00072.html -- Later, Darin -- 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] Branching fails for devel:ide:tools/codeblocks
by Andreas Vetter 15 Oct '13

15 Oct '13

Hi, I just branched devel:ide:tools/codeblocks. Then i added and deleted some Repos in my branch https://build.opensuse.org/package/show/home:asvetter:branches:devel:tools:… But the branch is broken somehow for package codeblocks. The error in the WebUI is: Files could not be expanded: service recompress failed: Running /usr/lib/obs/service/recompress --file *.tar --compression bz2 --outdir /lxc.tmp.19206/out Compressed _service:tar_scm:codeblocks-unstable-12.11.9399.tar to tar_scm:codeblocks-unstable-12.11.9399.tar.bz2 Any hints? TIA -- Mit freundlichen Gruessen, Andreas Vetter -- 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] ubuntu build hangs in dh_installdocs
by Andreas Baumann 14 Oct '13

14 Oct '13

Hi, I installed a local OBS-Server 2.4 (as appliance image). Added a project, added a repository with Ubuntu 13.04. Running a build on the one local worker. I'm building a boost 1.49 package.. The build starts and then hangs forever in: /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian 0 S 399 759 753 0 98 18 - 5968 wait 14:59 ? 00:00:00 /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian stracing PID 399, I get: wait4(762, This process with PID 762 is a: chown -R 0:0 debian/libboost1.49-doc/usr/share/doc the strace of it shows it waits in: read(3, An lsof of it shows: chown 762 399 3u IPv4 516089 0t0 TCP localhost:39812->localhost:55332 (ESTABLISHED) So the read hangs getting an answer from the 'faked': tcp 0 0 0.0.0.0:55332 0.0.0.0:* LISTEN 813/faked-tcp I just wondered, if somebody else has experienced this problem before. I saw a rather old message of somebody who might have had the same problem: http://lists.opensuse.org/opensuse-buildservice/2008-11/msg00231.html Greetings Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: abaumann(a)yahoo.com Homepage: www.andreasbaumann.cc -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2