June 2013 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Project config update
by Guillaume Gardet 21 Jun '13

21 Jun '13

Hi, I would like to know when the changes in project config take effect. Because I changed an Hostarch parameter for a given arch but no job is assigned to the worker whereas some packages are scheduled. Regards, Guillaume -- 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] Own instance - "requests" error in WebUI, and rake error
by Matthew Drobnak 20 Jun '13

20 Jun '13

It looks like the cron job is failing: wwwrun@obs01:/srv/www/obs/api> RAILS_ENV=production rake -s jobs:updateissues --trace ** Invoke jobs:updateissues (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute jobs:updateissues rake aborted! Wrong type NilClass. Not allowed! /usr/lib64/ruby/1.8/xmlrpc/create.rb:207:in `conv2value' /usr/lib64/ruby/1.8/xmlrpc/create.rb:230:in `conv2value' /usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `collect' /usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `each' /usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `collect' /usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `conv2value' /usr/lib64/ruby/1.8/xmlrpc/create.rb:118:in `methodCall' /usr/lib64/ruby/1.8/xmlrpc/create.rb:117:in `collect' /usr/lib64/ruby/1.8/xmlrpc/create.rb:117:in `methodCall' /usr/lib64/ruby/1.8/xmlrpc/client.rb:419:in `call2' /usr/lib64/ruby/1.8/xmlrpc/client.rb:410:in `call' /usr/lib64/ruby/1.8/xmlrpc/client.rb:617:in `send' /usr/lib64/ruby/1.8/xmlrpc/client.rb:617:in `method_missing' /srv/www/obs/api/app/models/issue_tracker.rb:54:in `update_issues' /srv/www/obs/api/lib/tasks/delayed_job.rake:17 /srv/www/obs/api/lib/tasks/delayed_job.rake:15:in `each' /srv/www/obs/api/lib/tasks/delayed_job.rake:15 /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:228:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:228:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:223:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:223:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:166:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:159:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/task.rb:152:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:143:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:101:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:101:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:101:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:110:in `run_with_threads' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:95:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:73:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:160:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/lib/rake/application.rb:70:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-10.0.3/bin/rake:33 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Tasks: TOP => jobs:updateissues Anyone have any clues as to why this would be? OBS package versions: wwwrun@obs01:/srv/www/obs/api> rpm -qa |grep obs obs-service-download_files-0.4-34.1.noarch obs-service-source_validator-0.2-22.1.noarch obs-service-cpanspec-0.1-2.2.noarch obs-service-verify_file-0.1-13.1.noarch obs-worker-2.3.8-3.10.noarch obs-productconverter-2.3.8-3.10.x86_64 obs-service-download_src_package-0.2-2.2.noarch obs-api-2.3.8-3.10.x86_64 obs-service-tar_scm-0.2.3-47.1.noarch obs-signd-2.1.5-1.1.x86_64 obs-service-download_url-0.1-13.1.noarch obs-service-extract_file-0.1-6.2.noarch obs-service-set_version-0.2-7.1.noarch obs-source_service-2.3.8-3.10.x86_64 obs-server-2.3.8-3.10.x86_64 obs-utils-2.3.8-3.10.x86_64 obs-service-recompress-0.2-7.1.noarch Any help getting this fixed ASAP would be greatly appreciated. I didn't find anything on the wiki referring to this. Thanks. -Matt -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 2

[opensuse-buildservice] Unpublish a package
by Cristian Morales Vega 19 Jun '13

19 Jun '13

When I created home:RedDwarf/binutils.12.3 and home:RedDwarf/binutils.Factory I forgot to disable publishing. How can I get rid of those packages now? The old builds are still in http://download.opensuse.org/repositories/home:/RedDwarf/openSUSE_12.3/x86_…. I even used wipebinaries, but after the rebuild the packages are still there! -- 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] Password Reset (Own instance)
by Troy Telford 19 Jun '13

19 Jun '13

The TL;DR version: When LDAP isn't being used, what is the suggested/preferred way to reset a user password in an OBS instance? The longer version: I've had an OBS instance for a number of years now, and it has relatively few users. It's setup so the passwords are stored in the database used by OBS. I am not using LDAP, or any other mechanism at this point in time. After upgrading from 2.2 to 2.4, I discovered that I am no longer able to log into the API vhost (for the sake of argument, I'll call it obsapi.default.domain). With version 2.2, I could simply login to the API vhost as an admin, and use its user management to reset a password for a user. Now that I've upgraded to 2.4, I am no longer able to login to the API vhost in a useful way. I still receive the login dialog, and can login... however instead of being taken to a web UI where I can modify the users (as was possible with 2.4), I get something like: This XML file does not appear to have any style information associated with it. The document tree is shown below. <about> <title>Open Build Service API</title> <description>API to the Open Build Service</description> <revision>2.4.0</revision> </about> I'm pretty sure this isn't a bug in anything but how I'm administering OBS. I'm still stuck trying to figure out how to reset this user's forgotten password, as well as other things such as groups, group membership, and so on. Any pointers would be appreciated. Thanks. -- Troy Telford -- 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] Directory Trees
by Michael Lindner 18 Jun '13

18 Jun '13

Hi, Just wanting to bump my previous question again, is it (can it be) possible to commit directory structures of source rather than a tarball? Apologies if this is a naive question. Thanks, 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] Constraints per spec file idea
by Tomáš Chvátal 18 Jun '13

18 Jun '13

Hello guys, I am facing issue with constraints in libreoffice package. We have one package folder with the sources and 10 spec files provided from those. As it is huge beast it has requirement like >=3gb ram and plenty of disk space (10g+ for the build only). With this set of requirements if I set up the constraints it gets imposed on all of those .spec files, even if I would need this only for the libreoffice.spec, because with applied to all it takes ages to get the possible machines to build this. Thus the idea where i could specify in constraints which spec file they are applied to, not just to the whole package. When I am thinking of it maybe there is some way how to exclude the constraint from being in other linked packages, but I dunno if that is possible or how to achieve that. Cheers Tom

3 4

[opensuse-buildservice] GSoC 2013 update for the week ending on 14/06/2013
by Shayon Mukherjee 18 Jun '13

18 Jun '13

Hello folks, So, here is my GSoC 2013 update for the week ending on 14/06/2013 Q. What have I done last week? 1. Finally getting a hang of openSUSE Hermes infrastructure and Testing methods in OBS 2. Met with my mentor each day to discuss daily workings. 3. Discussed technicalities like OBS[api] call structure for the discussion system over the OBS-ml 4. Discussed and learnt from my mentor on ActiveXML workings and how OBS[webui] talks with OBS[api] Q. What am I'm doing this week? 1. Well today onwards the coding period starts. So, firstly I will do some quick fixes and make sure OBS runs smoothly on my system (local api and webui). 2. Next, the plan is to setup the Comments Controller under the OBS[api], this way we will get start on how and where OBS[webui] talks to OBS[api] further. 3. We decided that we wont be using the gem acts_as_commentable_with_threading. As of now I will write up the methods respective methods and migrations from scratch. Q. What I couldn't achieve and Why? 1. Nothing crucial as of yet. Things are still going good :) Feel free to pass on any comments, suggestions, criticism or feedback you got. I am all eyes and ears ;). Important links Trello: https://trello.com/board/discussion-system/51a5ede2db062a7e6f001b7c Cheers! Shayon -- 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] GSoC: Setitng up API calls for OBS Discussion system
by Shayon Mukherjee 17 Jun '13

17 Jun '13

Hello, My mentor and myself have worked on how commenting will work inside OBS[api] and accordingly [webui] talk to [api]. Below mentioned are the calls I am plan on setting up. Examples are provided at most of the areas. GET /source/<project>/_comments?limit=10&offset=0 Arguments: project - Project name Parameter: limit - Limit the number of retrieved comments offset - offset received comments by offset To obtain comments posted for a project Example: <comments project=”home:name” size=”2” limit=”10” offset=”0”> <comment user=”joe” title=”title” id=”0815”> This is a comment </comment> <comment user=”sam” title=”title” id=”0816” parent=”0815”> This is a reply </comment> </comments> POST /source/<project>/_comments Arguments: project - Project name Creating new comment for a project GET /source/<project>/<package>/_comments?limit=10&offset=0 Arguments: project - Project name package - Package name Parameter: limit - Limit the number of retrieved comments offset - offset received comments by offset To obtain comments posted for a package in a project Example: <comments project=”home:name” package=”foo” size=”2” limit=”10” offset=”0”> <comment user=”joe” title=”title” id=”0815”> This is a comment </comment> <comment user=”sam” title=”title” id=”0816” parent=”0815”> This is a reply </comment> </comments> POST /source/<project>/<package>/_comments Creating new comment for a package GET /request/<id>/_comments?limit=10&offset=0 Arguments: id - request id Parameter: limit - Limit the number of retrieved comments offset - offset received comments by offset To obtain comments posted for a request Example: <comments request=”12345” size=”2” limit=”10” offset=”0”> <comment user=”joe” title=”title” id=”0815”> This is a comment </comment> <comment user=”sam” title=”title” id=”0816” parent=”0815”> This is a reply </comment> </comments> POST /request/<id>/_comments Creating new comment for a request If you have something to add or if you feel something isnt the way it is suppose to be. Please let me know your thoughts and comments, and/or if you have any alternative(s) to the same. Thanks Shayon -- 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] osc: reworked plugin mechanism
by Marcus Hüwe 17 Jun '13

17 Jun '13

Hi, last week osc's plugin mechanism was rewritten (for details see below). As a consequence some plugins may need to be adapted in order to work with the upcoming osc release. Currently there's only one known problem and the fix is "trivial": problem: NameError: name 'cmdln' is not defined This problem occurs if you are using the "@cmdln.option" decorator or other stuff from the cmdln module. Adding the following import should fix the problem: "from osc import cmdln" Background: Due to the recently added python3 support some things changed in the osc codebase, most notably is probably the transition from the "print" statement to the "print" function. As a result of this change all plugins would have had to use the new "print" function, too (which is quite intrusive if the plugin developer does not care about python3 support). In order to reduce the required adaptions for the existing plugins the plugin mechanism was "rewritten". An osc package which contains the new plugin code can be found here: http://download.opensuse.org/repositories/devel:/tools:/scm/ If you face additional problems please tell me:) Marcus -- 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 can I delete all packages from obs project at once
by UkJung Kim 17 Jun '13

17 Jun '13

Hi, Is there any way to delete all packages from obs project at once? I'm using following shell script for this but it takes time. for pkg in $(osc ls $obsprj); do osc rdelete $obsprj $pkg -m 'removed' done -- 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] Repository not updated, remove package's rpm not removed
by Sebastian Schubert 17 Jun '13

17 Jun '13

Hi, I have two possibly related issues in my home project: https://build.opensuse.org/project/show?project=home%3Asebschub 1) The openSUSE_12.3 repository has been on the status "Build jobs have been processed, new repository is not yet created" for about a week, while the other repositories update just fine. I was hit by the following bug https://bugzilla.novell.com/show_bug.cgi?id=823610 so I really would like to test whether it has been solved. Is there anything that stops the repository to update? 2) I removed the package "emacs-auctex" from my home project because a newer and better version is available in the factory and editor repository. However, the rpm is still available in the repository. How can I get rid of it? Cheers, Sebastian

2 4

[opensuse-buildservice] Open Build Service(OBS) 2.4.3 released
by Adrian Schröter 14 Jun '13

14 Jun '13

Open Build Service(OBS) 2.4.3 just got released =============================================== Another bugfix release of the 2.4 series is out there. This version fixes an issue in webui which can lead to lost admin rights when editing the user account. Also the general usability of the Download On Demand feature has been made possible (still experimental feature which is likely to change). Find more fixes and details in the release notes below. OBS 2.4.3 is published in "OBS:Server:2.4" project: http://download.opensuse.org/repositories/OBS:Server:2.4/ Appliances can be used as usual: http://openbuildservice.org/download/ >From the official release notes: Feature backports: ================== * none Changes: ======== * api: support default targets on OBS 2.5 remote instances using defined architecture per repositories Bugfixes: ========= * webui: fix for user editing could have dropped admin role * api: documentation fixes * api: fix storage of Download on Demand path in API (Note: this is still an experimental feature likely to change) * api: crash fixed when request status includes repository pathes to remote instances * api: allow request state change to approved only from new/review states (regression fix) * backend: fix scanprjbinaries event handling * backend: fixed caching for remote source handling in some cases * backend: undelete of a project does restore the signkey now * backend: fixed macro block parsing when using %if statements -- Adrian Schroeter email: adrian(a)suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] How to copy a particular package revision
by Ruediger Meier 14 Jun '13

14 Jun '13

Hi, I will never understand it. I want to do such simple thing like cloning rev.27 of Base:System/quota I've tried osc copypac -r27 Base:System/quota home:rudi_m/quota osc copypac -c -r27 Base:System/quota home:rudi_m/quota osc linkpac -r27 Base:System/quota home:rudi_m but I always get either the most recent revision or merge conflicts(!?). cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] OBS and firewall
by Guillaume Gardet 12 Jun '13

12 Jun '13

Hi, I would like to know what to allow in SuSEFirewall2 for obs-server and obs-worker to get it working. The most tricky parts seems to be RPC, not TCP ports. Guillaume -- 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] licensedigger 503 error
by Dmitry Roshchin 12 Jun '13

12 Jun '13

I have 503 error for licensedigger: https://build.opensuse.org/request/show/175895 {"reject": "source: HTTP Error 503: Service Temporarily Unavailable: no such package?; info/parse=1 of science kicad has no license string; info/parse=1 of science kicad has no version number"}  Is it possible to do something? -- 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] Site not responding
by Michael Lindner 12 Jun '13

12 Jun '13

Hi, I can access build.opensuse.org but my home project keeps timing out. Is there downtime scheduled again? I created a dummy account with a different browser - same. Thanks, Michael. -- 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] 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] "You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'"
by cheyw 11 Jun '13

11 Jun '13

Hi,All I get a problem when debug OBS server. ----------------------------------------------------------------------------------------------- EVR( System : Opensuse 12.3 (x86-64) Version of OBS : 2.4 Repo of OBS Server : http://download.opensuse.org/repositories/OBS:/Server:/2.4/openSUSE_12.3/ Version of ruby : ruby-1.9.3-15.2.1.x86_64 Version of debug(gem):debugger (1.6.0) debugger-linecache (1.2.0) debugger-ruby_core_source (1.2.2) ruby-debug-base19 (0.11.26) ruby-debug-ide (0.4.16) ruby-debug19 (0.11.6) Version of rails : rubygem-rails-3_2-3.2.12-44.2.x86_64 Command : ./script/rails server -e production -p 5555 -u Location : /srv/www/obs/webui/ Fail log : "=> Booting WEBrick => Rails 3.2.12 application starting in production on http://0.0.0.0:5555 => Call with -d to detach => Ctrl-C to shutdown server You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug' Exiting" -------------------------------------------------------------------------------------------- How can I do ? Thanks :) BRs cheyw -- View this message in context: http://opensuse.14.x6.nabble.com/You-need-to-install-ruby-debug-to-run-the-… 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

3 8

[opensuse-buildservice] Build service Ajax server down
by Dirk Müller 11 Jun '13

11 Jun '13

Hi, No live log available: connect: Connection refused on any log file.. Thanks, 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] [Errno 14] HTTP Error 400: connect Connection refused
by Cristian Rodríguez 10 Jun '13

10 Jun '13

Hi: I cannot build any packages today, the OBS returns. Trying openSUSE Build Service server for rpmlint-mini (openSUSE:Factory), not found at download.opensuse.org. preparing download ... -- GET https://api.opensuse.org/build/openSUSE:Factory/snapshot/i586/_repository?b… send: 'GET /build/openSUSE:Factory/snapshot/i586/_repository?binary=post-build-checks&binary=rpmlint-mini&binary=rpmlint-Factory&view=cpio HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: api.opensuse.org\r\nConnection: close\r\nUser-agent: osc/0.139\r\n\r\n' reply: 'HTTP/1.1 400 connect Connection refused\r\n' header: Date: Mon, 10 Jun 2013 20:31:31 GMT header: X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.19 header: X-Opensuse-APIVersion: 2.4.50_98_gbd5d416 header: X-Opensuse-Runtimes: {"view":null,"db":12.460779000000002,"backend":0,"xml":0} header: ETag: "7215ee9c7d9dc229d2921a40e899ec5f" header: Cache-Control: must-revalidate, private, max-age=0 header: X-Request-Id: 9c4571e0cafba41e76967eda03b07eca header: X-Runtime: 0.022806 header: X-Rack-Cache: miss header: Content-Type: text/xml header: Cache-Control: no-cache header: Content-Length: 79 header: Connection: close Traceback (most recent call last): File "/usr/bin/osc", line 22, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 53, in run return prg.main() File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 310, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 333, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 449, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1179, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 5376, in do_build return osc.build.main(self.get_api_url(), opts, args) File "/usr/lib/python2.7/site-packages/osc/build.py", line 701, in main fetcher.run(bi) File "/usr/lib/python2.7/site-packages/osc/fetch.py", line 247, in run self.__fetch_cpio(buildinfo.apiurl) File "/usr/lib/python2.7/site-packages/osc/fetch.py", line 150, in __fetch_cpio self.__download_cpio_archive(apiurl, project, repo, arch, package, **pkgs) File "/usr/lib/python2.7/site-packages/osc/fetch.py", line 106, in __download_cpio_archive self.gr.urlgrab(url, filename = tmparchive, text = 'fetching packages for \'%s\'' % project) File "/usr/lib/python2.7/site-packages/osc/fetch.py", line 51, in urlgrab raise exc urlgrabber.grabber.URLGrabError: [Errno 14] HTTP Error 400: connect Connection refused -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[fix 2 typos] Re: [Fwd: Re: [opensuse-buildservice] peazip bug report]
by Sérgio Basto 10 Jun '13

10 Jun '13

Hi, Peazip 4.9.1 also doesn't work that why I updated. If OBS doesn't use fedora updates repo in default repo , is wrong because should use it definitively . Also I'm not sure that will fix Peazip (building with lazarus-1.0.4-1.fc18) :/ Best regards, On Seg, 2013-06-10 at 23:13 +0800, Huaren Zhong wrote: > AFAIK, OBS does not update packages in default repo. > Rebuilding another lazarus package in local repo is also > not a good idea... > Maybe stay on peazip 4.9.1 and wait till FC19 to update? > > 2013/6/10 Sérgio Basto <sergio(a)serjux.com> > Hi, FYI if you don't read opensuse-buildservice ML. > builder does not use repo updates ? could we change it ? > > Thanks, > > -------- Forwarded Message -------- > From: Sérgio Basto <sergio(a)serjux.com> > To: Jan Engelhardt <jengelh(a)inai.de> > Cc: opensuse-buildservice <opensuse-buildservice(a)opensuse.org> > Subject: Re: [opensuse-buildservice] peazip bug report > Date: Mon, 10 Jun 2013 12:21:14 +0100 > > On Sáb, 2013-06-08 at 18:43 +0100, Sérgio Basto wrote: > > On Sáb, 2013-06-08 at 17:29 +0200, Jan Engelhardt wrote: > > > On Saturday 2013-06-08 17:04, Sérgio Basto wrote: > > > > > > >> >yum --enablerepo=home_zhonghuaren update > > > >> >(...) > > > >> >Updated: > > > >> > libcaca.x86_64 0:0.99.beta18-13.1 peazip.x86_64 > 0:4.9.2-2.1 > > > >> >po-debconf.noarch 0:1.0.16-4.1 > > > >> > > > > >> >peazip > > > >> >[FORMS.PP] ExceptionOccurred > > > >> > Sender=EReadError > > > >> > Exception=Error reading mback.ShortCutKey2: Unknown > property: > > > >> >"ShortCutKey2" > > > >> > Stack trace: > > > >> > > > > >> >but with same src.rpm built on fedora with mock runs > without errors , > > > >> >and works pretty well. > > > >> > > > >> As you can see, that is a _YUM_ problem, not a building > problem. > > > > > > > >No, is a binary problem, after yum install or update > peazip, the binary > > > >works different (with errors) build on OBS , is not > supposed to work on > > > >Fedora 18 ? > > > > > > > > > http://code.google.com/p/peazip/issues/detail?id=230 > > > > I diff [1] my build and opensuse build and just see this > difference : > > -NOTE: miscellaneous options file not found - using defaults > > +primary config path: /builddir/.lazarus > > > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/ -a > > . .. .bash_logout .bash_profile .bashrc build > .lazarus .rpmmacros > > > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/ -a > > . .. compilertest.pas environmentoptions.xml > > > > > cat /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/environmentoptions.xml > > [2] > > > > [1] > > wget > > > "https://build.opensuse.org/package/rawlog?arch=x86_64&package=peazip&projec…" -O build.log > > cat build.log | perl -pe 's/\[.*?\] //' > build2.log > > diff > build2.log /var/lib/mock/fedora-18-x86_64/result/build.log > -ubBw > > > diffbuild.txt > > http://www.serjux.com/diffbuild.txt > > > > [2] > > <?xml version="1.0"?> > > <CONFIG> > > <EnvironmentOptions> > > <Version Value="107" Lazarus="1.0.4"/> > > <LazarusDirectory Value="/usr/lib64/lazarus"> > > <History Count="1"> > > <Item1 Value="/usr/lib/lazarus/"/> > > </History> > > </LazarusDirectory> > > <CompilerFilename Value="/usr/bin/fpc"> > > <History Count="3"> > > <Item1 Value="/usr/local/bin/fpc"/> > > <Item2 Value="/usr/bin/fpc"/> > > <Item3 Value="/opt/fpc/fpc"/> > > </History> > > </CompilerFilename> > > <FPCSourceDirectory Value="/usr/share/fpcsrc"> > > <History Count="2"> > > <Item1 Value="/usr/share/fpcsrc/"/> > > <Item2 Value="/usr/share/fpcsrc/$(FPCVER)/"/> > > </History> > > </FPCSourceDirectory> > > <MakeFilename> > > <History Count="1"> > > <Item1 Value="/usr/bin/make"/> > > </History> > > </MakeFilename> > > <TestBuildDirectory Value="/tmp/"> > > <History Count="2"> > > <Item1 Value="/tmp/"/> > > <Item2 Value="/var/tmp/"/> > > </History> > > </TestBuildDirectory> > > </EnvironmentOptions> > > </CONFIG> > > [295/295] installing lazarus-0.9.30.4-2.fc18 > against in /var/lib/mock/fedora-18-x86_64/result/root.log > Installing: > lazarus x86_64 1.0.4-1.fc18 > updates > > I try to force use lazarus >= 1.0.4 > with BuildRequire but got in OBS: > unresolvable nothing provides lazarus >= 1.0.4 > well > on my Fedora 18 > yum list lazarus > Available Packages > lazarus.x86_64 1.0.4-1.fc18 updates > > > Thanks, > -- > Sérgio M. B. > > -- > To unsubscribe, e-mail: opensuse-buildservice > +unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-buildservice > +owner(a)opensuse.org > > > -- > Sérgio M. B. > > -- Sérgio M. B. -- Sérgio M. B. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

Re: [Fwd: Re: [opensuse-buildservice] peazip bug report]
by Sérgio Basto 10 Jun '13

10 Jun '13

Hi, Peazip 4.9.1 also doesn't work that why I updated. If OBS does use update repo in default repo , is wrong should use it definitively . Also I'm not sure that is the fix (use lazarus-1.0.4-1.fc18) :/ Best regards, On Seg, 2013-06-10 at 23:13 +0800, Huaren Zhong wrote: > AFAIK, OBS does not update packages in default repo. > Rebuilding another lazarus package in local repo is also > not a good idea... > Maybe stay on peazip 4.9.1 and wait till FC19 to update? > > 2013/6/10 Sérgio Basto <sergio(a)serjux.com> > Hi, FYI if you don't read opensuse-buildservice ML. > builder does not use repo updates ? could we change it ? > > Thanks, > > -------- Forwarded Message -------- > From: Sérgio Basto <sergio(a)serjux.com> > To: Jan Engelhardt <jengelh(a)inai.de> > Cc: opensuse-buildservice <opensuse-buildservice(a)opensuse.org> > Subject: Re: [opensuse-buildservice] peazip bug report > Date: Mon, 10 Jun 2013 12:21:14 +0100 > > On Sáb, 2013-06-08 at 18:43 +0100, Sérgio Basto wrote: > > On Sáb, 2013-06-08 at 17:29 +0200, Jan Engelhardt wrote: > > > On Saturday 2013-06-08 17:04, Sérgio Basto wrote: > > > > > > >> >yum --enablerepo=home_zhonghuaren update > > > >> >(...) > > > >> >Updated: > > > >> > libcaca.x86_64 0:0.99.beta18-13.1 peazip.x86_64 > 0:4.9.2-2.1 > > > >> >po-debconf.noarch 0:1.0.16-4.1 > > > >> > > > > >> >peazip > > > >> >[FORMS.PP] ExceptionOccurred > > > >> > Sender=EReadError > > > >> > Exception=Error reading mback.ShortCutKey2: Unknown > property: > > > >> >"ShortCutKey2" > > > >> > Stack trace: > > > >> > > > > >> >but with same src.rpm built on fedora with mock runs > without errors , > > > >> >and works pretty well. > > > >> > > > >> As you can see, that is a _YUM_ problem, not a building > problem. > > > > > > > >No, is a binary problem, after yum install or update > peazip, the binary > > > >works different (with errors) build on OBS , is not > supposed to work on > > > >Fedora 18 ? > > > > > > > > > http://code.google.com/p/peazip/issues/detail?id=230 > > > > I diff [1] my build and opensuse build and just see this > difference : > > -NOTE: miscellaneous options file not found - using defaults > > +primary config path: /builddir/.lazarus > > > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/ -a > > . .. .bash_logout .bash_profile .bashrc build > .lazarus .rpmmacros > > > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/ -a > > . .. compilertest.pas environmentoptions.xml > > > > > cat /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/environmentoptions.xml > > [2] > > > > [1] > > wget > > > "https://build.opensuse.org/package/rawlog?arch=x86_64&package=peazip&projec…" -O build.log > > cat build.log | perl -pe 's/\[.*?\] //' > build2.log > > diff > build2.log /var/lib/mock/fedora-18-x86_64/result/build.log > -ubBw > > > diffbuild.txt > > http://www.serjux.com/diffbuild.txt > > > > [2] > > <?xml version="1.0"?> > > <CONFIG> > > <EnvironmentOptions> > > <Version Value="107" Lazarus="1.0.4"/> > > <LazarusDirectory Value="/usr/lib64/lazarus"> > > <History Count="1"> > > <Item1 Value="/usr/lib/lazarus/"/> > > </History> > > </LazarusDirectory> > > <CompilerFilename Value="/usr/bin/fpc"> > > <History Count="3"> > > <Item1 Value="/usr/local/bin/fpc"/> > > <Item2 Value="/usr/bin/fpc"/> > > <Item3 Value="/opt/fpc/fpc"/> > > </History> > > </CompilerFilename> > > <FPCSourceDirectory Value="/usr/share/fpcsrc"> > > <History Count="2"> > > <Item1 Value="/usr/share/fpcsrc/"/> > > <Item2 Value="/usr/share/fpcsrc/$(FPCVER)/"/> > > </History> > > </FPCSourceDirectory> > > <MakeFilename> > > <History Count="1"> > > <Item1 Value="/usr/bin/make"/> > > </History> > > </MakeFilename> > > <TestBuildDirectory Value="/tmp/"> > > <History Count="2"> > > <Item1 Value="/tmp/"/> > > <Item2 Value="/var/tmp/"/> > > </History> > > </TestBuildDirectory> > > </EnvironmentOptions> > > </CONFIG> > > [295/295] installing lazarus-0.9.30.4-2.fc18 > against in /var/lib/mock/fedora-18-x86_64/result/root.log > Installing: > lazarus x86_64 1.0.4-1.fc18 > updates > > I try to force use lazarus >= 1.0.4 > with BuildRequire but got in OBS: > unresolvable nothing provides lazarus >= 1.0.4 > well > on my Fedora 18 > yum list lazarus > Available Packages > lazarus.x86_64 1.0.4-1.fc18 updates > > > Thanks, > -- > Sérgio M. B. > > -- > To unsubscribe, e-mail: opensuse-buildservice > +unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-buildservice > +owner(a)opensuse.org > > > -- > Sérgio M. B. > > -- Sérgio M. B. -- 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] GSoC 2013 udpate for the week ending on 07/06/2013
by Shayon Mukherjee 10 Jun '13

10 Jun '13

Hello folks, So, here is my GSoC 2013 update for the week ending on 07/06/2013 Q. What have I done last week? 1. Discussed with my mentor and decided on the tasks I need to do to finish the project successfully. So, we know exactly where we are going and what we want to do now. To-do cards can be found on trello. 2. Fixed my technical timeline as promised last week. Discussed the same with my mentor and agreed upon the same. 3. Discussed on the OBS ML about technicalities on how to deal with database data for the discussion to be implemented. 4. Read documents on testing in a rails environment. 5. Deployed Hermes starship on my local development machine. 6. Met with my mentor each day for a daily checkin. Q. What am I'm doing this week? 1. Read more on Unit and functional testing. And compare accordingly how it is done with OBS [webui] and [api]. 2. Look up how webui handles ActiveXML calls. 3. Start spending as much time as possible on understanding how OBS deals with hermes. Make sure I understand the ins and outs and write code the same way it is done now. Which means, do it right :). 4. Meet with my mentor each day for a daily checkin. 5. Lastly, at the end, take a deep breath, fire off some jazz and classical, and let the coding begin from the 17th ;). Q. What I couldn't achieve and Why? 1. Nothing crucial as of yet. Although learning hermes is taking a while. But trying my best to cover the topic as much as possible. Once again, feel free to pass on any comments, suggestions, criticism or feedback you got. I am all eyes and ears ;). Important links Trello: https://trello.com/board/discussion-system/51a5ede2db062a7e6f001b7c Cheers! Shayon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[Fwd: Re: [opensuse-buildservice] peazip bug report]
by Sérgio Basto 10 Jun '13

10 Jun '13

Hi, FYI if you don't read opensuse-buildservice ML. builder does not use repo updates ? could we change it ? Thanks, -------- Forwarded Message -------- From: Sérgio Basto <sergio(a)serjux.com> To: Jan Engelhardt <jengelh(a)inai.de> Cc: opensuse-buildservice <opensuse-buildservice(a)opensuse.org> Subject: Re: [opensuse-buildservice] peazip bug report Date: Mon, 10 Jun 2013 12:21:14 +0100 On Sáb, 2013-06-08 at 18:43 +0100, Sérgio Basto wrote: > On Sáb, 2013-06-08 at 17:29 +0200, Jan Engelhardt wrote: > > On Saturday 2013-06-08 17:04, Sérgio Basto wrote: > > > > >> >yum --enablerepo=home_zhonghuaren update > > >> >(...) > > >> >Updated: > > >> > libcaca.x86_64 0:0.99.beta18-13.1 peazip.x86_64 0:4.9.2-2.1 > > >> >po-debconf.noarch 0:1.0.16-4.1 > > >> > > > >> >peazip > > >> >[FORMS.PP] ExceptionOccurred > > >> > Sender=EReadError > > >> > Exception=Error reading mback.ShortCutKey2: Unknown property: > > >> >"ShortCutKey2" > > >> > Stack trace: > > >> > > > >> >but with same src.rpm built on fedora with mock runs without errors , > > >> >and works pretty well. > > >> > > >> As you can see, that is a _YUM_ problem, not a building problem. > > > > > >No, is a binary problem, after yum install or update peazip, the binary > > >works different (with errors) build on OBS , is not supposed to work on > > >Fedora 18 ? > > > > > > http://code.google.com/p/peazip/issues/detail?id=230 > > I diff [1] my build and opensuse build and just see this difference : > -NOTE: miscellaneous options file not found - using defaults > +primary config path: /builddir/.lazarus > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/ -a > . .. .bash_logout .bash_profile .bashrc build .lazarus .rpmmacros > > ls /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/ -a > . .. compilertest.pas environmentoptions.xml > > cat /var/lib/mock/fedora-18-x86_64/root/builddir/.lazarus/environmentoptions.xml > [2] > > [1] > wget > "https://build.opensuse.org/package/rawlog?arch=x86_64&package=peazip&projec…" -O build.log > cat build.log | perl -pe 's/\[.*?\] //' > build2.log > diff build2.log /var/lib/mock/fedora-18-x86_64/result/build.log -ubBw > > diffbuild.txt > http://www.serjux.com/diffbuild.txt > > [2] > <?xml version="1.0"?> > <CONFIG> > <EnvironmentOptions> > <Version Value="107" Lazarus="1.0.4"/> > <LazarusDirectory Value="/usr/lib64/lazarus"> > <History Count="1"> > <Item1 Value="/usr/lib/lazarus/"/> > </History> > </LazarusDirectory> > <CompilerFilename Value="/usr/bin/fpc"> > <History Count="3"> > <Item1 Value="/usr/local/bin/fpc"/> > <Item2 Value="/usr/bin/fpc"/> > <Item3 Value="/opt/fpc/fpc"/> > </History> > </CompilerFilename> > <FPCSourceDirectory Value="/usr/share/fpcsrc"> > <History Count="2"> > <Item1 Value="/usr/share/fpcsrc/"/> > <Item2 Value="/usr/share/fpcsrc/$(FPCVER)/"/> > </History> > </FPCSourceDirectory> > <MakeFilename> > <History Count="1"> > <Item1 Value="/usr/bin/make"/> > </History> > </MakeFilename> > <TestBuildDirectory Value="/tmp/"> > <History Count="2"> > <Item1 Value="/tmp/"/> > <Item2 Value="/var/tmp/"/> > </History> > </TestBuildDirectory> > </EnvironmentOptions> > </CONFIG> [295/295] installing lazarus-0.9.30.4-2.fc18 against in /var/lib/mock/fedora-18-x86_64/result/root.log Installing: lazarus x86_64 1.0.4-1.fc18 updates I try to force use lazarus >= 1.0.4 with BuildRequire but got in OBS: unresolvable nothing provides lazarus >= 1.0.4 well on my Fedora 18 yum list lazarus Available Packages lazarus.x86_64 1.0.4-1.fc18 updates Thanks, -- Sérgio M. B. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org -- Sérgio M. B. -- 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] Build service down? (no text)
by Stefan Brüns 10 Jun '13

10 Jun '13

Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3