February 2013 - openSUSE Build Service

[opensuse-buildservice] OpenSUSE OBS projects confusion
by Magnus Lewis-Smith 21 Feb '13

21 Feb '13

I see there are several projects building OBS and hence several repositories serving the tools: openSUSE:Tools openSUSE:Tools:1.7 openSUSE:Tools:2.0 openSUSE:Tools:2.1 openSUSE:Tools:2.3 openSUSE:Tools:2.4 OBS:Server:2.4 OBS:Server:Unstable Can I ask what they are all for? I presume legacy versions in the openSUSE:Tools:X.X projects, and openSUSE:Tools being stable. I currently run an ancient 2.1 local installation in dire need of upgrade. It is patched somewhat to customise the HTML for our organisation, so it builds itself, but makes updating ... interesting. With the imminent release of 2.4 I am wondering which repository to branch from. Regards Magnus -- 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] Is OBS 2.4 available?
by Aaron Yung 19 Feb '13

19 Feb '13

Hi All Is OBS 2.4 available ? I see the release notes at github(https://github.com/openSUSE/open-build-service/blob/master/ReleaseNo…. But I can't find any packages with version 2.4 but 2.3.7 in opensuse repos. Any body can give me an answer? Thanks ----- Go OBS -- View this message in context: http://opensuse.14.n6.nabble.com/Is-OBS-2-4-available-tp4984680.html 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

2 3

[opensuse-buildservice] have choice for postgresql-devel
by Michael Behrisch 19 Feb '13

19 Feb '13

Hi, when trying to build the package sumo depending on gdal-devel (from Application:Geo), I get "have choice for postgresql-devel needed by libgdal-devel: postgresql-devel postgresql92-devel" but only for the x86_64 versions of 12.3 and Factory https://build.opensuse.org/project/monitor?project=home%3Abehrisch . I know that I could add a prefer to work around this, but I wonder whether this is a bug because neither the gdal spec nor postgres or sumo have anything platform specific in their spec (as far as I can tell). Any hints? Best regards, Michael -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] when bs_publish will write/delete files to /obs/repos_sync?
by Rick Liu 18 Feb '13

18 Feb '13

Hi, I have a question about bs_publish. What's the life cycle for the $projid files in /obs/repos_sync? eg. how they got created and how they will be removed? Thanks for the help, Rick -- 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: [opensuse-buildservice] files in /obs/events/?
by Rick Liu 18 Feb '13

18 Feb '13

> > The rest folders "i586, x86_64, armv7el, armv8el, .. etc" in /obs/events > > stay empty as usual, except the '.ping' file. > > > > Any possible reason causes file created in '/obs/events/armv5el' folder > > when 'armv5el' is not enabled in $ OBS_SCHEDULER_ARCHITECTURES? > Only the scheduler creates it usually. So it got started once at least. > But you can just remove the directory. I also just found out that whenever I create a new Project or new Package, a new file will be created under 'obs/events/armv5el' and stays there. eg. If I create a new project 'RickLiu' and a new package under 'RickLiu' project, I'll have 2 new files: 1) /obs/events/armv5el/project\:RickLiu: <event type="project"> <project>RickLiu</project> </event> 2) /obs/events/armv5el/package\:RickLiu\:\:RickLiu: <event type="package"> <project>RickLiu</project> <package>RickLiu</package> </event> Is this normal? (even though I didn't specify any arch for the new project/package, the new files are created under armv5el arch). The schedulers running are only i586, x86_64, armv7el, and armv8el: (no armv5el) # ps aux |grep bs_sched obsrun 15525 0.0 0.2 192348 113112 ? S 2012 125:41 /usr/bin/perl -w ./bs_sched i586 obsrun 15526 0.0 0.1 148304 70200 ? S 2012 40:58 /usr/bin/perl -w ./bs_sched x86_64 obsrun 15527 0.1 0.6 392676 308600 ? S 2012 292:27 /usr/bin/perl -w ./bs_sched armv7el obsrun 15528 0.0 0.2 218068 120260 ? S 2012 111:47 /usr/bin/perl -w ./bs_sched armv8el Rick -- 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] Can't accept/decline request 152095
by Michal Vyskocil 18 Feb '13

18 Feb '13

Hi, I've got a deleterquest 152095. And because I'd say the home:mvyskocil:connman is pointless, I've removed it by subsequent dr. But atm I cannot accept/neither decline the original request. The first option fails because original project does not exists The second one fails because I have no permissions to do that Regards Michal Vyskocil

1 0

RE: [opensuse-buildservice] files in /obs/events/?
by Rick Liu 18 Feb '13

18 Feb '13

> > Hi, > > I'm using V2.3.1 OBS appliance. > We currently have only "i586 x86_64 armv7el armv8el" > enabled in $OBS_SCHEDULER_ARCHITECTURES (/etc/sysconfig/obs-server). > > But I found there's many file exists in '/obs/events/armv5el' folder, > and which folder didn't exist when I first setup obs server. [Rick Liu] some of files as old as 6 months. > > The rest folders "i586, x86_64, armv7el, armv8el, .. etc" in /obs/events > stay empty as usual, except the '.ping' file. > > Any possible reason causes file created in '/obs/events/armv5el' folder > when 'armv5el' is not enabled in $ OBS_SCHEDULER_ARCHITECTURES? > > > Thanks, > > Rick > > -- > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org > -- 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] files in /obs/events/?
by Rick Liu 15 Feb '13

15 Feb '13

Hi, I'm using V2.3.1 OBS appliance. We currently have only "i586 x86_64 armv7el armv8el" enabled in $OBS_SCHEDULER_ARCHITECTURES (/etc/sysconfig/obs-server). But I found there's many file exists in '/obs/events/armv5el' folder, and which folder didn't exist when I first setup obs server. The rest folders "i586, x86_64, armv7el, armv8el, .. etc" in /obs/events stay empty as usual, except the '.ping' file. Any possible reason causes file created in '/obs/events/armv5el' folder when 'armv5el' is not enabled in $ OBS_SCHEDULER_ARCHITECTURES? Thanks, Rick -- 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] removed packages, wiped binaries -- built package still hangin' around
by Jon Nelson 13 Feb '13

13 Feb '13

In a private OBS instance, I ran into a problem that remains unresolved. I deleted a package and found that other packages were still using it for build. In an attempt to fix this (weird) situation, I even wiped *all* of the binaries for the project. No dice. After logging into the actual build server, I found in: /srv/obs/build/$PROJECT/$REPO/$ARCH/:full only two files -- the *name* of the built package with two extensions: .rpm and .meta. What happened here? Clearly there seems to be a bug, but where? More importantly for the time being, how do I remediate? I'll note that the publishing of the package was disabled before it was deleted altogether. Perhaps that is relevant? I'm on openSUSE 12.1 with OBS 2.3 -- Jon -- 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] [PATCH] osc build on remote --host
by Michal Vyskocil 12 Feb '13

12 Feb '13

The new argument for osc build --host will perform the build on a remote host. It is a shortcut for rsync -az -e ssh `pwd` user@hostname:/remote/dir rsync -az -e ssh prefer-dir \ user@hotname:/remote/dir/__prefer-rpms__/prefer-dir ssh -t user@hostname "cd /remote/dir/package; osc build *build-args" rsync -az -e ssh user@hostname:/remote/dir/__keep-pkgs__ keep-pkgs iow it copy the current directory to the /remote/directory on hostname (if not specified, the ~/ is supplied) and then run the osc build on hostname. All global and local arguments are supplied to the remote osc build, but arguments points to local path (--host, --keep-pkgs, --prefer-pkgs, --rsync-dest, --rsync-src and --overlay) are modified to match to remote host. It support the OSC_ variables, so running with OSC_BUILD_ROOT=/somewhere osc build --host ... will push the variable to the remove osc process --- osc/commandline.py | 139 +++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 138 insertions(+), 1 deletion(-) diff --git a/osc/commandline.py b/osc/commandline.py index 8db214b..fe7cbe2 100644 --- a/osc/commandline.py +++ b/osc/commandline.py @@ -5267,6 +5267,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('--host', metavar='HOST', + help='perform the build on a remote server - user@server:~/remote/directory') def do_build(self, subcmd, opts, *args): """${cmd_name}: Build a package on your local machine @@ -5365,7 +5367,142 @@ Please submit there instead, or use --nodevelproject to force direct submission. raise oscerr.WrongOptions('--offline and --preload are mutually exclusive') print 'Building %s for %s/%s' % (args[2], args[0], args[1]) - return osc.build.main(self.get_api_url(), opts, args) + if not opts.host: + return osc.build.main(self.get_api_url(), opts, args) + else: + return self._do_rbuild(subcmd, opts, *args) + + def _do_rbuild(self, subcmd, opts, *args): + + # drop the --argument, value tuple from the list + def drop_arg2(lst, name): + if not name: return lst + while name in lst: + i = lst.index(name) + lst.pop(i+1) + lst.pop(i) + return lst + + # change the local directory to more suitable remote one in hostargs + # and perform the rsync to such location as well + def rsync_dirs_2host(hostargs, short_name, long_name, dirs): + + drop_arg2(hostargs, short_name) + drop_arg2(hostargs, long_name) + + for pdir in dirs: + # drop the last '/' from pdir name - this is because + # rsync foo remote:/bar create /bar/foo on remote machine + # rsync foo/ remote:/bar copy the content of foo in the /bar + if pdir[-1:] == os.path.sep: + pdir = pdir[:-1] + + hostprefer = os.path.join( + hostpath, + basename, + "%s__" % (long_name.replace('-','_')), + os.path.basename(os.path.abspath(pdir))) + hostargs.append(long_name) + hostargs.append(hostprefer) + + rsync_prefer_cmd = ['rsync', '-az', '-delete', '-e', 'ssh', + pdir, + "%s:%s" % (hostname, os.path.dirname(hostprefer))] + print 'Run: %s' % " ".join(rsync_prefer_cmd) + ret = subprocess.call(rsync_prefer_cmd) + if ret != 0: + return ret + + return 0 + + + cwd = os.getcwdu() + basename = os.path.basename(cwd) + if not ':' in opts.host: + hostname = opts.host + hostpath = "~/" + else: + hostname, hostpath = opts.host.split(':', 1) + + # arguments for build: use all arguments behind build and drop --host 'HOST' + hostargs = sys.argv[sys.argv.index(subcmd)+1:] + drop_arg2(hostargs, '--host') + + # global arguments: use first '-' up to subcmd + gi = 0 + for i, a in enumerate(sys.argv): + if a == subcmd: + break + if a[0] == '-': + gi = i + break + + if gi: + hostglobalargs = sys.argv[gi : sys.argv.index(subcmd)+1] + else: + hostglobalargs = (subcmd, ) + + # keep-pkgs + hostkeep = None + if opts.keep_pkgs: + drop_arg2(hostargs, '-k') + drop_arg2(hostargs, '--keep-pkgs') + hostkeep = os.path.join( + hostpath, + basename, + "__keep_pkgs__", + "") # <--- this adds last '/', thus triggers correct rsync behavior + hostargs.append('--keep-pkgs') + hostargs.append(hostkeep) + + ### run all commands ### + # 1.) rsync sources + rsync_source_cmd = ['rsync', '-az', '-delete', '-e', 'ssh', cwd, "%s:%s" % (hostname, hostpath)] + print 'Run: %s' % " ".join(rsync_source_cmd) + ret = subprocess.call(rsync_source_cmd) + if ret != 0: + return ret + + # 2.) rsync prefer-pkgs dirs, overlay and rsyns-src + if opts.prefer_pkgs: + ret = rsync_dirs_2host(hostargs, '-p', '--prefer-pkgs', opts.prefer_pkgs) + if ret != 0: + return ret + + for arg, long_name in ((opts.rsyncsrc, '--rsync-src'), (opts.overlay, '--overlay')): + if not arg: continue + ret = rsync_dirs_2host(hostargs, None, long_name, (arg, )) + if ret != 0: + return ret + + # 3.) call osc build + osc_cmd = "osc" + for var in ('OSC_SU_WRAPPER', 'OSC_BUILD_ROOT', 'OSC_PACKAGECACHEDIR'): + if os.getenv(var): + osc_cmd = "%s=%s %s" % (var, os.getenv(var), osc_cmd) + + ssh_cmd = \ + ['ssh', '-t', hostname, + "cd %(remote_dir)s; %(osc_cmd)s %(global_args)s %(local_args)s" % dict( + remote_dir = os.path.join(hostpath, basename), + osc_cmd = osc_cmd, + global_args = " ".join(hostglobalargs), + local_args = " ".join(hostargs)) + ] + print 'Run: %s' % " ".join(ssh_cmd) + build_ret = subprocess.call(ssh_cmd) + if build_ret != 0: + return build_ret + + # 4.) get keep-pkgs back + if opts.keep_pkgs: + ret = rsync_keep_cmd = ['rsync', '-az', '-e', 'ssh', "%s:%s" % (hostname, hostkeep), opts.keep_pkgs] + print 'Run: %s' % " ".join(rsync_keep_cmd) + ret = subprocess.call(rsync_keep_cmd) + if ret != 0: + return ret + + return build_ret @cmdln.option('--local-package', action='store_true', -- 1.7.10.4

2 2