June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Setup OBS to point on MeeGo repo (or any remote repo)
by Dominig ar Foll (Intel OTC) 15 Jun '11

15 Jun '11

Hi, I have installed a local OBS and I try to get it to offer to its user the option to build against the MeeGo repo.<br> Under Admin login, I use the Setup OBS button to create a link to the public MeeGo api.<br> My project is well created but when I try to build against the MeeGo project I do not see the list of the project which are available on the MeeGo OBS. In my case the Raw config shows : <project name="Meego-official"> <title>Link to public MeeGo OBS</title> <description>This project is representing a remote build service instance or official MeeGo</description> <remoteurl>https://api.meego.com/public</remoteurl> <person userid="Admin" role="maintainer"/> <person userid="Admin" role="bugowner"/> </project> I can manually create a build on any project hosted on MeeGo.com but I would like to create an easy web page in which list the various projects from MeeGo.com Where could I find the instruction to add MeeGo distro on the landing page when the user click on select build target ? Thanks. -- Dominig -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] [Seeking Feedback] OBS mobile: request page makeover
by Justine Leng 14 Jun '11

14 Jun '11

Greetings, Hope all is well. :) I'm a GSoC'11 student working on the OBS mobile client for Android, and I have a few ideas about improving the Request page. I figured some feedback from the community would be very helpful, especially from those who use OBS regularly. (A blog discussion & more vivid visual illustration of this can be found at: http://obsforandroid.wordpress.com/2011/06/09/obs-mobile-request-page -makeover/ ) At this moment, when we open up the OBS mobile and click on Requests, it takes us directly to the list of requests (http://img.susepaste.org/64883370). How would it look if we were to replace the list with some buttons on this page, e.g., View All Requests, Add Request, Search (http://img.susepaste.org/48027969)? Do you think this is a good place to Add Requests? I heard that new requests were often related to packages, so I wonder if it might make more sense to place "Add Requests" on the Package view page. Would it be useful to have a Search button here? So, when a user taps "View All Requests," the screen would slide over to display the entire list of requests (http://img.susepaste.org/95818729). I was thinking about adding some sorting functions here to show an ordered list of requests. Should the list be automatically sorted alphabetically or chronologically upon loading, or should there be some buttons on the page which the user could tap and sort himself/herself? How about a sort based on the request's status, e.g., accepted, declined, pending? Then, when the user taps on a specific request, instead of showing the original 3 collapsible functions (http://img.susepaste.org/77504424), the screen displays 4 collapsible buttons: Actions, Info, History, and Diff. (http://img.susepaste.org/95372228) Tapping the Actions button will expand it to display the 4 possible actions on a request: Accept, Decline, Modify, and Delete. (http://img.susepaste.org/67877982) How does this look? Is it more convenient & user-friendly? Also, do you think we should implement a mobile view for https://build.opensuse.org/home/my_work, for a better makeover of this Request page? Your comments and suggestions are always welcome! :) Best regards, ~ Justine -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] ERROR: source-validator failed
by Ciro Iriarte 14 Jun '11

14 Jun '11

Hi, is it possible to disable the source validator?, I'm referencing a source file included in another package using a _link file and because of this the validator is complaining at commit time... Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] error in OBS security:chipcard/libchipcard
by Nico Kruber 13 Jun '11

13 Jun '11

The following error occurred after my sr got accepted - the package was building fine in my branch though... security:chipcard/libchipcard/94e09d942cf1e858a76f855df686cef8: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Can somebody check and fix whatever happened there? see https://build.opensuse.org/package/show?package=libchipcard&project=securit… Regards Nico Kruber

1 0

[opensuse-buildservice] Virtualizing OBS worker build environment with OpenVZ or LXC
by Ville.Seppanen＠tieto.com 13 Jun '11

13 Jun '11

Greetings, Is there any work being done for OpenVZ, LXC or other OS-level virtualization support for the build environment in OBS? I am doing my Master's thesis on extending OBS to the cloud. Seeing that Amazon Web Services uses Xen for virtualization (and thus does not support Xen/KVM inside it), and that building without a sandboxed environment is not safe, OpenVZ and LXC would seem promising. There's also much talk about using these technologies in AWS, so I would see it possible. Best Regards, Ville Seppänen Tieto Corporation -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] latest api migration fails
by Robert Xu 13 Jun '11

13 Jun '11

Hi all, running rake db:migrate on the latest obs-api yields this message: undefined method `pass' for #<ActiveRecord::ConnectionAdapters::MysqlAdapter:0x7effb0186198> /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:352:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:352:in `method_missing' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:348:in `method_missing' ./db/migrate//20110609083665_create_configurations.rb:7:in `up_without_benchmarks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `__send__' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:491 /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `ddl_transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:490:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:401:in `up' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:383:in `migrate' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/databases.rake:112 /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 -- later, Robert Xu + rxu AT lincomlinux DOT org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] can't access?
by Robert Xu 12 Jun '11

12 Jun '11

Anyone else getting this while accessing https://build.opensuse.org? Forbidden You don't have permission to access / on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.2.10 (Linux/SUSE) Server at build-internal.opensuse.org Port 7002 -- later, Robert Xu + rxu AT lincomlinux DOT org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Problem with a package...
by Nelson Marques 10 Jun '11

10 Jun '11

Hi all, I'm having a small issue with one package. I've made a test package on Banshee:Unstable/banshee with some changes that are required for this new release of banshee. One of it's dependencies is dbus-sharp-glib which is provided in the Banshee repository (Banshee:Unstable inherits those packages to build). Now I'm facing a very strange issue here... dbus-sharp-glib-devel does include a Requires in the spec to pull the original package which provides the libraries... but on OBS builds that package isn't pulled... And if I enter a BuildRequires: dbus-sharp-glib (to force it to install that package), the local build works (osc build Banshee_openSUSE_11.4 --local-package) without issues, but if I commit it, it fails with this error: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/Banshee:Unstable/openSUSE_Factory+Banshee/18969219…' /usr/src/packages/SOURCES/banshee.spec error: Failed build dependencies: dbus-sharp-glib is needed by banshee-2.1.0-11.1.i586 Anyone has some ideas about this? For some strange reason OBS is unable to pick up that package. NM -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] ccache in the OBS somehow ?
by Cristian Rodríguez 10 Jun '11

10 Jun '11

Hi: I maintain and have seen some packages that may benefit from ccache installed in the OBS buildmachine, because the build process compiles in a loop different targets that share a large amount of code. Is there anyway to tell in the prjconf to "use ccache" ? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 3
by Marcus Hüwe 10 Jun '11

10 Jun '11

Hi, here's a small summary of the 3rd (coding) week. This week I spent most of my time with developing the remote model classes. The goal was to put most of the code into a base class from which all remote models will be derived (if you're interested how it works have a look at [1]). So far we have classes for: * a remote project (RemoteProject - manages project metadata) * a remote package (RemotePackage - manages package metadata) * a request (Request) TODO for this week: * add exception handling to the httprequest.py module * add a RemoteFile class which can be used to access a remote file like a buildlog, prjconf or a source file * add a BuildResult class: - get the build results for a project or package - get the buildlog of a package - get the binary/binaries from the api Marcus [1]: https://gitorious.org/osc2/osc2/blobs/master/osc/remote.py -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0