October 2013 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

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

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

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

4 4

[opensuse-buildservice] RedHat 7 rpms signed with OBS signer do not install
by Jeff_Glanz＠Dell.com 11 Nov '13

11 Nov '13

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

3 5

[opensuse-buildservice] mini-howto: LDAP / proxy_auth_mode / Header rewrite
by Andreas Herrmann 11 Nov '13

11 Nov '13

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

2 1

[opensuse-buildservice] building xz requires xz
by Brian K. White 03 Nov '13

03 Nov '13

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

5 6

[opensuse-buildservice] stuck builds
by Brian K. White 02 Nov '13

02 Nov '13

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

2 2

[opensuse-buildservice] WEBUI+API = ♥
by Henne Vogelsang 28 Oct '13

28 Oct '13

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

1 0

[opensuse-buildservice] Object not found!
by doiggl＠velocitynet.com.au 28 Oct '13

28 Oct '13

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

2 1

[opensuse-buildservice] Two patches for osc: API URLs with pathname and TLS SNI.
by Oleg Girko 27 Oct '13

27 Oct '13

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/

2 1

Re: [opensuse-buildservice] libraries to be added to build environment for xUbunbu 12.x
by Dmitriy Perlow 25 Oct '13

25 Oct '13

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

1 0

[opensuse-buildservice] libraries to be added to build environment for xUbunbu 12.x
by wobremer 25 Oct '13

25 Oct '13

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

1 0

[opensuse-buildservice] Open Build Service(OBS) 2.4.5 released
by Adrian Schröter 23 Oct '13

23 Oct '13

Open Build Service(OBS) 2.4.5 released ====================================== Another maintenance release of the 2.4 series is out there. This is a bugfix release with some feature backports. Most important is the support for the new Ubuntu 13.10 release, which is using a debian special multiarch packaging now. Also the upcoming CVE number scheme in 2014 is now supported. Apart from that we have a number of bugfixes as described below. OBS is available as usual via the OBS:Server:2.4 project. https://build.opensuse.org/project/show/OBS:Server:2.4 SLES 11 SP 3 is a new supported platform with this release. >From the official Release Notes: ================================ Feature backports: ================== * backend: Debian multiarch support (for Ubuntu 13.10 via perl-BSSolver) * api: support new CVE syntax as it will be used in 2014 Changes: ======== * None Bugfixes: ========= * appliance: fix start order between apache and mysql when using systemd * backend: fix for using if conditions in prjconf macros sections * backend: fix possible cache inconstency in worker binary cache * backend: multiple fixes for constraints handling * backend: use configured http proxies when download worker code. * api: ensure existins of "deleted" project and repository on update -- 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

[opensuse-buildservice] 404 error when creating a project delete request
by Greg Freemyer 23 Oct '13

23 Oct '13

I just noticed "server:zope" seems to be serving no purpose. https://build.opensuse.org/project/show/server:zope I tried to use the WebUI delete button on that page to create a project delete request, but I got a 404 error for this url: https://build.opensuse.org/request/delete_request?method=post fyi: This project has no build targets and was created to solve a bug on openSUSE 10.2 https://bugzilla.novell.com/show_bug.cgi?id=221256 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

2 1

[opensuse-buildservice] Failed to add project or repository: unable to walk on path 'KDE:Qt5/'
by Guillermo Amat 22 Oct '13

22 Oct '13

Hi When I try to add an additional path to my project's repository (openSuse12.3/standard) I get an error like this: Failed to add project or repository: unable to walk on path 'KDE:Qt5/' The steps I do are the following: 1. From the overview page of the project I go to repositories 2. Click on Edit repository 3. Click on Add additional path to this repository 4. Fill Project text box with KDE:Qt5 5. Select openSuse12.3 in the selection box 6. Submit the form 7. The page shows this error:Failed to add project or repository: unable to walk on path 'KDE:Qt5/' I've tried to add some other paths, i.e. openSUSE:12.3:Update with the same results Regards -- 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] When will a repository for 13.1 be created ?
by doiggl＠velocitynet.com.au 22 Oct '13

22 Oct '13

Hello, When will a repository for 13.1 be created ? Thanks Glenn i.e http://download.opensuse.org/distribution/13.1/repo/ http://download.opensuse.org/distribution/13.1/repo/non-oss/ http://download.opensuse.org/distribution/13.1/repo/oss/ -- 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 13.10 OBS failure
by Nico Kruber 21 Oct '13

21 Oct '13

Hi, I'm having problem building packages for Ubuntu 13.10 from https://build.opensuse.org/package/live_build_log/home:scalaris/scalaris/xU… [ 180s] [168/222] installing base-files [ 180s] Selecting previously unselected package base-files. [ 181s] rmdir: failed to remove '/var/run': Directory not empty [ 181s] dpkg: error processing base-files (--install): [ 181s] subprocess installed post-installation script returned error exit status 1 [ 181s] Processing triggers for man-db ... [ 181s] Processing triggers for install-info ... [ 181s] Errors were encountered while processing: [ 181s] base-files [ 181s] exit ... IIRC, there was a similar problem with Debian 7.0 when it was imported: http://lists.opensuse.org/opensuse-buildservice/2013-05/msg00115.html something with the following that needed to be added back then and may need to be extended for Ubuntu 13.10 now(?): %if "%_repository" == "Debian_7.0" Runscripts: gawk %endif Nico

2 2

[opensuse-buildservice] OBS appliance LVM setup
by Nathan Cutler 21 Oct '13

21 Oct '13

I installed OBS_Server using the "raw disk image" obtained from http://openbuildservice.org/download/other/ Now I'd like to use the LVM setup for workers, so I set up a volume group and named it "OBS". It currently has 9.5GB available, but it appears this isn't enough. When I boot the machine I see: Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "OBS" using metadata type lvm2 Activating LVM volume groups... 0 logical volume(s) in volume group "OBS" now active done Remove all LVM partitions in VG OBS for the worker WARNING: The LVM volume group 'OBS' can not be used. Please create one to get worker partitions configured Looking for existing OBS Server LVM Volume ERROR: Not enough space for worker root LVs, just -8628 MB, but at least 4 GB needed. This would seem to indicate that I need to add another ~12.6GB (8.6+4) for it to stop complaining. I.e. total of 22GB. Does it really need that much space? 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] submitting a specific revision does not work
by Olaf Hering 21 Oct '13

21 Oct '13

I'm trying to submit revision 242 of Virtualization/libguestfs, but somehow this fails: https://build.opensuse.org/request/diff/204088 Is there anything to be done on my side to submit rev 242? Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 9

[opensuse-buildservice] xUbuntu 13.10, nothing provides libboost-locale1.53-dev
by Andreas Baumann 19 Oct '13

19 Oct '13

Hi, Does anybody have an idea why 'libboost-locale1.53-dev' is missing in the 'xUbuntu_13.10' repository? A "normal" Ubuntu distribution has a 'libboost-locale1.53-dev'. So far I always kept a local build of 'boost1.xx' providing 'boost-locale1.xx-dev' locally in my project, but that's quite cumbersome. 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 1

[opensuse-buildservice] obs-service-download_files doesn't download files
by Kyrill Detinov 19 Oct '13

19 Oct '13

Hello. Two of my SRs are declined by factory-auto: https://build.opensuse.org/request/show/203318 https://build.opensuse.org/request/show/203319 The errors are: Failed to download. … Source URLs are not valid. Try "osc service localrun download_files" Well, running 'osc service localrun download_files' I see: % osc service localrun download_files HTTP/1.1 404 Not Found Date: Thu, 17 Oct 2013 12:51:50 GMT Server: Apache X-Powered-By: PHP/5.3.18 X-Pingback: http://www.indii.org/wordpress/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Encoding: gzip Vary: Accept-Encoding Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT Connection: close Content-Type: text/html; charset=UTF-8 ERROR: Failed to download "http://www.indii.org/files/tint/releases/tintii-2.8.0.tar.gz" Aborting: service call failed: /usr/lib/obs/service/download_files --outdir /tmp/tmpXGx5CM It works running manually: % wget http://www.indii.org/files/tint/releases/tintii-2.8.0.tar.gz asking libproxy about url 'http://www.indii.org/files/tint/releases/tintii-2.8.0.tar.gz' libproxy suggest to use 'direct://' --2013-10-17 16:55:16-- http://www.indii.org/files/tint/releases/tintii-2.8.0.tar.gz Распознаётся www.indii.org... 83.223.119.251 Устанавливается соединение с www.indii.org|83.223.119.251|:80... соединение установлено. Запрос HTTP послан, ожидается ответ... HTTP/1.1 200 OK Date: Thu, 17 Oct 2013 12:54:50 GMT Server: Apache Last-Modified: Sat, 05 Oct 2013 08:05:48 GMT ETag: "165003c-6460c-4e7f9e2fdcf00" Accept-Ranges: bytes Content-Length: 411148 Keep-Alive: timeout=2, max=100 Connection: Keep-Alive Content-Type: application/x-gzip Длина: 411148 (402K) [application/x-gzip] Saving to: «tintii-2.8.0.tar.gz» 100%[====================================================================>] 411 148 473K/s в 0,8s 2013-10-17 16:55:17 (473 KB/s) - «tintii-2.8.0.tar.gz» saved [411148/411148] What is the problem? -- WBR Kyrill

5 5

[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