March 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] Expired OBS Keys?
by King Thorin 02 Jul '13

02 Jul '13

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] obs 2.4 and ldap
by Darin Perusich 11 Jun '13

11 Jun '13

Hello, I'm attempting to configure ldap authentication in OBS 2.4 and get the warning "ldap_mode selected but 'ruby-ldap' module not installed." when I try to login w/an ldap account. I do have rubygem-ruby-ldap from the OBS:Server:2.4 repo installed and have restarted apache/passenger to ensure it's available. Any thoughts as to what's causing this? -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 10

[opensuse-buildservice] [GSoC2013][BitBake Integration]Call for mentors
by 赵旭 06 Apr '13

06 Apr '13

Hello, I am a student interested in the idea of integrating BitBake with OBS and hope I can work on it in GSoC 2013. Unfortunately Michal is busy this year and wont be able to help most probably. However I myself think it is a great idea and want to make it. So I come to this mailist for help (following Manu's advice) and hopefully there will someone willing to be my mentor on this project and let's make it together:) -- --------------------------------- Xu Zhao Department of Computer Science&Technology Tsinghua University Beijing P.R.China Mobile: +86-152-1058-8604 nuklly(a)gmail.com -- 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] Application:Geo OBS priority
by Angelos Tzotsos 06 Apr '13

06 Apr '13

Hi all, The geospatial repository seems to be building only 1-2 projects at a time for the last 3 days. Since we are upgrading some major applications, we need to build the whole repository and this delay is causing trouble to the users (postgis is still not released for 12.3). I believe that this repository should have a priority raise in OBS (I don't know the current priority or if there is a problem in OBS currently). Best, Angelos -- Angelos Tzotsos Remote Sensing Laboratory National Technical University of Athens http://users.ntua.gr/tzotsos -- 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] OBS build dependency issue
by Malcolm Fernandes 02 Apr '13

02 Apr '13

We have a project in our local OBS instance where we are encountering some build dependency issues. Our OBS is running on an appliance: obs-server-2.3.1-6.7.x86_64 To illustrate the problem: Let's assume we have 5 packages in a project (pkg1, pkg2, pkg3, pkg4, pkg5) The pkg2 spec file contains a "BuildRequires:" for one of the rpms generated by pkg1. Similarly the pkg3 spec file contains a "BuildRequires:" for one of the rpms generated by pkg2 and so forth. When a commit was made to pkg1, it got rebuilt and this triggered pkg2 to start building. While pkg2 was rebuilding, pkg3, pkg4 and pkg5 went into a blocked state (which is what we expected). However, after pkg2 finished building, pkg-3/4/5 get unblocked and do NOT get rebuilt. We tried to wipe the binaries of pkg1 and saw the same behavior. Also wiped the binaries of pkg2 and saw the same behavior for its dependent packages. Trying to understand how these dependencies work from an OBS perspective. Can you please shed some light on this as well as provide some advice on how to debug this further. I've run these options with 'obs_admin' and it has not returned anything: --rescan-repository --force-check-project --deep-check-project Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Broken Link in OBS GUI
by Martin Koegler 02 Apr '13

02 Apr '13

https://build.opensuse.org/project/repository_state?project=openSUSE%3A12.3… contains http://download.opensuse.org/repositories/openSUSE:/12.3:/Update/standard as download links, which yields to a 404 error. Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Rsync from Main Server to Download Servers - Private OBS
by Matthew Drobnak 02 Apr '13

02 Apr '13

Hi all, I see the bs_publish command has support for rsync'ing to another server, but I'm not quite certain how to implement this in the configuration. Does anyone have an example of how to make this work? Thanks. -Matt -- 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] Additional information: texlive openSUSE 12.2 - mf.base missing
by Joerg Emmelmann 02 Apr '13

02 Apr '13

Hello! As announced in my posting "texlive-2012.20120611-20120471.1.x86_64 for openSUSE 12.2 - mf.base missing" (Date: Tue, 05 Mar 2013 17:40:37 +0100) in above package I miss the following file: /var/lib/texmf/web2c/metafont/mf.base Some additional info about installed packages you find in the attached "tex.log" file. In the attached "out" file you find output of the following command: pdflatex article.tex My questions are: Which OBS package provides above file (as mention in my earlier posting due to dependencies of texlive-achemso I cannot install texlive which comes wit opensuse 12.2)? Which OBS packages are generally needed to replace the texlive package which comes wit opensuse 12.2? Thank you very much. Kind regards Joerg

3 3

[opensuse-buildservice] timezone package not in openSUSE 12.3/Factor workers
by Darin Perusich 29 Mar '13

29 Mar '13

Hello All, I've been looking at an issue with the perl-DBIx-SearchBuilder package in d:l:p where "make test" was failing openSUSE_12.3 and Factory. It turns out %check is failing because the timezone package is no longer included in the default OS image for openSUSE 12.3 and Factory. I can, and will, add timezone as a BuildRequire for this package but didn't know if this was by design or if it was overlooked and should be part of the default OS image. Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] How to find packages for other distros
by Gianluca Emme 29 Mar '13

29 Mar '13

Dear all, I'm trying to package my software to as many systems as possible. And for each new distribution release it is always a pain to search the correct name for the required packages for building the RPM. :-( :-( Maybe because I don't know the easy way to find the package name ?? What is your way to find the name package ?? Please, suggest me... or just share our way to do it... maybe everyone can learn something :-) My way: - first I search the package name for openSuse from the download.opensuse.org search page - after a successful compilation on openSuse, I'll try to figure out how to write the dependecies in the form of pkgconfig(package); for doing it, the only way I found is: - to install the package on my opensuse, - open Yast->Software Managements, - look for the package, - go to the list of installed files, - looking for a file with extension .pc - then I add other distro repositories with the hope that pkgconfig(package) works also for them - unlucky, does not work for all distribution... but I don't know how to find out which of the two following error arise: - unresolvable because the name of the package inside the pkgconfig statement is wrong. This because other distro might install a different named .pc file - unresolvable because the package is not in the standard repository of the distro - unresolvable because the package version in the standard repository is too old respect to what request by .spec file - in this case, my only way is to look for the package in some various rpm search engine like rpm.bone.net, pkgs.org etc, and - when I found the name of the package, I'll put into the .spec file an %if macro for the distro and so on for all the distro !! :-( So, the problem is even worst because different version of the same distros have different behaviour :-S For example, the "BuildRequires: pkgconfig(glu), cmake" works fine on CentOS 6... while the same exacly statement does not work on CentOS 5 whith the error: "unresolvable pkgconfig(glu) and cmake" Is it possible that "cmake" is in the standard repository of CentOS 6 and not into the standard repository of CentOS 5 ??? Is it possible that the CentOS 5 does not recognize the pkgconfig command in BuildRequires ?? Thanks, Gianluca. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] repo snapshots
by Kanstantsin Shautsou 28 Mar '13

28 Mar '13

Hi, could somebody describe how snapshots repo work? Let's assume that i have project PROJECT with repo REPO. I created repo snapshot by adding it to meta. then: obs_admin --clone-repository PROJECT REPO snapshot Destination repo must get created by scheduler first! According to source code it checks build/PROJECT/REPO dir, but project should have disabled building/publishing? Anyway even with enable publish for snapshot repo scheduler doesn't create needed directory. -- 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] Private OBS instance webui Authentication failed
by Darin Perusich 27 Mar '13

27 Mar '13

Hello All, I'm setting up a private obs instance on an opensuse 12.1 system and the setup's gone off without issue until I attempt to log into the web interface. When attempting to login with Admin/opensuse I get authentication failed. I'm able to log into the API using osc and a browser. From the webui production.log it looks like it's missing some configuration but I'm not sure where to look for that, the log is below. What do I need to do this resolve this? OpenSUSE 12.1 openSUSE_Tools_2.3 - http://download.opensuse.org/repositories/openSUSE:/Tools:/2.3/openSUSE_12.… [INFO |#21143] Processing ApplicationController#index (for ::1 at 2013-03-26 11:06:36) [GET] [FATAL|#21143] ActionController::RoutingError (No route matches "/configuration.json" with {:method=>:get}): passenger (3.0.9) lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' passenger (3.0.9) lib/phusion_passenger/abstract_request_handler.rb:513:in `accept_and_process_next_request' passenger (3.0.9) lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:321:in `start_request_handler' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `send' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/utils.rb:479:in `safe_fork' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:270:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:180:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:268:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:263:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:261:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:180:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:93:in `start' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:219:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:214:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:213:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:132:in `spawn_application' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) helper-scripts/passenger-spawn-server:99 [ERROR|#21143] rescue_action: caught ActionController::RoutingError: No route matches "/configuration.json" with {:method=>:get} [INFO |#21143] Rendering template within layouts/application [INFO |#21143] Rendering error (404) [INFO |#21143] Processing ApplicationController#index (for ::1 at 2013-03-26 11:06:36) [GET] [FATAL|#21143] ActionController::RoutingError (No route matches "/person/Admin" with {:method=>:get}): passenger (3.0.9) lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' passenger (3.0.9) lib/phusion_passenger/abstract_request_handler.rb:513:in `accept_and_process_next_request' passenger (3.0.9) lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:321:in `start_request_handler' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `send' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/utils.rb:479:in `safe_fork' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:270:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:180:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:268:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:263:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:261:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:180:in `start' passenger (3.0.9) lib/phusion_passenger/classic_rails/framework_spawner.rb:93:in `start' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:219:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:214:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' passenger (3.0.9) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:213:in `spawn_rails_application' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:132:in `spawn_application' passenger (3.0.9) lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.9) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.9) helper-scripts/passenger-spawn-server:99 [ERROR|#21143] rescue_action: caught ActionController::RoutingError: No route matches "/person/Admin" with {:method=>:get} [INFO |#21143] Rendering template within layouts/application [INFO |#21143] Rendering error (404) [INFO |#19275] Processing UserController#do_login (for 10.100.90.47 at 2013-03-26 11:06:36) [POST] [INFO |#19275] Parameters: {"authenticity_token"=>"mf52T8Pu/WLlBChPLQDInssERfZ8kFcWSwneuSuYjDg=", "return_to_path"=>"/", "login"=>"Login »", "action"=>"do_login", "username"=>"Admin", "method"=>"post", "password"=>"[FILTERED]", "controller"=>"user"} [INFO |#19275] Anonymous request to / [ERROR|#19275] --> caught EOFError: end of file reached, retrying with new HTTP connection [ERROR|#19275] Site configuration not found [INFO |#19275] Rendering template within layouts/application [INFO |#19275] Rendering user/login [INFO |#19275] Completed in 138ms (View: 66, DB: 10) | 200 OK [https://obs.its.ctg.com/user/do_login?method=post] -- 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 3

[opensuse-buildservice] Best Practice for protecting osc user credentials?
by Craig Gardner 26 Mar '13

26 Mar '13

Friends. I was walking through the scenario of setting up an osc client for a first-time user. It became clear to me that the use case for first-time osc setup may need to be refined. For those who don't want their password stored in clear text in .oscrc, there are several manual steps that must be taken, which makes the process rather clumsy. 1- install osc.rpm 2- run any 'osc' command that accesses an OBS server osc prompts user for username and password osc creates fresh, default ~/.oscrc file, and stores the user's password in plaintext 3- edit ~/.oscrc 3a - remove server section, including username and password keypairs 3b - set "use_keyring=1" or 3a - remove password keypair, and replace it with keyring=1 3b - set "use_keyring=1" 4- re-run any 'osc' command that accesses an OBS server Is there any other way to do this the first time, to originally tell osc to use a keyring? That is, without having to pre-create a .oscrc file? Is there any way to inform osc that you're already running in a keyring environment? It seems that osc presumes that no keyring management is running, which I suppose makes sense. -- 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] obs clone whole project
by Matwey V. Kornilov 26 Mar '13

26 Mar '13

Hi, I want to clone whole a project (or link, or branch, or something like that) into my home:. And I don't want to do it manually branching every package. I think it is possible to do it in more easy way. What I need to reach: 1. ability to edit prjconf of the clone project 2. ability to patch some packages and add new, not existing in original project I want to test RPM AutoReqProv scripts for Erlang. I need separate project cloned from devel:languages:erlang, where all packages will be rebuilt with my magic and available for everyone to install and test. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] new dependency errors in OBS
by Olaf Hering 25 Mar '13

25 Mar '13

What is the reason for the errors in Virtualization:libguestfs-devel? openSUSE_Factory x86_64 blocked: libvirt-devel, libvirt-client, perl-Sys-Virt openSUSE_Factory i586 blocked: perl-Sys-Virt openSUSE_12.3 i586 failed openSUSE_12.3 x86_64 failed openSUSE_12.2 i586 failed openSUSE_12.2 x86_64 failed openSUSE_12.1 x86_64 building: building on build20:15 openSUSE_12.1 i586 succeeded openSUSE_11.4 i586 building: building on build14/2 openSUSE_11.4 x86_64 finished: succeeded SLE_11_SP2 i586 unresolvable: have choice for distribution-release needed by kernel-default: sled-release sles-release SLE_11_SP2 x86_64 unresolvable: have choice for distribution-release needed by kernel-default: sled-release sles-release The 12.2/12.3 failures are odd, ruby is not installed, but when attempting the build ruby is required. The sles11 failure is also odd, there is a sles_version check in there which used to work. I have searched for uneven if/else/endif in the specfile, but it looks clean. Any idea whats going on here? Olaf -- 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] Error building 12.3 opensuse kernel
by Dmitry Teslenko 25 Mar '13

25 Mar '13

Hello! I want to branch current 12.3 opensuse kernel package to build it with custom config.addon.tar.bz2 configuration file. I've tried branching Kernel:stable and openSUSE:12.3:Update kernel-default package with no luck. I get this error: >> could not retrieve ssl certificate: 400 remote error: /usr/local/sbin/bssign 256 Here's link to error: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kerne… -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Mono:Community & openSUSE 12.3
by Dmitriy Perlow 23 Mar '13

23 Mar '13

Hello! Could anybody add oS 12.3 as a buildtarget at https://build.opensuse.org/project/show?project=Mono%3ACommunity please? -- Dmitriy DA(P).DarkneSS Perlow / Linux x64 -- 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] How to inherit package meta between project links?
by Srinidhi B 21 Mar '13

21 Mar '13

Hi, In case of a project link, how do I make packages inherit their corresponding meta from the linked project? Here's an example setup: * ProjectB contains <link project="ProjectA"/> in it's project meta * Both ProjectA and ProjectB meta contains <debuginfo><enable/></debuginfo> * ProjectA contains a package called PackageA with <debuginfo><disable/></debuginfo> Currently, PackageA has debuginfo enabled in ProjectB. Is it possible to make PackageA continue to have debuginfo flag disabled in ProjectB without making a copy of it in ProjectB? Srinidhi. -- 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] making SR review easier (was Re: [opensuse-packaging] Review policy)
by Adam Spiers 21 Mar '13

21 Mar '13

[setting Cc and Reply-To to the opensuse-buildservice list] Sascha Peilicke (speilicke(a)suse.com) wrote: > On 03/21/2013 09:50 AM, Togan Muftuoglu wrote: > > On 03/21/2013 09:10 AM, Sascha Peilicke wrote: > > > > The reason is I had a declination with a comment why I have not > > > > explained use of %ghost macro in a spec file, but a person who would > > > > have reviewed the rpm buildlogs for the package would realize the fact > > > > that rpmlint gives the following error. > > > > > > Who seriously looks at buildlogs when reviewing requests? > > > > I do and I would expect those who review requests do as well other wise > > why bother in the first place to generate a build log and rpmlint log. > > If the package doesnot build it is recommended to have a look at the > > build log. Well I would assume if it builds fine one still should look > > the logs and especially the rpmlint log > > Well, we review packages building for multiple architectures and a > plethora of distros. Of course I mostly care about openSUSE:Factory > (i586,x86_64) but still. And yes, I look at the rpmlint log for that > target too. And no, I don't look at any build-log. On a calm day, I > review ~50 packages 8-O Wow, I had no idea any one person did that much work! AFAICS, the rpmlint results are only available in two places: - the build log - the Rpmlint Results tab on each package's Overview page Right? And neither of these are formatted in a very nice way. > I simply don't have the time and it makes no > sense either. Packages that don't build are declined by > 'factory-auto' already, packages that build are good enough. I doubt > people would appreciate if we start commenting the fuzzy mess that > build-logs are ;-) Since I am not currently a regular reviewer, feel free to tell me if I'm talking rubbish, but it seems to me that there are some low-hanging fruit changes we could make here to make life much easier for reviewers, e.g.: - Change the Rpmlint Results tab to group warnings/errors by filter type, and just show the number of occurrences in each group. Then you can mouseover or click to see more details. - Add a way to view an rpmlint results summary via osc (is there an API call for this, or do you just have to grep the build log client-side?) - Automatically color the build log according to patterns. - Automatically split the build log into the different phases, e.g. - booting the VM - init_buildsystem etc. - %prep - %build - %install - /usr/lib/rpm/brp-* hooks - autoreqprov calculation - %clean - post-build checks (01-check-debuginfo ... 99-check-remove-rpms) - rpmlint - post-build tasks (e.g. "creating baselibs", "comparing built packages with former built") - VM power down and make each section expandable in the webUI with all sections starting collapsed and colour-coded red/green according to whether the section's contents matched any known failure patterns. (Actually I already have some code which might help implement this last idea.) Maybe an idea for the next hack week? If that makes sense to people then I can submit the idea as a proposal. -- 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] Buildservice mirrors?
by Jim Henderson 20 Mar '13

20 Mar '13

I'm looking to mirror the Virtualbox_backports repository on the build service, but I seem to keep running into problems with connecting to rsync.opensuse.org (connection slots full or a few other odd issues). When I looked to see what mirrors there are of OBS, the list showed empty - do those repos not get mirrored anywhere? If they do, where can I find a list of them? Thanks, Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] project config preinstall i686 on x86_64
by Kanstantsin Shautsou 20 Mar '13

20 Mar '13

Hello, i have binary imported glibc packages for i686 and x86_64 (from fedora). I'm trying to Preinstall both arches, but it doesn't work. It also don't see Required: glibc(x86-32) or glibc.i686. Any ideas?-- 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] Link, Aggregate and repositories... which to choose ??
by Gianluca 20 Mar '13

20 Mar '13

Dear All, I'm really confused about the documentation of Links, Aggregates and building against more repositories... and I don't know which one fit my situation. I have a project on which I'm building a package named "yarp". This package requires the library ACE and this library has been already packaged by the devel:libraries:ACE:major project. And I want to achieve a self-contained repository for my package yarp in order to just tell to the users to add my project repository without also the need to add the ACE repository. If I specify in my project repositories to use also ACE repository (<path project="devel:libraries:ACE:major" repository="openSUSE_12.3"/>) then the building of yarp package goes well, but the user has to add both ACE and my repository in order to statisfy all requirements and install ACE. I cannot find a way that implicity add also the ACE repository for the user, or that link in some ways the ACE package without wasting space. My first option was to use aggregate, but it is really discouraged its use because not only waste space but there is also a risk of incompatible breakages :-( But I'm not want to use link, because it rebuild the package ... and because I don't need to change anything to ACE, this option will be not only a waste of space but also a waste of building resources So... are there some other options ?? I wondering if there is a simple solution like a symbolic link toward the ACE package, in order to get all requires resolvable when the user add my repository. Is that possible ?? Thanks, Gianluca. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Any docs for development about open build service
by Aaron Yung 20 Mar '13

20 Mar '13

Hi All I am curious about the OBS webui communication with the backend api, so I begin to study ROR for some days. Is there a easy way to understand the communication between OBS frontend webui and the backend api , just like some docs about activexml module or for developers? Thanks! ----- Go OBS -- View this message in context: http://opensuse.14.n6.nabble.com/Any-docs-for-development-about-open-build-… Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 9

[opensuse-buildservice] specfile with internally defined %macro that rep_server doesn't like
by Craig Gardner 19 Mar '13

19 Mar '13

Hi fellow OBS experts, I have a problem with a specfile building in my own Build Service, version 2.3.8-ish. I suspect the same thing would happen with this specfile in OBS. Whenever I check in this specfile to my project, the rep_server gets very angry with me and gives me error messages. If fact, the src_server records the exact same messages. <cut> Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 257. Use of uninitialized value in concatenation (.) or string at build/Build/Rpm.pm line 365, <SPEC> line 257. Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 258. Use of uninitialized value in concatenation (.) or string at build/Build/Rpm.pm line 365, <SPEC> line 258. Odd number of elements in hash assignment at build/Build/Rpm.pm line 131, <SPEC> line 259. </cut> (There are actually more lines, but the text above is sufficient to show the error messages.) Looking at the specfile, the lines implicated took like this: <cut> %package_library cherrypy BSD %package_library django BSD %package_library iso8601 MIT </cut> The %package_library macro is defined as: <cut> %define package_library() \ %define library %1 \ %define license %2 \ %package lib-%{library} \ Summary: Foo Library: %{library} \ Group: Applications/System \ License: %{license} \ %description lib-%{library} \ Foo Shared Library: %{library} \ %files lib-%{library} \ %defattr(-,root,root) \ /%{_lib}/%{library} \ %{nil} </cut> This, of course, is a completely valid specfile when used with rpmbuild. It may not be written according to best practices, but it's entirely valid and very handy shorthand. It's just that the {src,rep}_server clearly don't like it. Is this something that should be filed as a bug in OBS? Any other suggestions on how to address this situation? -- 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] Add optional update for SLES to SUSE:SLE-11:SP2:Update
by Dirk Müller 19 Mar '13

19 Mar '13

Hi, could we please add http://download.novell.com/Download?buildid=IxkUO_gjJ4I~ as an additional package to SUSE:SLE-11:SP2:Update in OBS? I'm missing it in one of my projects. Thanks a lot in advance, Dirk -- 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] Replacement for my_work?
by Stephan Kulow 19 Mar '13

19 Mar '13

Hi, I have a script to query factory reminder mails and a lot of people seem to rely on them, but some update on build.opensuse.org broke it. Here is my code: my $ua = LWP::UserAgent->new; $ua->timeout(15); $ua->default_header("Accept" => "application/json"); my $mywork = $ua->get("https://build.opensuse.org/home/my_work?user=$user"); unless ($mywork->is_success) { die $mywork->status_line; } -> Here it always dies with a error 500 Please provide a replacement. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] texlive-2012.20120611-20120471.1.x86_64 for openSUSE 12.2 - mf.base missing
by Joerg Emmelmann 18 Mar '13

18 Mar '13

Hello! In above package I miss the following file: /var/lib/texmf/web2c/metafont/mf.base I have checked: # rpm -ql texlive-2012.20120611-20120471.1.x86_64 /usr/lib/tlpkg/TeXLive/TLConfig.pm /usr/lib/tlpkg/TeXLive/TLUtils.pm /usr/share/man/man8/public.8.gz /var/adm/update-scripts/texlive-2012.20120611-20120471.1-zypper # rpm -qf /var/lib/texmf/web2c/metafont texlive-filesystem-2012.61-30.1.noarch The package texlive-2011-13.5.1.noarch.rpm belonging to the updates of the openSUSE 12.2 distribution containes this file. Is there any OBS package where I can find this file? Hints: Due to a package dependency of texlive-achemso I cannot use texlive- 2011-13.5.1.noarch.rpm. My colleague which uses the texlive packages wants the font phvr7t and found this issue (see attachment). Thank you. Cheers Joerg -- ---------------------------------------------------------------- Jörg Emmelmann Max-Planck Institut für Intelligente Systeme (früher Max-Planck Institut für Metallforschung) Abt. Dietrich (IT-Gruppe) / Max Planck Institute for Intelligent Systems (formerly Max Planck Institute for Metals Research) Dept. Dietrich (IT-Group) Heisenbergstr. 3 70569 Stuttgart Tel. / phone: +49 711/689-1836 Fax. / fax: +49 711/689-1088 E-Mail / email: emmelmann(a)is.mpg.de ----------------------------------------------------------------

2 1

[opensuse-buildservice] New project openSUSE:Current?
by Cristian Morales Vega 18 Mar '13

18 Mar '13

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Forcefull removal of buildtargets failing
by Bjørn Lie 15 Mar '13

15 Mar '13

Hi all. I'm trying to remove a repo/buildtarget that other users have branched from, yet doing it the "suggest" way via bjolie@embla:~> osc meta prj -e Project:FOO -f Sending meta data... BuildService API error: 500 Try again? ([y/N]): n discarding /tmp/osc_metafile.DoNwAp.xml bjolie@embla:~> lands me in this lovely errormsg. Pretty sure this worked fine before latest changes on the obs. Does anyone have some insight into what might be going wrong? //Bjørn Lie -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] [ANNOUNCE] new osc plugin: prdiff for comparing projects
by Adam Spiers 13 Mar '13

13 Mar '13

Hi all, I wanted a way to quickly compare a project with its "upstream" project, and a quick hack ended up as a new osc plugin: https://gist.github.com/616b476a9c592a0a2a89 (Copy to your ~/.osc-plugins or /var/lib/osc-plugins to try it.) Example usages: $ osc prdiff --include=client openSUSE:Factory Cloud:OpenStack:Factory differs: python-glanceclient identical: python-keystoneclient differs: python-novaclient differs: python-quantumclient identical: python-swiftclient $ osc prdiff --new-only --exclude='crowbar|rubygem' \ systemsmanagement:chef:10:staging \ systemsmanagement:crowbar:2.0 identical: couchdb identical: erlang identical: gecode identical: js differs: rabbitmq-server new only: all-barclamps-good new only: fakechroot new only: libyaml new only: ruby new only: ruby-common new only: ruby19 new only: sleshammer $ cd ~/OBS/home/aspiers/branches/devel/languages/ruby/ $ osc prdiff --diffstat --requests differs: ruby-common generate_buildrequires.sh | 31 ++++++++++++++++++++++++++----- ruby-common.changes | 8 ++++++++ 2 files changed, 34 insertions(+), 5 deletions(-) 148023 State:new By:aspiers When:2013-01-11T11:04:14 submit: home:aspiers:branches:devel:languages:ruby/ruby-common -> devel:languages:ruby Descr: - Fix it to work even if all-good has just been created locally via mkpac and doesn't exist server-side yet. - Improve support for running within a branch of the original project. This allows submitreqs which change all-good.spec. Feedback welcome. I'd also like to know if it makes sense to include this in osc core (my vote is yes, but I'm biased ;-) Cheers, Adam -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 10

[opensuse-buildservice] Building for Base:System fails with public key message
by Andreas Jaeger 13 Mar '13

13 Mar '13

Building a package on openSUSE 12.3 for openSUSE:Factory using Base:System, the building suddenly stops with this messages: warning: /var/tmp/osbuild- packagecache/Base:System/openSUSE_Factory/x86_64/coreutils-8.17-183.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5d053b4f: NOKEY /var/tmp/osbuild- packagecache/Base:System/openSUSE_Factory/x86_64/coreutils-8.17-183.1.x86_64.rpm : public key not available /var/tmp/osbuild- packagecache/Base:System/openSUSE_Factory/x86_64/diffutils-3.2-23.1.x86_64.rpm : public key not available /var/tmp/osbuild- packagecache/Base:System/openSUSE_Factory/x86_64/filesystem-12.3-102.1.x86_64.rpm : public key not available /var/tmp/osbuild- packagecache/Base:System/openSUSE_Factory/x86_64/fillup-1.42-283.14.x86_64.rpm : public key not available What's wrong here? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] devel:languages:smalltalk dead?
by Michael Behrisch 13 Mar '13

13 Mar '13

Hi, while looking for a recent scratch http://scratch.mit.edu/ in opensuse I found that there are different versions of squeak running around in X11:Sugar and devel:languages:smalltalk. The latter project seems not to have seen any updates for almost three years, so I decided to submit all of my changes to Education (where scratch lives). Is there any smalltalker who wants to revive it or is it better to have it all in Education? Best regards, Michael -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] How to Bypass user authentication during webui debug
by cheyw 08 Mar '13

08 Mar '13

Dear All Now I Encountered a problem about debugging webui. I follow the steps at the debug website (http://en.opensuse.org/openSUSE:Build_Service_Webclient_Development#Debuggi…) when I access 'localhost/project/list_public' or something else after execute the "script/server", the browser is always showing me that "Unauthorized access, please login" and so on . As we know, at this time there is no any user in database. How can I bypass the problem ? Or I did something wrong ? -- View this message in context: http://opensuse.14.n6.nabble.com/How-to-Bypass-user-authentication-during-w… Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Internet access during local build
by Gianluca 07 Mar '13

07 Mar '13

Dear All, in the %build section of an .spec file I'm writing I need to run a thirds part script that use wget to download some file directly from internet. If I try to build the .rpm locally to check any error before to commit the changes, I'll get the following error: Resolving www.netlib.org (www.netlib.org) failed: Connection refused. wget: unable to resolve host address `www.netlib.org' It seems that during the build of an rpm there is no internet access. How can I configure osc in order to have internet access during the local building of packages ?? Thanks, Gianluca Massera. -- 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] osc diff complains about missing files
by Olaf Hering 06 Mar '13

06 Mar '13

The 'osc diff' command from osc-0.139.1 complains about missing files if files from an earlier 'osc ar' were removed. I think 'osc diff' should be more forgiving and diff just whats (still) there. # rm release-1.tar.bz2 # wget host/pub/release-2.tar.bz2 # sed -i 's@^Version:.*@Version: 2@g' *.spec # osc ar # sleep $((60 * 60 * 24 * $n)) # rm release-2.tar.bz2 # wget host/pub/release-3.tar.bz2 # sed -i 's@^Version:.*@Version: 3@g' *.spec # osc diff file 'release-2.tar.bz2' is marked as 'A' but does not exist (either add the missing file or revert it) # Olaf -- 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] Open Build Service (OBS) 2.4.0 RC 1 is out there
by Adrian Schröter 06 Mar '13

06 Mar '13

We are proud to announce the availability of OBS 2.4.0 RC 1. Plenty of features and other improvements went into this release. In short, it supports new packaging formats, new architectures, supports new virtualization methods, offers new collaboration workflows and can handle build job distribution better. As a release candidate, it may get released unmodified, but please give it a final test before. One thing which is currently in unclear state is the LDAP support. While there is a group working on improving it, the current code is completely untested by SUSE. It would be great if someone could test it before release. The release rpms and appliances can be found in OBS:Server:2.4 project: http://en.opensuse.org/openSUSE:Build_Service_Appliance Repositories: http://download.opensuse.org/repositories/OBS:/Server:/2.4/ The version is currently tagged as 2.3.95. Please find the full release notes below: ========================================= # # Open Build Service 2.4 # Please read the README.SETUP file for initial installation instructions or use the OBS Appliance from http://en.opensuse.org/Build_Service/OBS-Appliance There is also an install medium with installs OBS on hard disc now. dist/README.UPDATERS file has informations for updaters. OBS Appliance users who have setup their LVM can just replace their appliance image without data loss. The migration will happen automatically. Regressions: ============ * LDAP support is not tested and in unknown state (not part of test suite) (A rewrite of it is WIP) * source service editor in webui is not available anymore Changes on purpose: =================== * Migration to Ruby 1.9 and Rails 3.2 * request database got moved from backend to the api. Directly after update all requests seem to have vanished, but a delayed job is importing them again. This can take some hours dependening on the amount of requests. * package meta of package copy command is not copying relationships and devel definitions anymore * Requests do require a description now in any case * webui configurations got moved from environments/*.rb to config/options.yml. * Package conflicts and obsoletes are taken into account when resolving dependencies for build jobs. This improves build consistency but may also lead to new "unresolvable" errors, since they were ignored so far. The old behaviour can be restored by adding the following line into the project configuration: ExpandFlags: ignoreconflicts * cross architecture build directives in project configuration CBInstall and CBPreinstall are not supported anymore. Use standard "Install" and "Preinstall" directives instead. => all architectures can be used as host for cross build now. * The api file/distribution.xml is obsolete, the config gets stored in the SQL database now. Existing file gets imported during migration. The list from remote instances can displayed and updated automatically now. Features ======== * Arch Linux package format support got added. * Build Job Constraints handling. It can be used to define build instance requirements for certain build jobs. Either for defined package sources or for all repositories. Documentation about this can be found here: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_… * Support of preinstall images, which can be used to speed up build jobs. They need to be build manually, but get automatically used for creating a build instance base in a faster way than just with installing packages. * Static links (without version and release numbers) for binary results in the published repositories can be configured now. This can be done via the "staticlinks" keyword in Repotype: definition. * Build Prerequires can be used also with the FileProvides feature in the build configuration now. * Regular users can copy entire projects (without binary results) now. * Upload of binaries via api is allowed to administrators now. * Data about used resources of build jobs get collected. However it gets not yet used for build job assignment * Requests can be listed also for given groups now. * Checkout of delete packages does not require a srcmd5 sum anymore. * Delete Requests can be used to request deletion of repositories from a project. * Support of creation of application data xml which can be used for app stores for application centric browsing versus package browsing. * Support hugetable memory usage for kvm workers. * Support building cross build formats, eg. building an rpm with a kiwi build description or an deb package via a .spec file. * Efficient transport of product build results from worker to backend. * aarch64 architecture added (aka armv8 or arm64) * New generic "emulator" virtualization support. Can be used to build inside of system emulators (for foreign hardware for example) * New s390 z/VM virtualization support. Deprecated: =========== The following calls have been marked as deprecated, they will get removed in OBS 3.0 * api - /person/$LOGIN/group -> use /group?login=$LOGIN instead - /search/project_id -> use /search/project/id instead - /search/package_id -> use /search/package/id instead * The deprecated support to copy qemu binaries from external build host into build environment has been removed. This includes also the CBInstall and CBPreinstall project configuration directives. Notes for systems using systemd: ================================ OBS is using init scripts, not systemd style .service files. This will stay until we will switch from SLES 11 to SLES 12 as default production platform. openSUSE installations may use systemd (instead of sysvinit) and it should work in general. Not working are usages like # rcobssrcserver status You will only get the systemd status here. Also stopping services may not kill all processes, which leads to abstract errors when trying to restart them. We heard also about trashed MySQL databases when using systemd. To avoid these problems you need switch directory to avoid the systemd mapper: # cd /etc/init.d # ./obssrcserver status|stop|start -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

1 0

[opensuse-buildservice] Certificate not found
by Archie Cobbs 06 Mar '13

06 Mar '13

This is on a 12.2 system where I'm attempting to run osc for the first time: $ osc build *** certificate verify failed at depth 1 Subject: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3 Issuer: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV Root CA Valid: Apr 2 12:00:00 2008 GMT - Apr 3 00:00:00 2022 GMT Fingerprint(MD5): C68B9930C8578D416F8C094E6ADB0C90 Fingerprint(SHA1): 42857855FB0EA43F54C9911E30E7791D8CE82705 Reason: unable to get local issuer certificate Reason: certificate not trusted A certificate in the chain failed verification Would you like to 0 - quit (default) 1 - continue anyways 2 - trust the server certificate permanently 9 - review the server certificate Enter choice [0129]: 9 Certificate: Data: Version: 3 (0x2) Serial Number: 06:c5:3c:43:e4:39:47:ec:d4:7c:66:da:7c:09:b9:1d Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert High Assurance CA-3 Validity Not Before: Jan 11 00:00:00 2012 GMT Not After : Mar 20 12:00:00 2015 GMT Subject: C=US, ST=Utah, L=Provo, O=Novell, Inc., OU=IS&T, CN=*.opensuse.org Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (2048 bit) Modulus: 00:e0:55:90:91:8d:0d:7c:a8:37:61:59:78:13:23: bf:9e:48:29:b0:8c:c7:cf:da:76:1c:48:7c:cd:eb: 49:06:35:85:65:1f:28:dc:b1:f0:78:7b:2d:32:40: b3:16:22:e0:70:f7:eb:f1:a6:51:ea:48:29:03:60: ef:87:ea:24:01:79:83:d2:35:e9:5a:e0:12:14:86: 4d:21:02:73:37:8c:da:a9:33:4c:82:94:a7:9d:bf: 79:68:c7:fb:86:81:75:2e:cb:82:5a:53:2c:a9:ed: 9c:d0:92:06:6a:5b:2e:1b:42:08:24:80:02:3d:2f: ba:30:87:f7:92:f7:62:a2:43:c1:cd:5e:5d:05:6b: e9:ed:5e:bc:cd:1a:e6:b5:2c:9d:04:80:26:31:c2: 51:0f:aa:2a:21:34:52:0d:c8:d4:63:fe:77:14:fc: b6:0a:d2:a8:09:99:73:dc:e2:72:57:ba:b6:1c:36: 3f:00:81:ba:40:7b:7d:32:dd:45:23:61:15:ca:4f: f2:d2:eb:07:7b:6f:e4:e1:a0:bf:c2:01:9b:76:90: 4d:5e:a4:45:4a:d1:7a:3e:07:d4:4d:19:52:fb:d0: c4:94:3b:62:61:f6:8d:10:0b:22:3c:30:51:4b:ee: 14:94:08:1f:fe:15:69:6d:6d:71:97:d5:cc:f0:60: e0:19 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Authority Key Identifier: keyid:50:EA:73:89:DB:29:FB:10:8F:9E:E5:01:20:D4:DE:79:99:48:83:F7 X509v3 Subject Key Identifier: E2:7C:7C:F8:A8:67:AF:C4:82:C3:9C:75:29:E3:68:CE:52:F2:03:6F X509v3 Subject Alternative Name: DNS:*.opensuse.org, DNS:opensuse.org X509v3 Key Usage: critical Digital Signature, Key Encipherment X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 CRL Distribution Points: Full Name: URI:http://crl3.digicert.com/ca3-g3.crl Full Name: URI:http://crl4.digicert.com/ca3-g3.crl X509v3 Certificate Policies: Policy: 2.16.840.1.114412.1.1 CPS: http://www.digicert.com/ssl-cps-repository.htm User Notice: Explicit Text: Authority Information Access: OCSP - URI:http://ocsp.digicert.com CA Issuers - URI:http://cacerts.digicert.com/DigiCertHighAssuranceCA-3.crt X509v3 Basic Constraints: critical CA:FALSE Signature Algorithm: sha1WithRSAEncryption bd:2f:fd:a7:e3:1e:c2:7e:8c:19:58:cc:2d:c7:fa:b0:60:0b: 81:94:5e:1e:3d:94:96:ae:2d:0f:c3:1c:21:6a:ad:2b:1e:dc: 40:2b:ee:52:8b:0b:f4:83:d5:68:3e:7e:70:05:50:c3:41:ab: 61:ed:4b:2b:f0:a0:32:6e:51:52:53:ae:79:37:46:27:a0:b3: d9:f6:68:bd:02:df:7a:a2:1d:f9:a9:5e:70:1e:17:d3:1f:69: a5:3a:95:31:27:e2:aa:f8:94:12:02:3d:d2:93:7e:ae:e8:5b: 94:06:a7:97:49:50:d4:e9:23:52:d6:64:c1:5f:af:ed:d7:9f: cc:54:db:d9:ce:e9:93:1c:4a:6d:8a:76:ed:32:22:cf:d6:67: a9:1a:82:5c:2d:ab:44:d4:50:b8:c0:2b:95:24:f6:be:72:b1: 82:5d:b6:2c:fa:42:55:4e:a4:59:a9:74:f0:6c:ed:a2:ab:e3: 47:f3:a4:aa:a3:fa:91:cc:7a:db:80:64:cc:2e:54:2d:9b:53: ab:74:41:84:3b:d5:2a:1f:86:39:09:7d:5d:b8:40:83:b0:77: 5f:d2:d8:88:ee:9f:64:25:75:5e:ac:2c:50:c3:61:e4:4a:bd: 51:57:57:16:32:e9:cf:a7:54:3f:b8:f2:00:4a:fa:18:5a:2f: a4:f2:ec:b6 It seems surprising that the cert for opensuse.org is not recognized on an opensuse.org machine. My .oscrc says: [general] apiurl = https://api.opensuse.org su-wrapper = sudo extra-pkgs = vim ncurses-utils build_repository = openSUSE_12.2 Version of ca-certificates is 1.19-1.1. Any thoughts? -Archie -- 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

2 2

[opensuse-buildservice] OBS for a library, example and directions
by Pablo Speciale 05 Mar '13

05 Mar '13

Hi, Since I am new with obs, I am asking for some directions. Questions: * Which is the status of the proposed workflow for git: http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSupport * In case of using the separated workflow, is there an easy way to add/delete files using the information of the new tarball? Assuming the building dependencies are the same, the only difference would be these changes (adding/deleting files, if I understand correctly). For adding, I think I could use something extreme like: osc add `find .`. But for deleting... it may be more complicated. * Is there an example of a package which use cmake? Particularly, I would like to have an example for a library. * For a ubuntu package, for example, will the system generated a repository with all the dependencies ready and possible to be added as a repository into /etc/apt/sources.list? Or will the user need to install all the dependency manually? What about the unnecessary dependencies (like packages that are already in default repositories)? Sorry but I couldn't find this information in the wiki. Another option could be something similar to: "Create Patterns" (but for Ubuntu, and other distributions). http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Create_Patterns Best regards, and thanks in advance! -- Spe -- Spe -- 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] KIWI image build on OBS creates endless loop
by Carsten Schoene 04 Mar '13

04 Mar '13

Hello, i'm trying to build a small image using kiwi as a base for a later project, i created .kiwi files for each image (net,iso,usb,vmx). The usb & vmx build is running into an endless loop, maybe someone can have a look what the problem may be and can point me to the right direction to fix this. Project: home:netmax:playground:kiwi Package: mini-image-usb & mini-image-vmx Thats the part which is looping: Feb-28 20:11:32 <1> : Increasing disk size by 10M to: 4283M [ 986s] . [ 986s] Feb-28 20:11:32 <1> : EXEC [qemu-img create /usr/src/packages/KIWI-vmx/vmx/mini-image.x86_64-0.0.1.raw 4283M 2>&1] [ 986s] Feb-28 20:11:33 <1> : EXEC [/sbin/losetup -f --show /usr/src/packages/KIWI-vmx/vmx/mini-image.x86_64-0.0.1.raw 2>&1] [ 986s] Feb-28 20:11:33 <1> : EXEC [bash -c "PATH=$PATH:/sbin which parted" 2>&1] [ 986s] Feb-28 20:11:33 <1> : EXEC [bash -c "PATH=$PATH:/sbin which parted" 2>&1] [ 986s] Feb-28 20:11:33 <1> : EXEC [dd if=/dev/zero of=/dev/loop0 bs=512 count=1 2>&1] [ 986s] Feb-28 20:11:33 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 mklabel msdos 2>&1] [ 987s] Feb-28 20:11:33 <1> : EXEC [/usr/sbin/parted -m /dev/loop0 unit s print | head -n 3 | tail -n 1 | cut -f2 -d:] [ 987s] Feb-28 20:11:33 <1> : Disk Sector count is: 8771583 [ 987s] Feb-28 20:11:33 <1> : PARTED input: /dev/loop0 [mkpart primary 2048 8771583] [ 987s] Feb-28 20:11:33 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 2048 8771583 2>&1] [ 987s] Feb-28 20:11:33 <1> : PARTED input: /dev/loop0 [set 1 boot on] [ 987s] Feb-28 20:11:33 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 1 boot on 2>&1] [ 987s] Feb-28 20:11:33 <1> : EXEC [/sbin/kpartx -a /dev/loop0 2>&1] [ 987s] Use of uninitialized value $pdev in concatenation (.) or string at /usr/share/kiwi/modules/KIWIBoot.pm line 5872. [ 987s] Feb-28 20:11:33 <1> : EXEC [blockdev --getsize64 2>&1] [ 988s] Feb-28 20:11:34 <1> : EXEC [sync] [ 988s] Feb-28 20:11:34 <1> : EXEC [sync] [ 988s] Feb-28 20:11:34 <1> : EXEC [kpartx -d /dev/loop0 2>&1] [ 988s] Feb-28 20:11:34 <1> : EXEC [losetup -d /dev/loop0 2>&1] Regards, Carsten

1 1

[opensuse-buildservice] there is 12.3 repo confusion in my home project. How to fix?
by Greg Freemyer 02 Mar '13

02 Mar '13

All, I've given OBS 4 days to build/publish a package edit I made. I'm only trying to test the 12.3 repo, so I don't know if the others are working or not. (I repeat, no specfile / tarball / patch changes in 4 days.) The 12.3 repo for the package in my home project is showing weird results and I can't install the various sub-packages because zypper claims they don't exist. https://build.opensuse.org/package/show?project=home%3Agregfreemyer%3ATools… Can I somehow force the repo to rebuild on OBS? --- some details -- Per http://software.opensuse.org/package/libewf I have libewf 0.0.0+20130128 in my home project (home:gregfreemyer:Tools-for-forensic-boot-cd package=libewf) Per zypper I don't (and I forced a metadata update right before this) === sudo zypper se -s libewf Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------+------------+----------------------+--------+--------------------------------------------- | libewf | srcpackage | 0.0.0+20120813-45.3 | noarch | home:gregfreemyer:Tools-for-forensic-boot-cd | libewf-debugsource | package | 0.0.0+20120813-2.1.1 | i586 | openSUSE-12.3-Debug | libewf-devel | package | 0.0.0+20120813-2.1.1 | i586 | openSUSE-12.3-Oss i | libewf2 | package | 0.0.0+20120813-2.1.1 | i586 | openSUSE-12.3-Oss | libewf2-debuginfo | package | 0.0.0+20120813-2.1.1 | i586 | openSUSE-12.3-Debug === --- Further there are other missing sub-packages of the overall libewf package. Greg Freemyer Chief Technology Officer Intelligent Avatar Corporation (678) 653-4860 Greg.Freemyer(a)gmail.com http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrie… -- 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] Can we have the old OBS package search back?
by Greg Freemyer 01 Mar '13

01 Mar '13

All, On OBS (the public instance) I'm used to searching for packages (libewf in this case) and getting a list of results. With each result I'm used to seeing the project the specific instance of the package is in. Not anymore. https://build.opensuse.org/search?utf8=%E2%9C%93&search_text=libewf&commit=… Thanks Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4