January 2011 - openSUSE Build Service - openSUSE Mailing Lists

[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