March 2013 - openSUSE Build Service - openSUSE Mailing Lists

[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