May 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Re: [opensuse-svn] r7243 - in trunk/buildservice/src/clientlib/python/osc: . osc
by Peter Poeml 06 May '09

06 May '09

Hi, On Mon, May 04, 2009 at 01:07:10PM -0600, Novell Forge SVN wrote: > Author: AdrianSuSE > Date: 2009-05-04 13:07:05 -0600 (Mon, 04 May 2009) > New Revision: 7243 > > Modified: > trunk/buildservice/src/clientlib/python/osc/NEWS > trunk/buildservice/src/clientlib/python/osc/osc/cmdln.py > trunk/buildservice/src/clientlib/python/osc/osc/commandline.py > trunk/buildservice/src/clientlib/python/osc/osc/conf.py > Log: > Consolidating delete commands: > * obsolete deletepac and deleteprj to delete and rdelete commands. > - enable package tracking by default This doesn't work for me (osc r7264): poeml@batavia510 ~ % osc rdelete home:poeml:branches:Subversion Traceback (most recent call last): File "/suse/poeml/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/suse/poeml/osc-trunk/osc/babysitter.py", line 38, in run return prg.main() File "/suse/poeml/osc-trunk/osc/cmdln.py", line 255, in main return self.cmd(args) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 278, in cmd retval = self.onecmd(argv) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 394, in onecmd return self._dispatch_cmd(handler, argv) File "/suse/poeml/osc-trunk/osc/cmdln.py", line 1084, in _dispatch_cmd return handler(argv[0], opts, *args) File "/suse/poeml/osc-trunk/osc/commandline.py", line 1001, in do_rdelete elif len(meta_get_packagelist(conf.config['apiurl'], project)) >= 1 and not opts.force: NameError: global name 'project' is not defined [1] 5651 exit 1 osc rdelete home:poeml:branches:Subversion It seems that the failure is caused by a wrong variable name, "project" instead of "prj", in one place. I'll commit this as a fix, assuming that it's the entire problem. Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] recent 1.6beta2 obs-worker and src-server won't start
by Jon Nelson 05 May '09

05 May '09

Previously I was running obs 1.6beta2 release 1.1 For obsworker: Run 2 obsworker using /tmp/build /var/run/obs/worker/boot ~ curl: (7) couldn't connect to host cpio: premature end of archive chmod: cannot access `bs_worker': No such file or directory ~ /var/run/obs/worker/boot ~ ~ For src-server: Initializing obssrcserverCan't locate Build.pm in @INC (@INC contains: /usr/lib/obs/server/ /usr/lib/obs/server//build /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/5.10.0 /usr/lib/perl5/site_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.10.0 /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl .) at /usr/lib/obs/server//bs_srcserver line 50. BEGIN failed--compilation aborted at /usr/lib/obs/server//bs_srcserver line 50. The version of the 'build' package went from 2009.03.23-39.1 to 2009.04.23-46.1 at the same time. -- Jon -- 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] Build Team Meeting
by Adrian Schröter 05 May '09

05 May '09

present: mls, freitag, froh, adrian, poeml, abauer Topics: * Status Round Status Round: ============= mmohring: - fixed build package+svn trunk, missing another file, and also debian packaging - fixed osc build for arm native targets, still python site-package issue on ubuntu 9.04 - added more complex config example for OBS/lighttpd to svn trunk - tracked down cycle breaking problem in ubuntu 9.04 (order: vs. ignore: - seem not to work in my case) - evaluated arm arch parameter passing from OBS to rpm - supported Maemo/Mer project to get Maemo:Mer:Devel snapshot working (from Maemo 5.0 sources) - discussion about how to clean <buildroot> in build chroot/XEN (files and mounts). needs final solution - discussion how to include also KIWI Devel snapshots into testing, readded openSUSE:Tools:Devel/kiwi - packaged svn trunk -r 7247 obs, osc, build packages in openSUSE:Tools:Devel möller: - fixing some more openSUSE packages for arm builds (gmp, ...) - research rpmbuild <-> armv5/6/7 issue abauer: - keep working on web client 2.0 freitag; - OBS develop system is running AI: adrian ask mmorhing and friends for ssh keys and allow them access adrian: - osc delete operations consolidation - implementing of delete request (partly committed) - scheduler optimzations for mass events storms (not yet committed) - dirty markers for repositories (not yet committed) poeml: - looking in optimizing the repo pusher, which seems to be a bottleneck currently -- 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

Re: [opensuse-buildservice] How to resolve build errors with linked packages
by Adrian Schröter 04 May '09

04 May '09

Am Montag, 4. Mai 2009 13:18:38 schrieb Richard Bos: > On Mon, May 04, 2009 at 01:09:45PM +0200, Adrian Schr?ter wrote: > > Am Montag, 4. Mai 2009 12:55:39 schrieb Richard Bos: > > .. > > > > > I fix the conflicting perl-ldap.spec file. At least that is what I > > > think, and execute: > > > devel:languages:perl/perl-ldap/repairlink> osc ci -m "repair broken > > > linkage (with Factory)" perl-ldap.spec > > > Please resolve all conflicts before committing! > > > > you need to tell osc that the conflict is resovled by > > > > osc resolved $FILENAME > > Ah, and that is executed in the repairlink directory? yes > Does the same count for the commit action, is that also to > be executed from the repairlink directory? the repairlink directory is like a checked out package source of the package, just with merged changes. > After that I assume it is okay, to remove the repairlink > directory, after which a "osc update" will be sufficient, > to get a updated working directory (in my case > devel:language:perl/perl-ldap), isn't it? yes > Would it be okay, to remove the project*.diff files, > would that start a rebuild? In this particular case, it > would be a quick and easy solution. yes, but you need also remove it from _link file. -- 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] How to set build-root and rpm cache to other directory than /var/tmp?
by Qian Feng 04 May '09

04 May '09

Hi dear all, osc build always use /var/tmp/build-root and /var/tmp/osbuildpackages as root and rpm cache. This bothers me because my / partition is quite small. Is there any way to use some other directory? build has the --root option but I don't know how to use this option in "osc build". Thanks, Fred -- 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] How to resolve build errors with liked packages
by Richard Bos 04 May '09

04 May '09

Hi, I get the following message: devel:languages:perl/perl-ldap> osc up Link cannot be expanded: could not apply patch 'project.diff' Use "osc repairlink" to fix merge conflicts. when working on the package perl-ldap in the repository devel:languages:perl. So I do: Which result in: devel:languages:perl/perl-ldap> osc repairlink using last working link target G perl-ldap-0.39.tar.bz2 U perl-ldap.changes C perl-ldap.spec ready Please change into the 'repairlink' directory, fix the conflicts, and commit the changes. I fix the conflicting perl-ldap.spec file. At least that is what I think, and execute: devel:languages:perl/perl-ldap/repairlink> osc ci -m "repair broken linkage (with Factory)" perl-ldap.spec Please resolve all conflicts before committing! I did clearly something wrong, but what? I just want to update to the latest version. As such I removed the lines that are no longer needed from the file: repairlink/perl-ldap.spec (e.g. I removed version: 0.37 in favour of the new line containing version: 0.39). The package contains the files: devel:languages:perl/perl-ldap> osc ls devel:languages:perl perl-ldap _link perl-ldap-0.39.tar.bz2 project.diff project1.diff I no longer need the project.diff files (1 change I can easily create again). What is correct way to deal with this??? -- Richard -- 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] [Patch] support setting of different _target_arch
by Jan-Simon Möller 04 May '09

04 May '09

Hi ! In preparation to my GSoC project (openSUSE@arm) I'd like to propose this patch of Build.pm for inclusion into the Build Service code. =================================================================== --- Build.pm (Revision 7227) +++ Build.pm (Arbeitskopie) @@ -216,6 +216,9 @@ $config->{'patterntype'} = [ @l ]; } elsif ($l0 eq 'release:') { $config->{'release'} = $l[0]; + } elsif ($l0 eq 'changetargetarch:') { + @macros = grep {$_ !~ /^%define _target_cpu/ } @macros; + push @macros, "%define _target_cpu @l"; } elsif ($l0 !~ /^[#%]/) { warn("unknown keyword in config: $l0\n"); } Reasoning: Some lines above in Build.pm %_target_arch gets set to the scheduler arch (scheduler name). In ARM world this is a bit more complicated - e.g. there's armv5tel, armv5tejl, armv5tevl . This is no problem in debian world IIRC as we see so far in Mer. Unfortunately rpmbuild needs to know the right value (armv5tel instead of armv5el). It would be bad to use now different schedulers only for tel/tejl/tevl and so on. So with my patch we can use still the armv5el scheduler and differ through "changetargetarch:" the _target_cpu where needed. Best, Jan-Simon

2 1

[opensuse-buildservice] [PATCH] osc submitreq create DESTPRJ [DESTPKG]
by Michal Vyskocil 04 May '09

04 May '09

Hi all, following patch makes importing of new packages to OBS easier. If you want add a new package to Factory, you don't have a sourcelink yet and no metadata exists, so you must type osc sr create SOURCEPRJ SOURCEPKG openSUSE:Factory [DESTPKG] -m "message" even if SOURCEPRJ and SOURCEPKG should be read from working dir instead. With this you can type only osc sr create openSUSE:Factory [DESTPKG] -m "message" Any objections against it? Regards Michal Vyskocil

2 1

[opensuse-buildservice] MonoOSC IRC Channel
by Petit Eric 03 May '09

03 May '09

Hi, people who use MonoOSC should be happy to joint the MonoOSC IRC Channel, i also use it for my SVN commit. irc server is : irc.freenode.net irc chanel is : #MonoOSC Have a fun ! -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. -- 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] Help me bout the concept of "excluded" and "blocked"?
by Qian Feng 03 May '09

03 May '09

Dear all, I am building an iso image based on SLE-11_GA on IBS web page: https://build.suse.de/package/show?package=Image&project=home%3Afengqian The Build Status column shows that: SLE-11_GA i586 is excluded, ia64 is disabled. So what's the difference between excluded and disabled? I guess "excluded" means I don't want a pure SLED iso so don't build it, and "disabled" means "don't even think about this architecture". Correct? Also, I wonder why my "images - i586" repo is "blocked". I don't know what this really means. I had built the iso there, but now for some reason it's blocked, I cannot trigger any rebuild. Thanks in advance. Rgds, Fred -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1