August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Bashism in complete.sh
by Guido Berhoerster 26 Aug '10

26 Aug '10

Hello, could somebody please apply the following small fix in osc: --- complete.sh.orig 2010-02-11 21:03:14.000000000 +0100 +++ complete.sh 2010-08-26 13:50:16.000000000 +0200 @@ -1,6 +1,6 @@ test -z "$BASH_VERSION" && return -complete -o default _nullcommand &> /dev/null || return -complete -r _nullcommand &> /dev/null || return +complete -o default _nullcommand >/dev/null 2>&1 || return +complete -r _nullcommand >/dev/null 2>&1 || return test -s /usr/share/osc/complete && complete -o default -C /usr/share/osc/complete osc test -s /usr/lib64/osc/complete && complete -o default -C /usr/lib64/osc/complete osc test -s /usr/lib/osc/complete && complete -o default -C /usr/lib/osc/complete osc This bashism triggers a warning in ksh93's parser each time a login shell is started which is pretty annoying. Thanks, -- Guido Berhoerster -- 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] For OBS Service setup with mutiple hosts
by Hou, Jingdu 26 Aug '10

26 Aug '10

Hi, I am strongly confused recently! I firstly setup a OBS Server with API server, web, SRC server, mySQL, 18 workers etc. in a host (OS is Opensuse 11.3), I can completed a full build about 9 hours. Then I want to add more workers to increase the performance, I setup one more host, configure 18 workers (changed the configure file /etc/sysconfig/obs-workers) to make sure they can work for the same API(totally 36 workers now). But I can completed a full build about 15 hours now. The question is that why when I double the workers, I need more time to complete a full build? It makes me crazy. Any comments, suggestion or documents on this? Appreciate if anyone can response! Thanks, Jingdu

2 1

[opensuse-buildservice] Need help on "Release:" in projconf
by Manjunath_A_Pattansh＠Dell.com 26 Aug '10

26 Aug '10

Hi, I need to override the projconf's "Release:" with 'CI_CNT' and 'B_CNT' with the "Release:" details from the spec file. But I noticed that it doesn't happens without CI_CNT and B_CNT in the "Release:" value in the spec file. That is if I just give "Release: myrel%(?dist)", the projconf's "Release:" overrides this. But if I include "Release: myrel.<CI_CNT>.<B_CNT>%{?dist}" in the spec file it happens but conditional. In some cases I get error for RHEL6 and SLES11 saying invalid "<" character. But on the rest of distros passes with nil values for CI_CNT and B_CNT. I need the correct behavior for this or how I can achieve it from the spec file without modifying the projconf file. My requirement is to have "-myrel.<valueof:CI_CNT>.<valuof:B_CNT>.sles.rpm" as suffix. Thanks, Manjunath A. Pattanshetti -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] obs branching question
by Christian Daudt 26 Aug '10

26 Aug '10

Hi, I just recently started using branches in obs, and to my surprise when the parent branch (the source proj:pkg used in osc branch command) gets an update, that is immediately pushes to the branches. This branching is not like the others :-( - i.e. unlike any version control in which the origin->child merge is done on demand, not auto-initiated. The problem that I see with this is that developing on the branch becomes a bit like building on quicksand, since you never know when the ground is going to shift on you. I have a little build script which uses the same patchname ("current.patch") while I'm developing a mod but not yet ready to commit to a name for the patch, and this is causing the children branches to get broken whenever I update the origin (since at that time the update "current.patch" gets pushed to the children and causes all of the children to break due to a merge conflict in this "current.patch" file). Is there a way to change this behaviour so that a branch reflects the state of the origin when the branch was created, and doesn't auto-update? I do plan to change my script so that it uses a more random name for the patch, but I would still prefer to use the non-auto-push behaviour in case it's available. Thanks, Christian. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6

[opensuse-buildservice] Home Project vs. SubProject
by Srivats P 26 Aug '10

26 Aug '10

Hi, I just started using the OBS to package Ostinato (http://code.google.com/p/ostinato) for several distros - this is a fantastic service! I'm however not sure if I should build packages in the "home" project or create a subproject and build packages within the subproject. From all I've read/seen till now they seem to be equivalent in all respects. Is there a recommended practice or convention? Also as I release new versions of Ostinato, I would like to retain the packages of older versions while releasing new versions - note I don't mean different RPM releases for the same program version but different program versions. How do I achieve this (creating a new subproject/package for every new program version seems wasteful). Thanks in Advance. Regards, Srivats -- 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] build21 seems to be dead
by Greg Freemyer 25 Aug '10

25 Aug '10

I just noticed all the red bars on the monitor. It's not even showing up on the detail status page. Greg -- 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] call for testing: reworked osc's update mechanism
by Marcus Hüwe 25 Aug '10

25 Aug '10

Hi, in the last days/week I rewrote osc's update mechanism because the old version had some bugs here and there. The main features of the new version are: * resume aborted updates (for instance if you interrupted "osc up" the next invocation of "osc up" will try to resume the old update). This way we (hopefully) avoid broken wc's. * support for new commands like "osc revert" Since the current code is still experimental it isn't pushed to git master yet (the current code is available in my home repo: http://gitorious.org/~marcush/opensuse/marcushs-osc). I also created packages which are available here: http://download.opensuse.org/repositories/home:/Marcus_H:/branches:/openSUS… Feedback and bug reports are always welcome:) Marcus -- 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] ia-64 (itanium) scheduling and worker
by Troy Telford 25 Aug '10

25 Aug '10

I've got a pretty decent private OBS server set up; but there is one thing I'm fairly sure will be easy, but am looking for pointers as to where to look first: Architectures other than those currently on build.opensuse.org - specifically, Itanium/IA-64 Assuming that I'm working with older distros that support IA-64/Itanium, how difficult would it be to get OBS to schedule/build on IA-64? I'm thinking it shouldn't be too hard, given that bs_sched in in perl, as is obs-worker. So what would I have to do in order to support Itanium on my private OBS install? -- 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] kde-obs-generator Error
by Kai-Uwe Behrmann 24 Aug '10

24 Aug '10

I try to generate a cross distribution package for Oyranos. My test with kde-obs-generator failed with following message: ERROR: Do not know which analyzer to use The Package is a configure/make/make install one, but not autotools. https://build.opensuse.org/package/show?package=oyranos-0.1.10&project=home… The INFO file seems not to help. Can I use kde-obs-generator for that? kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] publishing still disabled?
by Mathias Homann 24 Aug '10

24 Aug '10

Hey, is publishing still disabled? I have a few packages sitting in my project that finished building about half an hour ago, and still are in state "finished" as opposed to "published"... and there are no other build jobs in my project. any hints? bye, MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3