January 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Another services error
by Cristian Morales Vega 23 Jan '11

23 Jan '11

At this point I'm not sure if this helps. It's my understanding that it's already known that service aren't 100% reliable. But yesterday someone wrote http://forums.opensuse.org/english/other-forums/development/opensuse-build-… and now I'm finding the same error in https://build.opensuse.org/package/show?package=scummvm-tools&project=games -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] OBS Web Interface Error: Errorcode: unknown - Message: undefined method `name' for "home:XXXX":String
by doiggl＠velocitynet.com.au 23 Jan '11

23 Jan '11

Hello, I tried to remove a file from a package using the obs gui , I got this error Unsure if its related to [1] OBS Web Interface Error: Error Details: Errorcode: unknown Message: undefined method `name' for "home:XXXX":String Glenn [1] http://lists.opensuse.org/opensuse-buildservice/2011-01/msg00093.html -- 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] %{buildroot} not expanded in SLES10 and SLES11
by Luiz Antonio Maldonado Marthos 21 Jan '11

21 Jan '11

Hello, I'm trying to make a rpm file and the macro %{buildroot} doesn't expand. I used the eval parameter on the rpm command like this: rpm --define "_topdir %{_tmppath}/libmylib" --eval %{buildroot} And I get in response only %{buildroot} On my spec file, the BuildRoot is set to %{_tmppath}/%{name}-%{version}-%{release} I use this same command on others distros, like mandriva, and I get the macro expanded. Any ideas what is going on? -- 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] How can I retreive the text version of a build log using a bash script ?
by doiggl＠velocitynet.com.au 20 Jan '11

20 Jan '11

Hello, Is there a way to remotly get the build log in text format without logging on, using a bash script ? I tried the following but it looked like html output not text log="https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre…" wget -c $log How can I retreive the text version of it using a bash script ? Thanks Glenn -- 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] OBS 2.2 got deployed on api.opensuse.org
by Adrian Schröter 20 Jan '11

20 Jan '11

After the last unsuccessfull tries it looks like have catched all performance problems finally. So api.opensuse.org is running OBS 2.2 (not yet released) now. The only remaining regression, I am aware of atm is that osc build with -- local-package option is not working. I will look into that in next minutes. Another big difference is now the behaviour of submit and devel change requests were you have no maintainer permissions in the source. In the past you were simply not allowed to create such a request. OBS 2.2 is allowing to create such an request, but adds the maintainer of the source package as reviewer of the request. This means concrete, when you see something, either a new package or and updated package, which should go to another project like openSUSE:Factory, you can ask now to submit it via such a request. But the original maintainer still can accept or decline this request. I hope this fullfills the discussed needs which got formely discussed. Unfortunatly, neither osc nor the webui can handle these reviews nicely yet. We will work on this these days as well. Have fun and please report if you see regressions with the new api. thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Creating stable snapshots of projects
by Malcolm Fernandes 19 Jan '11

19 Jan '11

We have a Project-A (1000+ packages) where we import some src rpms from another distribution on a periodic basis. Several other projects are built against the Project-A's repository. These other projects get de-stabilized because of the constant fluctuation caused by the imports of new src rpms in Project-A. The goal is to create a stable snapshot of Project-A (let's call that Project-A-STABLE), once Project-A has been built and tested. This Project-A-STABLE will then be used by the other projects. When src rpms are subsequently imported into Project-A, it should not cause any re-builds in Project-A-STABLE. How do you go about linking complete projects in OBS? Note sure if we should be using branch, linkpac, copypac, ... Please outline the steps involved in: - creating the first snapshot (Project-A-STABLE ) - creating subsequent stable snapshots from Project-A to Project-A-STABLE. The snapshot projects should preserve the revisions that it was branched off. Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Re: [Evergreen] [opensuse-packaging] Re: Need help on a Evergreen kernel module
by Greg Freemyer 19 Jan '11

19 Jan '11

All, I'm having a "Out of Memory" error building a package for 11.1 that should build fine for 11.3. === details I'm still trying to get a clean VirtualBox package to use with Evergreen. This attempt is to compile VirtualBox-ose from openSUSE11.3 with the 11.1 repo. I'm pretty sure it worked for both 32bit and 64bit compiles the first time I tried it. 32bit also worked the second time I tried it, but 64bit has failed twice in a row. I working in "home:gregfreemyer:Evergreen-11.1 > virtualbox-ose" Looking closer at the last OBS log I see: === [ 1674.366896] Out of memory: Kill process 11317 (cc1plus) score 121 or sacrifice child [ 1674.366911] Killed process 11317 (cc1plus) total-vm:243020kB, anon-rss:13640kB, file-rss:268kB === Does anyone have any insight into this? Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] obs worker and repserver services are not getting started
by ext-senthil.muthukalai＠nokia.com 18 Jan '11

18 Jan '11

Hi, I am trying to setup a private instance of OBS on my opensuse 11.3 machine. I downloaded and installed the OBS tools from http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUS… But I get the following errors when I try to run these services. linux-uff0:/home/senthil # rcobsworker start Run 1 obsworker using /var/cache/obs/worker cpio: premature end of archive chmod: cannot access `bs_worker': No such file or directory linux-uff0:/home/senthil # rcobsrepserver start Initializing obsrepserver done linux-uff0:/home/senthil # rcobsrepserver status Checking for obsrepserver and running processes: /srv/obs/run/bs_repserver.status: No such file or directory unused linux-uff0:/home/senthil # tail -f /srv/obs/log/rep_server.log ==> /srv/obs/log/rep_server.log <== Unquoted string "c" may clash with future reserved word at /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/_h2ph_pre.ph line 164. Illegal character in prototype for main::__INT16_C : c at /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/_h2ph_pre.ph line 164. Can't locate loadable object for module BSSolv in @INC (@INC contains: . build /usr/lib/perl5/site_perl/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.12.1 /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.12.1 /usr/lib/perl5/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/5.12.1 .) at /usr/lib/obs/server//bs_repserver line 66 Compilation failed in require at /usr/lib/obs/server//bs_repserver line 66. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_repserver line 66. Unquoted string "c" may clash with future reserved word at /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/_h2ph_pre.ph line 164. Illegal character in prototype for main::__INT16_C : c at /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi/_h2ph_pre.ph line 164. Can't locate loadable object for module BSSolv in @INC (@INC contains: . build /usr/lib/perl5/site_perl/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.12.1 /usr/lib/perl5/vendor_perl/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.12.1 /usr/lib/perl5/5.12.1/x86_64-linux-thread-multi /usr/lib/perl5/5.12.1 .) at /usr/lib/obs/server//bs_repserver line 66 Compilation failed in require at /usr/lib/obs/server//bs_repserver line 66. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_repserver line 66. Can anybody help me with this please? Thanks, Senthil M -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 14

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 18 Jan '11

18 Jan '11

present: mls, coolo, adrian, saschpe, bg, mrdocs Topics: ======= * OBS book * OBS 2.2 / 2.3 release * build.o.o status OBS Book ======== Infrastructure for OBS book writing has been set up. Announcement with details will follow today. OBS 2.2 / 2.3: ============== * Current master code is not releasable as 2.2, we need to - fix all FIXME2.2 marked places - debug speed problems to be able to deploy it on api.opensuse.org. * We think we will release 2.2 and 2.3 features at same time, planned for end next month. build.o.o status ================ * Our workers are still not really stable after updating to Factory. However, we added workarounds for now to kill hanging sessions. Also XEN and KVM developers are looking into the problems. * api.o.o was down on weekend due to performance regressions after updating to OBS 2.2 code. We reverted this therefore. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Documentation could use a refresh
by Helen 17 Jan '11

17 Jan '11

I notice a lot of the Buildservice documentation is getting a little bit dusty. Most of the distributions referred to as examples are over a year old. I know that often people do want to build on older distros, but - For me as a user, that makes me doubt the currency of the page, and worry that maybe things are outdated. If you think it's a good idea and have some spare time, it might be nice someone could take a look and freshen up a few pages. http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks http://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto Also is the Roadmap up to date? http://en.opensuse.org/openSUSE:Build_Service_Roadmap Many thanks!! Helen -- 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] Package links not handled correctly in project link?
by Anas Nashif 17 Jan '11

17 Jan '11

Hi, I am noticing that some packages, which are link to other packages in the same project are not handled correctly in linked projects. I get for example: 400 remote error: devel:trunk:testing/poppler-qt/39ed68813f5aace3c3c20bc2da79494f not in repository. poppler-qt in this case is a link to poppler in the origin project which I link to from devel:trunk:testing. Anas-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] [PATCH] Notification about unresolved state of packages
by Islam Amer 14 Jan '11

14 Jan '11

Hello, I noticed that there is no notification sent about unresolved state of packages in a project repository, so I did the attached small patch to fix that. The patch applies to the scheduler because AFAICS that was the place where the error was caught, and no build job was triggered. Please review, any comments welcome :) -- Thanks, Islam Amer

1 0

[opensuse-buildservice] OBS rebuild_time graph does not work
by Malcolm Fernandes 13 Jan '11

13 Jan '11

Hi, We have a local OBS instance (Ver: 2.1.3-2.1), running on openSUSE-11.2 When I click on the 'Check the rebuild time for this architecture' link from within the 'Repository States' webui, the Rebuild graph is NOT displayed. The individual package times do get displayed in the 'Longest Paths' . I've searched the web for any information on how to set this up, but cannot find any related documentation. Do I need to install some additional rpms and/or configure this somehow. Could you please shed some light on this. Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] obs-worker unable to obtain binary packages?
by Roman Valov 12 Jan '11

12 Jan '11

Hello, I've setup local build service instance and currently trying to build first project. My target is xUbuntu 10.04 and 10.10. Once sources were uploaded via web-interface -- it seems obs-server put build job in queue and job has been assigned to worker_1 running on the same machine. At this point I see status of my project as 'building' but log is permanently empty. I've found corresponding file /var/cache/obs/worker/root_1/.build.log is empty too and there is a file in /var/cache/obs/worker/root_1/.pkgs/.errors that lists base system packages with status "not available". My system uses proxy to access external resources and this is usually the source of problems. But I've already put proxy settings in BSConfig.pm. Regards, Roman. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] php5 on sles11
by Holger Stengel 12 Jan '11

12 Jan '11

Am Samstag, 25. September 2010, 09:36:58 schrieb Marcus Rueckert: > On 2010-09-25 09:02:55 +0200, Marcel Ritter wrote: > > Am 25.09.10 00:56, schrieb Peter Bowen: > > >A recent update to php5 on SLES11 moved from 5.2.6 to 5.2.14. However > > >builds are still against 5.2.6, meaning all the independent php5-* > > >packages are still picking up a requirement on php5 = 5.2.6, rendering > > >them uninstallable. How can we build against 5.2.14 so we get packages > > >compatible with the updated version? > > > > Hi Peter, > > > > we've got the very same problem, here's the reply > > I got from this list on the topic: > > > > --- start quote --- > > > > > I just noticed, that SLES 10/11 (latest SP) upgraded the > > > php5 Version to 5.2.14 - the buildservice still uses older > > > > > > php versions: > > > SLES 10 SP3 : 5.2.5 > > > SLES 11 SP1: 5.2.6 > > > > > > Will the updated versions be available in OBS? > > > Or is there a different repository with latest patches > > > for SLES (something like "openSUSE:11.3:Update" > > > in the opensuse world?) > > > > No, there isn't. But SLE updates should stay compatible, so it should > > not be a problem to build against the old version. (what is needed > > anyway, since SLE updates are optional to install unlike openSUSE). > > --- end quote --- > > > > I asked our Novell support engineer about this, and > > he agrees about the "should stay compatible" part, > > however the php-Macros > > > > Requires: php(zend-abi) = %{php_zend_api} > > Requires: php(api) = %{php_core_api} > > > > report changes in the API, so the new packages can no > > longer be used (maybe they might work if we ignored > > the dependencies, but this will break updates). > > > > I hope there'll be a solution for this problem soon. > > this issue is already being worked on. > > stay tuned. What is the current status of this issue? Thanks, Holger -- 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] Moving a package to another project maintaining history (and Release.Build)
by Anas Nashif 12 Jan '11

12 Jan '11

Hi, Is there an easy way to move packages while maintaining the source change history and the release.build numbers? Anas-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 12

[opensuse-buildservice] Problem with "build" package
by Kyrill Detinov 10 Jan '11

10 Jan '11

Monday 10 January 2011 I see, there is a problem with "build-2010.12.xx" package. Trying both, from Factory and openSUSE:Tools. /usr/lib/build/configs/default.conf is a broken link to missing file sl11.4.conf. Running local build I've got: ... reordering..._buildconfig-openSUSE_Factory-x86_64.conf not found, using default.conf /usr/lib/build/configs/default.conf: No such file or directory done ... -- WBR Kyrill -- 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] Re: [PATCH] run pre_checkin.sh on build and commit
by Adrian Schröter 10 Jan '11

10 Jan '11

please revert this ! We consider this a security issue, because you can't review always all possible existing pre_checkin.sh scripts. We want to solve most of these cases via source services. thanks adrian Am Mittwoch, 5. Januar 2011, 16:10:49 schrieb OBS osc: > From: Michal Vyskocil <mvyskocil(a)suse.cz> > > The pre_checkin.sh is script run after each checkin of package into > SUSE. Osc build and commit commands now runs it automatically too, > unless --no-precheckin is specified. > --- > NEWS | 1 + > osc/commandline.py | 17 ++++++++++++++++- > osc/core.py | 19 +++++++++++++++++++ > 3 files changed, 36 insertions(+), 1 deletions(-) > > diff --git a/NEWS b/NEWS > index c52df4d..beb64d6 100644 > --- a/NEWS > +++ b/NEWS > @@ -1,4 +1,5 @@ > 0.131 > + - call pre_checkin.sh on build and commit (can be suppressed with > --no-precheckin) > > 0.130 > - new "revert" command to restore the original working copy file (without > diff --git a/osc/commandline.py b/osc/commandline.py > index 456e621..5871622 100644 > --- a/osc/commandline.py > +++ b/osc/commandline.py > @@ -3084,6 +3084,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. help='Skip the source validation') > @cmdln.option('--verbose-validation', default=False, > action="store_true", help='Run the source validation with verbose > information') + @cmdln.option('--no-precheckin', action='store_true', > default=False, + help="don't run pre_checkin.sh, if exists") > def do_commit(self, subcmd, opts, *args): > """${cmd_name}: Upload content to the repository server > > @@ -3133,6 +3135,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. if conf.config['do_package_tracking'] and > is_project_dir(arg): try: > prj = Project(arg) > + if not opts.no_precheckin: > + run_precheckin(prj.pacs_have) > prj.validate_pacs(validators, opts.verbose_validation) > if not msg: > msg = edit_message() > @@ -3166,6 +3170,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. single_paths.append(pac.dir) > for prj_path, packages in prj_paths.iteritems(): > prj = Project(prj_path) > + if not opts.no_precheckin: > + run_precheckin((os.path.join(prj_path, p) for p in > packages)) prj.validate_pacs(validators, opts.verbose_validation, > *packages) if not msg: > msg = get_commit_msg(prj.absdir, pac_objs[prj_path]) > @@ -3173,6 +3179,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. store_unlink_file(prj.absdir, '_commit_msg') > for pac in single_paths: > p = Package(pac) > + if not opts.no_precheckin: > + run_precheckin() > p.validate(validators, opts.verbose_validation) > if not msg: > msg = get_commit_msg(p.absdir, [p]) > @@ -3181,6 +3189,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. else: > for p in pacs: > p = Package(pac) > + if not opts.no_precheckin: > + run_precheckin() > p.validate(validators, opts.verbose_validation) > if not msg: > msg = get_commit_msg(p.absdir, [p]) > @@ -4092,7 +4102,7 @@ Please submit there instead, or use --nodevelproject > to force direct submission. > > repositories = [] > # store list of repos for potential offline use > - repolistfile = os.path.join(os.getcwd(), osc.core.store, > "_build_repositories") + repolistfile = os.path.join(os.getcwd(), > store, "_build_repositories") if noinit: > if os.path.exists(repolistfile): > f = open(repolistfile, 'r') > @@ -4234,6 +4244,8 @@ Please submit there instead, or use --nodevelproject > to force direct submission. help='take previous build from DIR (special > values: _self, _link)') @cmdln.option('--shell', action='store_true', > help=SUPPRESS_HELP) > + @cmdln.option('--no-precheckin', action='store_true', default=False, > + help="don't run pre_checkin.sh, if exists") > def do_build(self, subcmd, opts, *args): > """${cmd_name}: Build a package on your local machine > > @@ -4316,6 +4328,9 @@ Please submit there instead, or use --nodevelproject > to force direct submission. if opts.offline and opts.preload: > raise oscerr.WrongOptions('--offline and --preload are mutually > exclusive') > > + if not opts.no_precheckin: > + run_precheckin() > + > print 'Building %s for %s/%s' % (args[2], args[0], args[1]) > return osc.build.main(self.get_api_url(), opts, args) > > diff --git a/osc/core.py b/osc/core.py > index 98d9a7b..fda1813 100644 > --- a/osc/core.py > +++ b/osc/core.py > @@ -5954,4 +5954,23 @@ def filter_role(meta, user, role): > for node in delete: > root.remove(node) > > +# run the pre_checkin.sh if exists > +def run_precheckin(packages=('.', )): > + oldpwd = os.getcwd() > + for dir in packages: > + if os.path.isdir(dir): > + os.chdir(dir) > + if os.path.isfile('pre_checkin.sh'): > + ret = subprocess.call(["/bin/sh", "pre_checkin.sh"]) > + if ret != 0: > + script_name = 'pre_checkin.sh' > + if dir != '.': > + script_name = "%s/%s" % (dir, script_name) > + #XXX: an ugly hack to prevent ../package - to me it > seems, there's a bug in do_commit + if script_name[:3] > == '../': > + script_name = script_name[3:] > + raise oscerr.ExtRuntimeError("sh %s has failed with > exit code %d, fix it or ignore using --no-precheckin" % (script_name, ret), > script_name) + os.chdir(oldpwd) > + return True > + > # vim: sw=4 et -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] RHEL/CentOS port questions
by Radoslav Dibarbora 10 Jan '11

10 Jan '11

Hello, I'm working on porting obs to RHEL and CentOS rel 5.x and 6.x. I would like to push the work to upstream but I'm not sure about few aspects of sending submit requests. 1. It is possible to submit request to add package witch will build just for specified repositories? 2. startup scripts have to be modified to work on RHEL/CentOS. Question is how to provide the RHEL specific startup scripts. Is it OK to prepare separate tarball with them and replace them during the install phase? Many thanks for any hints Regards Dibo -- 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] Building packages on specific hosts
by Malcolm Fernandes 07 Jan '11

07 Jan '11

We are trying to configure our local OBS instance (Ver 2.1.3-2.1) to build some packages on specific hosts. In BSConfig.pm, we have used the powerhosts and powerpkgs variables to build some packages (gcc, glibc, kernel,..) on the specified powerhost. In addition to this, we would like to build other packages such as 'qt' on another specific host. Is this possible, and if so, how do I go about configuring it? I've noticed this commented section in the BSConfig.pm file, to use specialbuildhost, but do not find any references to specialbuildhost in the OBS source code. Has this code been obsoleted? # Build some package only on specific hosts, or do not build on them # our %specialbuildhost = ( # "openSUSE:Factory/glibc" => { good => [ "build20", "build21" ] }, # "openSUSE:Factory/cmake" => { bad => [ "build10", "build11" ] }, #); Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] uninitialized value at /usr/lib/obs/server//bs_srcserver line 1377
by Jan-Simon Möller 07 Jan '11

07 Jan '11

Hi and happy new year! Running obs-api-2.1.73-2.1.x86_64 I see this in the logs when adding a remote repo from openSUSE.org to build against. Use of uninitialized value in addition (+) at /usr/lib/obs/server//bs_srcserver line 1377. The build doesn't start at all. Steps to reproduce: 1) Start up appliance and add interlink to openSUSE.org api 2) Create fixed version branched package (e.g. from openSUSE.org:openSUSE:11.3/bash) 3) Manually add openSUSE.org:openSUSE:11.3 standard i586 as build target. Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] how do i use the _published repo_ of a project as dependency in my own project?
by Mathias Homann 07 Jan '11

07 Jan '11

Hi there, is there a way to add the _published repo_ of a project in another project as dependency? background: my homeproject lists KDE:Release:45 as requirement. Now, K:R:45 is gettzing ready for KDE 4.5.5... but is set to "don't publish" for obvious reasons. This leads to any number of my packages being rebuilt over and over when there's no need yet (4.5.5 not being out yet), and then being not installable for broken deps... If it was possible to use the _published repo_ as dependency instead, packages wouldn't be built against 4.5.5 until 4.5.5 is actually released... any ideas / opinions? bye, MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] timeouts on workers leave jobs in undefined state
by Anas Nashif 05 Jan '11

05 Jan '11

Hi, Recently we are noticing lots of stale jobs that seem to have finished building, however stuck in finished status. Looking in the worker for those jobs reveals that something wrong happened after job has completed, in this case: build succeeded, but old build had same result ! build succeeded, but does not differ from old build result... sent, all done... send_state http://192.168.50.27:5252: rpc timeout Any idea what is going on here? Is there a way to remedy such jobs? Anas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Disable generating plain text passwords
by Michal Čihař 05 Jan '11

05 Jan '11

Hi I don't think it is necessary for osc to still save plain text password in ~/.oscrc. Is there any good reason for still doing so? Attached patch removes this functionality. -- Michal Čihař | http://cihar.com | http://blog.cihar.com

3 3

[opensuse-buildservice] OSC source validator
by Michal Čihař 04 Jan '11

04 Jan '11

Hi As OSC source validator seems to be required for silent osc operation, I'd like to package it for Debian as well to avoid these noisy warnings. However it brings some questions: - What is the license of the stuff? - Are there some releases happening? - Is there some VCS where the sources are placed? It really looks like a random snapshot of some internal scripts... -- Michal Čihař | http://cihar.com | http://blog.cihar.com

2 5