openSUSE Build Service December 2009

buildservice@lists.opensuse.org

50 participants
75 discussions

[opensuse-buildservice] php5 question/issue/proposal ?

by Joop Boonen

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

11 years, 1 month

[opensuse-buildservice] Build service wiki content (code in svn) is wrong

by Richard Bos

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

11 years, 1 month

[opensuse-buildservice] Packaging baselibs.conf as extra Source

by Jan Engelhardt

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

11 years, 1 month

[opensuse-buildservice] The move to git: what changes for you

by Stephan Kulow

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

11 years, 1 month

[opensuse-buildservice] Re: [opensuse-edu] No updates for packages in openSUSE 11.2 BS repository

by Jigish Gohil

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

11 years, 1 month

Re: [opensuse-buildservice] obs webclient development tutorial

by Richard Bos

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

11 years, 1 month

[opensuse-buildservice] distro repositories management

by schoappied

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

11 years, 1 month

[opensuse-buildservice] Error building python-keyring for Ubuntu:9.10

by Luke Imhoff

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

11 years, 1 month

[opensuse-buildservice] .deb build help -- "can not parse package name from spec file"

by Nicholas Tung

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

11 years, 1 month

[opensuse-buildservice] New osc 0.124 release

by Adrian Schröter

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

11 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service December 2009