December 2009 - openSUSE Build Service

[opensuse-buildservice] Did have method to disable obs check requires in cycle?
by Jian Lee 23 Dec '09

23 Dec '09

hi, all I'm researching the build ablity of obs, and I'm find that any events of every package in the project should change the schedule of task. My step is: 1. create a new project, no repository added 2. use a script commit more than 1000 srpm packages auto in batch. 3. all packages commit done, I added a standard repository Result: the obs-server working in a cycle 1. do some requires check, select some packages to build and many packages to waiting 2. the successed packages made a event to rebuild some successed pkgs 3. redo 1 and 2 Questions: did obs have a solution to made a only one schedule list ? 1. do requires check based on current pkgs, and create a schedule list 2. do building. 3. user can select do or not do check and rebuilding after the schedule list executed done. Thanks, ---- Jian Lee [ http://jianlee.ylinux.org ] -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 16

[opensuse-buildservice] obs-worker: Use sysfs for counting VCPUs
by Jan Engelhardt 22 Dec '09

22 Dec '09

The following changes since commit 1b916677dce359536faab8524f8db441032c265b: Stephan Kulow (1): - add bento theme linked to webdesign module - move some styling into css files are available in the git repository at: git://dev.medozas.de/suse-build-service master Jan Engelhardt (1): Obtain number of vcpus without relying on cpuinfo dist/obsworker | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) ---8<--- parent 1b916677dce359536faab8524f8db441032c265b () commit bd91f0edbf48ee171338bee7d48e6dfcaad0fc45 Author: Jan Engelhardt <jengelh(a)medozas.de> Date: Tue Dec 22 19:58:46 2009 +0100 Obtain number of vcpus without relying on cpuinfo /proc/cpuinfo has different layout and content on different architectures. The old command line would always result in 0 on SPARC. Signed-off-by: Jan Engelhardt <jengelh(a)medozas.de> --- dist/obsworker | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/dist/obsworker b/dist/obsworker index 134e736..f3de41e 100644 --- a/dist/obsworker +++ b/dist/obsworker @@ -103,8 +103,11 @@ case "$1" in NUM="$OBS_WORKER_INSTANCES" else # start one build backend per CPU - NUM=`grep ^processor /proc/cpuinfo | wc -l` + NUM=$(ls -d /sys/devices/system/cpu/cpu[0-9]*/topology | wc -l) fi + if [ "$OBS_WORKER_INSTANCES" -eq 0 ]; then + NUM=1; + fi; I=0 ROOT="/tmp" [ -d /BUILD ] && ROOT="/BUILD" -- # Created with git-export-patch -- 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] About info of the server
by Petit Eric 21 Dec '09

21 Dec '09

Hi The about info of the server : https://api.opensuse.org/about Is definitively no more available(obsolete), buggy or moved ? -- Cordially. Deploy your softwares for all platforms and finally update them in 3 clicks. Try now the OpenSource MonoOSC tool http://monoosc.sourceforge.net/ http://download.opensuse.org/repositories/home:/surfzoid/ http://download.opensuse.org/repositories/home:/surfzoid:/DebianUbuntu/ http://download.opensuse.org/repositories/home:/surfzoid:/DebianUbuntu:/Mon… Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] Is OBS respect debian/ubuntu standard ?
by Petit Eric 20 Dec '09

20 Dec '09

Hi i build debian/ubuntu pkg here https://build.opensuse.org/package/show?package=libgdiplus&project=home%3As… all the files except the dsc, and 2 gz already exist in the source tarball (in debian dir), but with the standard and normal way, build failed with a problem during distclean, the fact to add all the extra files yu see solve the problem sound like OBS don't follow correctly the debian standard and wait for rule, changelog, control and other files at the same place of the gz and dsc file ? how OBS will react when the diff.gz and directly uploaded files disagree ? -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] Changing the email address
by Bernhard Walle 20 Dec '09

20 Dec '09

Hi, I know that this question is not specific to the openSUSE Build Service but it affects the Novell account in general. However, I think that's a list where the people that know the answer read the mail. :-) The question: Where can I change the email address so that 'osc vi' picks the right one? Regards, Bernhard -- 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] How can I publish MS Windows installer MSI packages?
by Hib Eris 18 Dec '09

18 Dec '09

Hi, I am using the openSUSE build service to build a MS Windows installer package for the Evince Document Viewer (evince.msi) on the openSUSE build service, running the build commands from a .spec file. I have got this working quite well, but now, my problem is, where to put the resulting evince.msi file. Normally, the resulting binaries of a .spec file are put into rpm packages that are then published by the build service. Of course, I can put the evince.msi file into a rpm package as well and let the rpm package be published by the build service. But because MS Windows(-users) cannot handle rpm packages, this is not very usefull. I would like to publish msi files, not rpm files with msi files in it. Is this possible and/or can the build service be adopted to publish *.msi files resulting from a .spec file build? Kind regards, Hib Eris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Re: [PATCH] - first attempt at "osc pull" and "linkcontrol"
by Marcus Hüwe 18 Dec '09

18 Dec '09

Hi, On 2009-12-17 17:22:08 +0100, OBS osc wrote: <SNIP> > diff --git a/osc/conf.py b/osc/conf.py > index e59c801..b26fca2 100644 > --- a/osc/conf.py > +++ b/osc/conf.py > @@ -106,6 +106,7 @@ DEFAULTS = { 'apiurl': 'https://api.opensuse.org', > 'check_filelist': '1', > # check for pending requests after executing an action (e.g. checkout, update, commit) > 'check_for_request_on_action': '0', > + 'linkcontrol': '0', > Hmm is this really supposed to be a config option or is it's sole purpose to influence the behaviour of some methods? Marcus -- 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: libgcrypt redirection
by Jan Engelhardt 18 Dec '09

18 Dec '09

Hi, when trying to branch from openSUSE:Factory/libgcrypt, I get redirected to home:hennevogel:TODO/libgcrypt. Alternatively, trying to branch from security:privacy/libgcrypt, I get redirected to another home project, home:makoenig:Factory/libgcrypt. Neither of these look authoritative. Can the involved parties resolve this uncertainty? Thanks, Jan -- 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] SLES 10 and console only support for python-keyring-gnome
by Luke Imhoff 17 Dec '09

17 Dec '09

I'm not sure how many other users of osc are using SLES 10 still, but I've got a modified version of python-keyring that supports using gnome-keyring on SLES 10. It involves patching gnome-keyring as gnome_keyring_get_info_sync is bugged, but I can supply that too. If anyone else is still using SLES 10 and wants keyring support on it, I can make the mods into a git request, but I just wanted to know if anyone beside me would use it before spending the time one it. The other part of the mods was to add support in the gnome_keyring.so and keyring/backend.py to prompt the use for passwords when necessary. This handles cases where the user does not have a valid DISPLAY in their environment. Comes up a lot for GNU screen sessions. I wasn't sure how gnome-keyring handles launching gnome-keyring-ask in later distributions, but it just face plants in 0.4.6, that's in SLES 10, so I wrote console support myself. Anyone interested in either bit of functionality? -- 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] Pitfall with building on oS 11.2 (SUSE_ASNEEDED in environment)
by Peter Pöml 17 Dec '09

17 Dec '09

Hi, I had a failing build on openSUSE 11.2, for no apparent reason. Compiling with -Wall, no error or warning was issued, just: /tmp/ccg01MtC.o: In function `main': /usr/src/packages/BUILD/mirrorbrain-2.11.3/tools/ geoiplookup_continent.c:56: undefined reference to `GeoIP_open' /usr/src/packages/BUILD/mirrorbrain-2.11.3/tools/ geoiplookup_continent.c:57: undefined reference to `GeoIP_database_edition' /usr/src/packages/BUILD/mirrorbrain-2.11.3/tools/ geoiplookup_continent.c:66: undefined reference to `GeoIP_record_by_name' /usr/src/packages/BUILD/mirrorbrain-2.11.3/tools/ geoiplookup_continent.c:60: undefined reference to `GeoIP_country_id_by_name' /tmp/ccg01MtC.o: In function `printf': /usr/include/bits/stdio2.h:105: undefined reference to `GeoIP_country_continent' collect2: ld returned 1 exit status However, the gcc command executed manually in the build system without a problem. After some thinking (I have been building packages for 9 years only), I figured that only something in the environment could be influencing the strange behaviour. A strategically placed 'env' showed that "SUSE_ASNEEDED=1" is exported, and that proved to be the culprit. http://old.nabble.com/Strange-build-behaviour-td26741825.html explains the behaviour. The "fix" is reordering arguments: -gcc $RPM_OPT_FLAGS -Wall -lGeoIP -o geoiplookup_continent geoiplookup_continent.c +gcc $RPM_OPT_FLAGS -Wall -o geoiplookup_continent geoiplookup_continent.c -lGeoIP Critique: --------- IMHO, this could have been made more obvious. The above shown linker error isn't really elucidating. In fact, it doesn't seem to make any sense at all. I doubt that all build service users read the opensuse-specific packaging list. And new users won't know that it might have been discussed there. Some kind of keyword as a start for a Google recherche is lacking. Peter

4 5