December 2009 - openSUSE Build Service

[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

[opensuse-buildservice] sorry for beeing tux
by Jan Loeser 17 Dec '09

17 Dec '09

last commit was by "tux", so i am sorry. it was me and i fixed it in my gitconfig :) regards -- Jan Loeser, Trainee, L3/Maintenance SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] The osc-server monitor have many info flaged by red color.
by Jian Lee 16 Dec '09

16 Dec '09

hi, all the obs have some fuzzle to me: I've setup a obs server on local host, when I open http://myhost:81/monitor, I've found that many task have a red flag display , and the status of task is building when i open the task link. But the job time is very long for those task. Did I can "refresh" the task monitor of obs-server, and get a right monitor ? 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

1 0

[opensuse-buildservice] numactl packaging seems broken
by Jan Engelhardt 15 Dec '09

15 Dec '09

Hi, something is up with numactl. $ osc branch Base:System numactl A working copy of the branched package can be checked out with: osc co home:jengelh:branches:Base:System/numactl $ osc co home:jengelh:branches:Base:System/numactl Link "home:jengelh:branches:Base:System/numactl" cannot be expanded: could not apply patch 'project.diff' Use "osc repairlink" to fix merge conflicts. Jan -- 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] release numbering
by Wolfgang Rosenauer 15 Dec '09

15 Dec '09

Hi, just right now I've updated a few packages but release number generation seems to be heavily confused. It's ignoring Release in spec file, it doesn't count changes within the first digit but only rebuilds in the second one. And it reset the release number to 1 so I don't get the updated package. That's a critical thing, please help. Wolfgang -- 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] Glibc disappears - project building falls apart
by Jan Engelhardt 14 Dec '09

14 Dec '09

Hi, I had a change in home:jengelh:Base:System/glibc, whose submitrequest got accepted. As a result, glibc was removed from the project space - and that looks like a reasonable thing to do. The bad side effect however is that all the other packages have a dependency on that glibc. Since the latter is gone, there is an expansion error. I am not sure why it does not use /Base:System's glibc again after mine got removed. Could someone please investigate and/or reset the metadata? thanks, Jan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] rpmlint error "no binary" for packages that DO contain binaries?
by Mathias Homann 14 Dec '09

14 Dec '09

Hi all, I'm building some stuff, and while the packages are 100% in order, rpmlint complains about "no binaries" even though the packages contain working binaries, in /usr/bin rsp. /usr/sbin. why is that? and is there a more "healthy " fix than a rpmlintrc workaround? 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

[opensuse-buildservice] [patch] build: sparc support
by Jan Engelhardt 14 Dec '09

14 Dec '09

Please consider for merge. The following changes since commit 318c860c5c178c72988ccae149f4c7e6c2f557bf: Michael Schroeder (1): Merge branch 'master' of gitorious.org:opensuse/build are available in the git repository at: git://dev.medozas.de/suse-build master Jan Engelhardt (1): SPARC architecture support Build.pm | 1 + baselibs_global.conf | 6 ++++++ common_functions | 2 ++ 3 files changed, 9 insertions(+), 0 deletions(-) ----------8<---------- parent 318c860c5c178c72988ccae149f4c7e6c2f557bf () commit 6dedaacf1dd51ed6512359814fbe7d7c5af86cff Author: Jan Engelhardt <jengelh(a)medozas.de> Date: Fri Dec 11 22:57:09 2009 +0100 SPARC architecture support --- Build.pm | 1 + baselibs_global.conf | 6 ++++++ common_functions | 2 ++ 3 files changed, 9 insertions(+), 0 deletions(-) diff --git a/Build.pm b/Build.pm index 99ce6bb..f309448 100644 --- a/Build.pm +++ b/Build.pm @@ -32,6 +32,7 @@ my $std_macros = q{ %define arm armv4l armv4b armv5l armv5b armv5el armv5eb armv5tel armv5teb armv6el armv6eb armv7el armv7eb %define arml armv4l armv5l armv5tel armv5el armv6el armv7el %define armb armv4b armv5b armv5teb armv5eb armv6eb armv7eb +%define sparc sparc sparcv8 sparcv9 sparcv9v sparc64 sparc64v }; my $extra_macros = ''; diff --git a/baselibs_global.conf b/baselibs_global.conf index 76fe238..96191bf 100644 --- a/baselibs_global.conf +++ b/baselibs_global.conf @@ -3,6 +3,12 @@ arch i686 targets x86_64:32bit ia64:x86 arch s390 targets s390x:32bit arch ppc targets ppc64:32bit arch ppc64 targets ppc:64bit +arch sparc targets sparc64:32bit +arch sparcv8 targets sparc64:32bit +arch sparcv9 targets sparc64:32bit +arch sparcv9v targets sparc64v:32bit +arch sparc64 targets sparcv9:64bit +arch sparc64v targets sparcv9v:64bit configdir /usr/lib/baselibs-<targettype>/bin diff --git a/common_functions b/common_functions index 8a67511..f27c1be 100644 --- a/common_functions +++ b/common_functions @@ -14,6 +14,8 @@ set_build_arch() i586) BUILD_ARCH="i586:i486:i386" ;; i486) BUILD_ARCH="i486:i386" ;; x86_64) BUILD_ARCH="x86_64:i686:i586:i486:i386" ;; + (sparc64*) BUILD_ARCH="sparc64v:sparc64:sparcv9v:sparcv9:sparcv8:sparc";; + (sparc*) BUILD_ARCH="sparcv9v:sparcv9:sparcv8:sparc";; esac if test "$BUILD_ARCH" != "${BUILD_ARCH#i686}" ; then cpuflags=`grep ^flags /proc/cpuinfo` -- # 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

4 5

[opensuse-buildservice] removing a linkage in a profile
by doiggl＠velocitynet.com.au 14 Dec '09

14 Dec '09

Hello I am trying to remove openSUSE_Factory from my profile and I get a openSUSE Webclient Error: Error Details: Errorcode: project_save_error Message: error saving project: Repository home:doiggl/openSUSE_Factory cannot be deleted because following repos link against it: home:elvigia:branches:home:doiggl/openSUSE_Factory home:psmt:branches:home:doiggl/openSUSE_Factory Questions 1. Who do I send a email to remove the linkage so I remove openSUSE_Factory from my profile ? 2. If thats not possible or there is no response to the request. Who can force the linkage so its removed ? Thanks Glenn -- 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] "Prefer" definitions
by Jan Engelhardt 13 Dec '09

13 Dec '09

Hi, Given the presence of both 32-bit and 64-bit packages, I do encounter this particular problem with build: $ b64 somethingelse.spec [...] expansion error have choice for libpcreposix.so.0()(64bit) needed by pcre-tools<64-bit>: libpcreposix0-64bit libpcreposix0 It can understand why that happens. However, zlib is also present in both bitnesses, and yet there is no error about that. So how would I resolve this problem without adding lots of Prefer: libfooxyz lines to sl11.2.conf? -- 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] obs webclient development tutorial
by Thomas Schmidt 12 Dec '09

12 Dec '09

Hi, I updated the tutorial on how to develop the obs webclient: http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/Ea… It is very easy now to contribute patches by using the gitorious merge request mechanism. Greetings -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux Products GmbH :: Research & Development :: Tools "Don't Panic", Douglas Adams (1952 - 11.05.2001) -- 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] php5 question/issue/proposal ?
by Joop Boonen 11 Dec '09

11 Dec '09

Dear all, I'm building package php5-gtk because of the scan directory I have an issue when php5-gtk is installed in combination with apache2 i.e. for instance cacti doesn't work any more as php tries to start up with php-gtk when it's installed. I think it would be better to have outside of the /etc/php5/conf.d also /etc/php5/apache2/conf.d and /etc/php5/cli/conf.d in which specific ini files can be put that are only used for either apache2 or cli. In my case the php5-gtk.ini would reside in /etc/php5/cli/conf.d as it's a cli implementation only. I think the php5.spec file can be change in the following way: --with-config-file-scan-dir=%{php_sysconf}/conf.d %{php_sysconf}/$sapi/conf.d I've read that --with-config-file-scan-dir can now have more than one directory. Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Build service wiki content (code in svn) is wrong
by Richard Bos 11 Dec '09

11 Dec '09

The link to 'Code in SVN' (https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/backend) on this page http://en.opensuse.org/Build_Service/Product_Definition does not work anymore. Is this page http://en.opensuse.org/Build_Service/Junior_Projects still up to date? -- 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] Packaging baselibs.conf as extra Source
by Jan Engelhardt 11 Dec '09

11 Dec '09

Hi, currently, baselibs.conf are only available as part of a OBS checkout, and since they are not listed as a Source123: baselibs.conf in the .spec files, they will not be in .src.rpms. This leads to local builds not doing baselibs at all. I think baselibs.conf should be added, does anybody disagree? 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] The move to git: what changes for you
by Stephan Kulow 11 Dec '09

11 Dec '09

Hi, The build service is in git now and while svn was simply and easy, git is powerful and more complex. The good news is that the things most of you do are easy with git too. If you head to the power usages, you might need more documentation than this mail. So let me first summarize the basic ideas in svn and git: SVN has one central server and only admins have access to the repository, developers need to access it through a client for almost everything. This includes creating diffs, checking out branches, creating branches, ... SVN also has no specific concept about branches, everything in there are directories, you copy away trunk into another directory (common practise is a subdirectory below /branches, but that's just convention) and then you need to track patches between trunk and the branches your own. There are tools to help with that though. The working copy is a 1:1 representation of one directory of the SVN server. You either have uncommited changes or they are on the server too. GIT has no central server, everyone has full access to the repository and the clients will mainly only exchange their changes. Of course you can put these repositories on servers so it's easier for exchange between several people - that's what gitorious.org (and many others provide). All other actions are done in the local repository of the single developer, you create diffs, checkout branches, commit, create branches, merge branches - all in _your_ repository. Unless you decide to "push" these changes into another repository or "pull" from another repository it's all for yourself. The working copy always contains the full repository (you can limit the download to certain branches and history depth though). So there is a fundamental difference between these two that _is_ a cultural shock - no doubt. But this cultural difference is basically what the whole openSUSE project is all about: SVN is "group of people develops on their server", GIT is "everyone is free to join, no-one has more rights than the other to develop". (You might disagree and I'm oversimplifying) Of course the repository on gitorious.org is protected and not everyone can push to _that_ repository directly without review. But with svn you have to collect patches on your own and keep sending them, with git(orious) you can clone the build-service repository, develop on your own annotating every change you did (keeping track on your own development history) and once you're satisfied you push it as "merge request". This is _very_ similiar to what you do with osc and devel branches. So this should not be new to you. So how do you start? Let me take osc as an example. Checkout: git clone git://gitorious.org/opensuse/osc.git cd osc ./osc-wrapper.py -h Update: git pull Commit to your repository: git commit -a # -a for all files Upload your changes: git push Show the last commit: git show HEAD Show all branches: coolo@desdemona#osc>git branch -a * master remotes/origin/HEAD -> origin/master remotes/origin/jw remotes/origin/master Checkout a branch: # note that this is all locally, no server contacted git checkout -t origin/jw Merge another branch (the short way): git merge origin/master Merge another branch (the long way): coolo@desdemona#osc>git merge origin/jw Auto-merging NEWS CONFLICT (content): Merge conflict in NEWS coolo@desdemona#osc>eclipse NEWS coolo@desdemona#osc>git diff NEWS # see diffs against merge point coolo@desdemona#osc>git add NEWS # mark as resolved coolo@desdemona#osc>git commit # commit manual merge Note the "origin", every remote repository has a name. There can be more than one. As you can clone repositories, you can also register more than one repository "clone" and then merge the changes locally in your repository and push it to a 3rd repository - as I said in the beginning: git is powerful and complex. So my suggestion would be: start with simple things and get used to the commands. You can also clone the repositories on gitorious and play around as much as you like in those clones - they can be discarded in a second if something went wrong :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Re: [opensuse-edu] No updates for packages in openSUSE 11.2 BS repository
by Jigish Gohil 11 Dec '09

11 Dec '09

On Fri, Dec 11, 2009 at 3:15 AM, Kirill Kirillov <kirill.kirillov(a)gmail.com> wrote: > Hi! > > I've found out that packages in Education BS project repository for > openSUSE 11.2 aren't updated after they have been built. > You can compare [1] and [2] > May be someone knows how to fix this issue? > > Thanks in advance. > > [1] > http://download.opensuse.org/repositories/Education/openSUSE_11.1/i586/?C=M… > [2] > http://download.opensuse.org/repositories/Education/openSUSE_11.2/i586/?C=M… > This package is stuck at "finished" since 29th Oct. https://build.opensuse.org/package/show?package=libeigen2&project=Education Can oBS admins please check what is wrong there? I tried abortbuild, trigger rebuild but nothing seem to have any effect on that package. Ciao -J -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] obs webclient development tutorial
by Richard Bos 10 Dec '09

10 Dec '09

Op woensdag 09 december 2009 15:12:53 schreef Thomas Schmidt: > Hi, I updated the tutorial on how to develop the obs webclient: > http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/Ea >sy_OBS_Web_Client_Development Why is 'sa' used in 'zypper sa http://download.opensuse.org/rep.....' in the install section? From the man page (as 'sa' is not listed in zypper --help) 'sa' seems to be for 'rug service-add (sa)' Wouldn't it be easier to understand to use e.g. something like: zypper addrepo <repo> ? In case 'sa' is really is it possible to add an explanation for it? -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] distro repositories management
by schoappied 10 Dec '09

10 Dec '09

Hi, I like to have a distribution project with the following repositories * stable * testing * experimental * non-free How do I manage this the best way? To be able to build for testing, likely a few package are needed which are also needed for stable etc. And the same is true if you package for non-free, you likely need packages from main... So how to do this smartly? Thanks in advance, \r -- 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] Error building python-keyring for Ubuntu:9.10
by Luke Imhoff 10 Dec '09

10 Dec '09

I've been trying to build python-keyring for Ubuntu:9.10 for our local deployment of osc 0.123, but I'm getting this error: creating build/temp.linux-x86_64-2.6/keyring/backends gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wall -g -O2 -fPIC -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-keyring-1 -I/usr/include/python2.6 -c keyring/backends/gnome_keyring.c -o build/temp.linux-x86_64-2.6/keyring/backends/gnome_keyring.o In file included from /usr/include/python2.6/Python.h:8, from keyring/backends/gnome_keyring.c:8: /usr/include/python2.6/pyconfig.h:1028:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/limits.h:27, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/limits.h:122, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/syslimits.h:7, from /usr/lib/gcc/x86_64-linux-gnu/4.4.1/include-fixed/limits.h:11, from /usr/lib/glib-2.0/include/glibconfig.h:11, from /usr/include/glib-2.0/glib/gtypes.h:34, from /usr/include/glib-2.0/glib/galloca.h:34, from /usr/include/glib-2.0/glib.h:32, from keyring/backends/gnome_keyring.c:4: /usr/include/features.h:210:1: warning: this is the location of the previous definition gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wall -g -O2 build/temp.linux-x86_64-2.6/keyring/backends/gnome_keyring.o -ldbus-1 -lpthread -lrt -lgnome-keyring -lglib-2.0 -o build/lib.linux-x86_64-2.6/gnome_keyring.so /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/libgnome-keyring.a(gnome-keyring.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/libgnome-keyring.a: could not read symbols: Bad value collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 make: *** [build-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The error seems to be complaining about building the gnome_keyring backend against the static libgnome-keyring. I believe the makefile is auto-generated by setup.py, so I'm not sure how I force the build to use the .so instead of the .a. Has anyone else tried building python-keyring for a Debian or Ubuntu-based platform? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 8

[opensuse-buildservice] .deb build help -- "can not parse package name from spec file"
by Nicholas Tung 10 Dec '09

10 Dec '09

Hi all, I'm following the documentation at http://en.opensuse.org/Build_Service/Deb_builds for building a .deb file. However, I keep seeing the error, "can not parse package name from spec file". My project is here, https://build.opensuse.org/package/show?package=sketch-cegis&project=home:g… Thanks much, Nicholas — ntung at ntung — https://ntung.com -- 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] New osc 0.124 release
by Adrian Schröter 10 Dec '09

10 Dec '09

Hello, we put out the new osc version 0.124 release in the openSUSE:Tools project. http://software.opensuse.org/search?baseproject=openSUSE:Tools&q=osc The version has a hughe changelog, in addition it fixes also the regression of product building. Using this osc and the new build.rpm from same project you can build products now faster than ever via osc build images i586 --linksource I want to push out this release also a official maintenance release again in 1-2 weeks. Solving esp. the problems of authentification problems of 0.120. So please report here any regression, I am not away of any. Please ask here also when you need further informations about the changes: have fun adrian 0.124 - added 'osc bugowner' as a more intelligent version of 'osc maintainer -B' - added option '-B' to osc maintainer, prints bugowner OR maintainer. - added 'osc req help' as convenience alias to 'osc help req'. - 'osc in' to be done. Its usage just prints a suggested zypper command line. - give better hint how to use osc vc without network connectivity. - added printing of cache statistices to osc build - support http proxies when using python 2.6 or newer (#551004) - partial fix for checkout problems (bnc#551147) - fixed #477690 ("osc fetching binaries really slow") - osc jobhistory accepts also "prj [pkg] repo arch" now - osc buildinfo accepts now also "prj pkg repo arch [spec/dsc]" - osc buildconfig accepts now also "prj pkg repo arch" - fixed warning messages regarding SSL certificate on some plattforms (Fedora) - support submit requests on project level, osc is checking which packages have changed and submits only the changed after asking back. - show worker/id on jobhistory and make it faster by adding a default limit of 20 - add "osc build --root" option to allow to specify build root directory - add "osc build --release" option to allow to specify a package release number - added osc mv command which can rename file and leave them under version control - added new commands "dependson" and "whatdependson" to find out which packages get triggered before checkin/request accept. - add new "osc build --linksource" option, speeds up esp. image building a lot - add "osc triggerreason" command to show detail reason, why a package got triggered for build - Incompatible changes: * osc se now prints Project Package, instead of Package Project for easier copy&paste. * osc se uses exact search by default. Use osc se -s for substring search * osc repourls neither needs nor accepts a path to a package working dir anymore * osc repo neither needs nor accepts a path to a package or project working dir anymore # # Features which require OBS 1.7 # - search: allow to limit results via existing attibutes - added "osc meta attribute" for basic attribute creation, deletion, showing and value setting - implement "osc mbranch" call to create projects with multiple source package (instances) - new "osc patchinfo" command: basic patchinfo generation and modification support - add support for _patchinfo package submissions in "osc sr" on project level - support review handling of requests (new "osc review accept/decline $REQUEST_ID" command -- 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