March 2006 - openSUSE Build Service - openSUSE Mailing Lists

opensuse-commander
by Dr. Peter Poeml 11 May '06

11 May '06

Hi, I want to share with you a primitive script which allows copying files from and to the buildservice server. It is probably similar (and likely inferiour) to the opensuse-commandline tool from Christopher Hofmann http://build.opensuse.org/package/show?package=opensuse-commandline&project… and the primary reason I didn't build on it is that it wasn't accessible at the time I wanted to try it out ;) However, I also like the idea of having the functionality in a python library. It can be found here, and if anyone wants to extend it please contact me to get write access: http://svn.poeml.de/svn/osc http://svn.poeml.de/viewcvs/osc/ To explain what's currently implemented, here are usage examples: # list contents opensuse-commander.py ls opensuse-commander.py ls Apache opensuse-commander.py ls Apache subversion # show xml meta opensuse-commander.py meta Apache opensuse-commander.py meta Apache subversion opensuse-commander.py id username # check out sources mkdir subversion cd subversion opensuse-commander.py co Apache subversion [file] vi *.spec opensuse-commander.py diff Apache subversion [file] opensuse-commander.py ci Apache subversion file1 [file2...] (I hope I got that right, it is partly from memory) Regards, Peter -- SUSE LINUX Products GmbH Thought is limitation. Research & Development Free your mind.

3 5

open source development model
by Robert Schiele 22 Mar '06

22 Mar '06

Hi everybody! In my opinion there is still a big problem with the open source development model that is used for the build service: If you want to attract external developers to work on that project then you should put _everything_ you plan to release as open source _as early as possible_ to the public svn repository (i.e. _now_). You should even do this if the code you are hacking is incomplete and unusable. I mean a public repository is no shop window for doing marketing but something to coordinate development work. If you always wait putting stuff into public visibility until you consider it having reached a certain level of completeness, you might impress some people that want to use the tool but you are unlikely to attract external developers. There should never be such comments in the repository like "to be checked in by xxx next week" because if you check it in _now_ even when it is incomplete, potential external developers could see it growing and later start to contribute. If you again wait with releasing it until it has grown fat and ugly, potential developers will be scared away because reading and understanding other's code needs some time. If external developers get the impression that they are always trying to understand code that was already obsoleted by other code that the internal developer is currently working on (again behind the curtain) then (s)he is likely to lose interest in working on that project. If you have legal problems to release something, then _explain_ the situation and don't leave the situation that you don't take your plan to run an _open_ project serious. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."

6 10

API test tool
by Cornelius Schumacher 21 Mar '06

21 Mar '06

I have checked in a tool for testing that the API conforms to the specification. It's called rest_test and it's in trunk/buildservice/docs/api. Instructions how to use it are in trunk/buildservice/docs/api/README.rest_test. For testing the openSUSE API you call it with "rest_test api.txt". You have to provide a file "api.txt.test.config" with some login information (details are in the README), otherwise all tests will fail with a 401. The currently deployed API doesn't pass all tests, mainly because the response to PUT operations doesn't adhere to the specified schema. This is fixed in SVN and will become active with the next deploy of the frontend. If you parse the XML returned as result of the PUT requests you probably will have to adapt the client to the correct schema. -- Cornelius Schumacher <cschum(a)suse.de>

1 0

web client error when adding file to package
by Sonja Krause-Harder 20 Mar '06

20 Mar '06

Hi, on my local setup I encountered the following error when adding files to a package with the web client: (from src/webclient/log/development.log) rescue_action_in_public: caught NoMethodError: undefined method `file' for #<Package:0xb7576d20> default exception handling Rendering layoutfalsestatus500templateerror within layouts/application Rendering error (500) The error goes away with the following patch: skh@linux-4:/local/opensuse/buildservice/src/webclient/app/controllers> svn diff package_controller.rb Index: package_controller.rb =================================================================== --- package_controller.rb (revision 55) +++ package_controller.rb (working copy) @@ -107,6 +107,9 @@ end filetype = params[:filetype] + logger.debug "controller: starting to add file: #{filename}" + @package.add_file :file => file, :filename => filename, :filetype => filety pe + if @package.file("@filename='#{filename}'") @package.remove_file filename flash_message = "File '#{filename}' replaced successfully" @@ -114,10 +117,7 @@ flash_message = "File '#{filename}' added successfully" end - logger.debug "controller: starting to add file: #{filename}" - @package.add_file :file => file, :filename => filename, :filetype => filety pe - - if @package.save_files and @package.save + if @package.save_files and @package.save flash[:note] = flash_message else flash[:note] = "Failed to add file '#{filename}'" I'm very puzzled that build.opensuse.org doesn't show the same error. cheers, Sonja -- Sonja Krause-Harder (skh(a)suse.de) Research & Development SUSE Linux Products GmbH

2 2

Update of active rbac
by Klaas Freitag 17 Mar '06

17 Mar '06

Hi, today I commited a larger junk of code to the frontend svn. I commited an update of active rbac. Active rbac is (now) a rails engine that provides full featured user management with permissions, roles, groups. We are using that in the frontend for user management and it turned out to be really powerfull so far. The update today was neccessary because a new version of active rbac came out that fixed of course some bugs but also has another advantage: While it was a component before it is an engine now. That's cooler - and I am sure the rails gurus can explain why if required ;-)) While digging through this topic I created the object BSUser that inherits from the rbac-provided User object. Now we can add user stuff more easy and do not have to change the rbac code what we had before. One thing that needs to be done along with this change: The column user_id of the watched_projects table needs to be renamed to bs_user_id. That can be either done by a complete renew of the database or by only deleting the table watched_projets and recreate it using the lines from frontend/db/create_mysql.sql have fun, Klaas -- Klaas Freitag Novell - SUSE R&D - Internal Tools

1 0

MBOX for buildservice-List
by Johannes Kastl 17 Mar '06

17 Mar '06

Hello, I missed the start of the buildservice-Mailinglist. Has anyone got a full archive of the mailinglist? And can send it to me as mbox? Thanks, OJ -- `And Ginny, don't call Ron a prat, you're not captain of this team -? `Well you seemed to busy to call him a prat and I thought someone should -? (Harry Potter and Ginny Weasley in Harry Potter 6)

1 0

Adding co-maintainers bug?
by Will Stephenson 15 Mar '06

15 Mar '06

I've added the Kopete project's resident Debian whiz, andred, to the Kopete project and Kopete package as a maintainer, but he complains that he can't add files or make other changes - have we found a bug? Will

2 2

IMPORTANT: SVN changes
by Sonja Krause-Harder 15 Mar '06

15 Mar '06

Hi, The SVN repositories have been migrated to a new server. The official announcement of this can be found at: http://forge.novell.com/pipermail/forge-svn/2006-March/000039.html The most important impact of this change is that anonymous checkout with svn+ssh does no longer work, but result in a "Permission denied" error. If you have a local repository, you need to switch it to the new server, and to using the https protocol with the following command: $ svn switch --relocate \ svn+ssh://anonymous@forgesvn1.novell.com/svn/opensuse/trunk/buildservice \ https://forgesvn2.novell.com/svn/opensuse/trunk/buildservice For new checkouts use this command: $ svn checkout \ https://anonymous@forgesvn2.novell.com/svn/opensuse/trunk/buildservice I'll update the documentation in the wiki now. Sorry for the inconvenience, Sonja -- Sonja Krause-Harder (skh(a)suse.de) Research & Development SUSE Linux Products GmbH

3 5

package build looping
by Dr. Peter Poeml 13 Mar '06

13 Mar '06

Hi buildservice hackers, I have created a package "libapr-util1" in a project named Apache. This package keeps builds again and again (status "building"). Another package depending on it ("apache2") never builds, it seems to wait (although it is in state "unknown"). Did I mess something up? Is it a bug? Regards, Peter -- SUSE LINUX Products GmbH Thought is limitation. Research & Development Free your mind.

2 1

How to get an account
by Joop Boonen 13 Mar '06

13 Mar '06

All, At FOSDEM was told you can use your normal bugzilla account on the build service. THis doesn't seem to work. According to the instructions you need to request for an account. I did this a tuesday but i didn't get an answer. Am i doing something wrong? Regards, Joop Boonen.

3 4