May 2006 - openSUSE Build Service - openSUSE Mailing Lists

Namespaces
by Marcus Rueckert 06 Jun '06

06 Jun '06

hi, on irc we had a discussion about adding some logical namespaces. It was started by looking for the right place for a php project. we now agreed on having a "server:" namespace. the first proposed projects in that namespace we see: server:apache (the former Apache project) server:mail (exim and home:choeger:postfix could be moved there) server:ftp server:php (php project, and php extensions, and my hardened php package) server:dns (i will move my pdns, mydns, nsd packages there. maybe the bind and dnsmasq package could move there aswell?:) ) It would be nice to have a server:voip aswell. peter nixon has some packages in that area iirc. :) The jpackage projects are moved into the Java: namespace. Some people might ask: why dont you just move php into the apache project. The answer is pretty short: Because it makes its impossible to build newer php against older apache versions. with the new layout we can add server:apache:<somedist> as build target to the php project aswell as the plain suse distros. :) So in long term i would suggest to join such logical project instead of having multiple "mixed purpose projects". if you want to add a package to such a project please contact the project owner on this list. keep up the good work everyone darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

12 34

Fedora Extras
by Peter Nixon 02 Jun '06

02 Jun '06

Hi Guys A number of my packages require "cppunit-devel" which is available natively on SUSE but on Fedora it is part of the "Extras" repository which doesn't appear to be available on the Build Service. How do you suggest I handle this dependency? -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

3 3

java-1_5_0-sun-devel dependency
by Peter Nixon 02 Jun '06

02 Jun '06

How can packages that require java-1_5_0-sun-devel and other java packages be built on the build service which appears to only include OSS packages? -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

4 5

RE: [opensuse-buildservice] Fedora Extras
by Bernard Li 31 May '06

31 May '06

Hi Adrian: Sounds good. I in no way want to add any additional work on you guys, I was just wondering when they will be available - and I think the system has been working fairly well, despite its alpha state :-) Keep up the good work! Cheers, Bernard ________________________________ From: Adrian Schröter [mailto:adrian@suse.de] Sent: Wed 31/05/2006 09:34 To: opensuse-buildservice(a)opensuse.org Subject: Re: [opensuse-buildservice] Fedora Extras Am Wednesday 31 May 2006 18:24 schrieb Bernard Li: > That's fair enough... :-) > > BTW, I guess these base distroes can only be maintained by the buildservice > staff? Would it be possible to have these community maintained in the > future? > > Just a suggestion :> I do not see a near solution to get them maintained by non-root account people on the storage system (which is currently limited to very few people (less than 5)). However, that does not mean that the community does not have influence in how to configure it. We can do a poll of wanted targets for example. The sysadmin is only the poor executor in the end ... bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany 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

2 1

entering repoview
by Christoph Thiel 31 May '06

31 May '06

Hi everyone, we have enabled repoview to make browsing the repositories more useable. This also introduces RSS feeds for all repos. (Some repos might not have the repoview browsing + rss feeds yet, as they are getting those once they are pushed into software.openSUSE.org and it's mirrors.) To get an idea of how it looks like, refer to [1] for the browsing part and to [2] for the RSS feed. I would like to theme the repoview pages a bit more openSUSE-like, but I'm currently busy with other stuff. So, if there is anyone who would like to work on the repoview template, please speak up now! The openSUSE.org wiki or the brand-new build.openSUSE.org theming offer all the stuff that you need, in terms of colors. The repoview package is available from my home project in the openSUSE Build Service (at [3]). Regards Christoph [1] http://software.opensuse.org/download/repositories/home:/cthiel1/Factory/re… [2] http://software.opensuse.org/download/repositories/home:/cthiel1/Factory/re… [3] http://software.opensuse.org/download/repositories/home:/cthiel1/

1 0

RE: [opensuse-buildservice] Fedora Extras
by Bernard Li 31 May '06

31 May '06

That's fair enough... :-) BTW, I guess these base distroes can only be maintained by the buildservice staff? Would it be possible to have these community maintained in the future? Just a suggestion :> Thanks, Bernard ________________________________ From: Adrian Schröter [mailto:adrian@suse.de] Sent: Wed 31/05/2006 09:17 To: opensuse-buildservice(a)opensuse.org Subject: Re: [opensuse-buildservice] Fedora Extras Am Wednesday 31 May 2006 18:08 schrieb Bernard Li: > Hi Marcus: > > This is very useful, thanks for setting it up! > > BTW, do you (or anybody else), have an idea when the x86_64 repositories > for FC4 and FC5 will contain all the RPMs? It does not have a priority atm for me. Find some more people to complain about that ;) -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany 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

2 1

RE: [opensuse-buildservice] Fedora Extras
by Bernard Li 31 May '06

31 May '06

Hi Marcus: This is very useful, thanks for setting it up! BTW, do you (or anybody else), have an idea when the x86_64 repositories for FC4 and FC5 will contain all the RPMs? Thanks, Bernard ________________________________ From: Marcus Schäfer [mailto:ms@suse.de] Sent: Wed 31/05/2006 03:56 To: opensuse-buildservice(a)opensuse.org Subject: Re: [opensuse-buildservice] Fedora Extras Hi, > A number of my packages require "cppunit-devel" which is available natively on > SUSE but on Fedora it is part of the "Extras" repository which doesn't appear > to be available on the Build Service. > > How do you suggest I handle this dependency? I have synced an extras repositories and asked Adrian to put it on the server. That's because I need packages from the extras repository as well. I think we will have "extras" as a seperate project available soon. Adrian should know more Regards Marcus -- Public Key available ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org

2 1

Update of API and Webclient
by Andreas Bauer 31 May '06

31 May '06

Hi, I'm going to update the servers api.opensuse.org and build.opensuse.org at 15:15 (3:15 PM) CET. Downtime will be ~15-30 minutes. -- Andreas Bauer - Novell - SUSE Internal Tools

1 1

announcing packages
by Marcus Rueckert 30 May '06

30 May '06

hi, as we noticed in the namespace thread we always have the problem that we can run into duplicated packages. i think we should try to avoid that as much as possible. lets cooperate. so i would like to suggest again: 1. announce newly created packages no this mailinglist. if you needed to fork the package please mention why. 2. consider using the namespaces so we have all related packages in some common place. I will start with my packages now. please see the attached text file. :) today i started a server:php project but i havent figured out how to name the packages there yet. i am mainly interested in maintaining the hardened php package. thats all from me for now. :) i think external packagers (packman, guru, usr-local-bin) could do the same. :) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

1 1

linking packages
by Marcus Rueckert 30 May '06

30 May '06

hi, when ever possible avoid copying the package. you can use the linking feature to pull 3rd party packages into your project. that means you dont have to maintain/update the package and still have the package in your area. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

1 0

BS provides no benefit for me
by Pascal Bleser 30 May '06

30 May '06

(moving this thread from smart-maintainers to opensuse-buildservice, I think its content is more relevant here ;)) Christoph Thiel wrote: > On Mon, 29 May 2006, Pascal Bleser wrote: > >>>> And Christoph because you might want to check whether you've got all >>>> of those patches in the SL10.1/Factory smart RPM (but if you do a new >>>> build, please don't have a release >= 25 that supersedes my package >>>> again ;D). >>> >>> I'll check our smart package soon. Now, that we have the openSUSE >>> Build Service up and running, we might consider working on the smart >>> package together and share the maintainership. How about that? >> >> I don't think so. >> >> Well, we could, and I would base my own spec on the one in the build >> service (though there wouldn't be any benefit for me, rather the >> opposite, it would be more work). >> >> The buildservice is not interesting to me ATM because >> >> 1) the buildservice is not advertised anywhere as a repository for >> packages (as opposed to > 50% of SUSE Linux users already using my >> repository) > > We will be promoting the Build Service very aggressively soon. A re-design > of the web frontend is on the way and the commandline tools already work > very well (IMO). OK. But the web frontend currently is only targeted at packagers AFAIK. I really mean the end-user side of things. Don't know whether there are plans to also design an interface that's usable for end-users. And if so, what those plans look like. Unfortunately, it's all happening behind the SUSE curtain :( Navigating the BS repositories/directories is currently a PITA because there's no real concept for how those should be organized (I *don't* think putting stuff into home:/home:pbleser/smart would be a good idea, for example). There must be a single summary page that lists all the projects and packages that are in the BS. >> 2) I preconfigure my smart package with a lot of channel files, >> including packman and guru so... legal issues ? > > Indeed -- but I'd rather split those channel files into a new package and > have smart depend on it (or suggest it). I might even be able to put a > channel package into SUSE Linux, with a reduced set of channels. Mmmmmyeah, that would be a technical option, but not a good thing for end-users IMO. When I look at the current situation with 10.1 and its broken zypp, end-users are already struggling to install my smart RPM (mostly because it depends on rpm-python, that is not installed by default) and have to jump a few hoops because YaST2 or rug just won't work on their system: http://dev-loki.blogspot.com/2006/05/how-to-install-and-use-smart-on-suse.h… http://spinink.net/2006/05/20/installing-smart-package-manager/ So adding another package/dependency would make things even more complex. And from a technical POV, if I put those channels into, say, smart-suse-channels.rpm, you can't really make smart.rpm depend on it because smart-suse-channels.rpm won't be in the Build Service. >> At some point, smart will be in the packman repository, and then the >> BuildService becomes even less interesting: >> - no mirror infrastructure yet > > This is WIP at the moment. We already push to ftp-1.gwdg.de and another > mirror. Check out http://software.openSUSE.org/ Yes, I've read Adrian's mail about that. Good news :) >> - no web frontend as with packman [1] >> [1] see http://packman-test.links2linux.org > > ;) No kidding, it's really an advantage of hosting it at Packman instead of the Build Service ;) >> But as for maintaining the smart package for Factory, yes, we could do >> it together in the BuildService (if that's already feasible with the >> current implementation of BS) so when I add patches to my package, I can >> also add them to the smart project in the BuildService. > > Exactly -- have you tried osc (the python cmdline client to the openSUSE > Build Serivce)? I gave it a quick shot which was not very concluding, but mostly because I didn't know where to create my projects (sent a mail to opensuse-packaging two weeks ago but no reply, and it's been reorganized anyway). I definitely have to give it another shot. osc is obviously the approach that I prefer and suits me best, a simple CLI client (and not a web frontend). Thanks to Peter for writing it :) I don't want to discard or discredit your efforts on the BuildService, but I really don't see any advantage for me in using it at the moment, it's rather the opposite: - I build for SUSE 9.1 -> 10.1, and only 10.0, 10.1 and Factory are in the BS as of now (AFAIK) - no web frontend for end-users as I'll have with Packman Note that I don't care at all about building for other distributions. What would make the BS more compelling to me would be to have a ppc build target (and providing what I'm missing, above ;)). Of course, that's my very personal POV, in the light of building packages that are not provided at all on SUSE Linux or that could only be built as a crippled subset because of potential legal/patent issues. It's a totally different case concerning packages that are already in the distribution, that I could co-maintain directly and that are built as full-fledged because they're not in the gray legal/patent realm. cheers -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v http://www.fosdem.org http://opensuse.org

8 11

RE: [opensuse-buildservice] Mandriva 2006 check in spec file
by Bernard Li 30 May '06

30 May '06

Hi Adrian: I don't think that works (just tested it). BTW, on Red Hat/Fedora, /usr/lib/libfreetype.a is provided by freetype-devel, however, it is provided by libfreetype6-static-devel on Mandriva 2006, so perhaps you want to add that to your mapping such that freetype-devel on Red Hat/Fedora expands to freetype-devel and libfreetyp6-static-devel. P.S. Build on Mandriva 2006 gives: "error: cannot open Pubkeys index using db3 - No such file or directory (2)" - not sure if this is known issue or not. Cheers, Bernard ________________________________ From: Adrian Schröter [mailto:adrian@suse.de] Sent: Mon 29/05/2006 22:56 To: opensuse-buildservice(a)opensuse.org Subject: Re: [opensuse-buildservice] Mandriva 2006 check in spec file Am Tuesday 30 May 2006 04:13 schrieb Bernard Li: > Hi Guys: > > Anybody knows the equivalent of "%if %{?suse_version:1}0" under Mandriva > 2006? does %if %_host_vendor = "mandriva" work ? -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany 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

2 1

Mandriva 2006 check in spec file
by Bernard Li 30 May '06

30 May '06

Hi Guys: Anybody knows the equivalent of "%if %{?suse_version:1}0" under Mandriva 2006? Thanks, Bernard

2 1

Dependency question
by Peter Nixon 29 May '06

29 May '06

Hi Guys I am building a bunch of packages at present (sipxpbx) which have a convoluted set of dependencies. As it turns out all of the dependencies are provided by SUSE 10.1, some are missing in 10.0 and many more are missing in 9.3 For example, one set of dependencies is "ruby, rubygems, rake". Now, given that these are all provided by SUSE 10.1, how can I provide these packages to SUSE 10.0 and 9.3 users? I could of course take the source rpms from 10.1, and add them to my project, but that then means to I am providing a package for 10.1 which already exists.. At a minimum I would like a way to enable/disable build targets per package, which would make this solution workable. A more preferable solution (although one that may require a bit more work) would be the ability to link a SUSE 10.1 package into my project which should then be transparently built for my other build targets if they don't provide it. Is this possible? Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

2 3

chown failed - Read-only file system
by Peter Nixon 29 May '06

29 May '06

Ooops.. Someone (hopefully not me) appears to have broken something: reordering...done installing filesystem-10.1-5 error: unpacking of archive failed on file /proc: cpio: chown failed - Read-only file system http://build.opensuse.org/package/live_build_log?arch=i586&package=sipxprox… -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

2 1

File upload bug in web interface
by Peter Nixon 29 May '06

29 May '06

Hi guys There appear to be some bugs in the way the build service web interface handles uploads. This happened to me before, but I thought I must have made a mistake, however last night the same thing happened again. I started 3 separate file uploads to 3 different packages: http://build.opensuse.org/package/show?package=sipxconfig&project=home%3Ape… http://build.opensuse.org/package/show?package=sipxcalllib&project=home%3Ap… http://build.opensuse.org/package/show?package=sipxvxml&project=home%3Apete… However, when the uploads were finished, all three uploaded files were in one of the packages, and nothing had been uploaded to the other two! See: http://build.opensuse.org/package/show?package=sipxvxml&project=home%3Apete… -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

2 3

Linking packages from released distributions
by Christian Boltz 26 May '06

26 May '06

Hello, I wanted to create a modified courier-authlib package (to be exact: with added mysql backend, requires just a specfile patch AFAIK) for 10.1, but wasn't able to link to the package. Michael Schröder told me that the sources for 10.1 were not uploaded - I think this should be changed ;-) The reasons why I do not want to link to the Factory package are the same with for YOU updates - I want to minimize the changes I need to do to the whole system (so: no version upgrades) and would like to have an automated package rebuild in case there's a security update for courier-authlib. Of course, I can upload the 10.1 sources myself - but I don't consider this a very good idea... BTW: Can I upload a src.rpm instead of a tarball also? Regards, Christian Boltz PS: Maybe wildcard linking would be an interesting feature ("link to package foobar from the distributions I'm building packages for") - but in this case you would need the option to apply a patch to a limited set of your build targets. The alternative is to create a project per target distribution and to apply the patch to the distributions that need it. -- wie jeder weiß ist Debian auf ISDN die langsamste bekannte Methode Selbstmord zu begehen ("Selbstmord durch Erosion") [http://blog.koehntopp.de/archives/113-Debian-ist-doch-schlecht..html]

3 4

Build target naming
by Christian Boltz 26 May '06

26 May '06

Hello, when adding a build target (say "SUSE:SL-10.0/standard") I can enter a name for that target. Browsing around on software.opensuse.org, I found several different names for the same distribution: - SL10.0 - SuLi100 - SUSE_Linux_10.0 This is not very user-frendly. I think the naming should be more standardized - at least in a soft way: When choosing something in the "Platform" dropdown, the "Name" field should be filled with the name of the selected Platform as default. In case someone builts on top of another project (like a package for KDE4 on SL 10.1), the default should be the underlying distribution (here: SL 10.1). Opinions? Regards, Christian Boltz -- >> I was already 21 when color tv got introduced in Germany... > Old Fart, ain't cha? <grin>.... Oh no. Linux is keeping you young, and OpenSUSE even can make younger. SUSE people, please tell this your marketing team. ;-)) [Eberhard Moenkeberg and > Patrick Shanahan in opensuse]

2 2

BS status and rebuild ...
by Adrian Schröter 25 May '06

25 May '06

Hi, we do support now the new ftp directory layout for the repositories. The packages and repositories do get signed with a new openSUSE build service key. The bug not to remove all subpackages got fixed as well. What does this mean ? We are ready to get synced from our mirrors and that means we can really provide usefull rpms now with the build service :) I will trigger soon a complete rebuild to have only signed rpms and the new directory layout everwhere. This is hopefully the last complete rebuild we will ever need, because our basic configuration for the repositories should be final now. Do not wonder, when your rpms in software/repos.opensuse.org do disappear, it is because of the rebuild. Next steps: * get mirrors (I will write a mail to our mirror admins). * stop classic ftp.suse.com supplementary and project updates and get the SUSE packagers on the openSUSE build service * support export of debian packages * rename Fedora, Mandriva and Debian distros to use the namespaces as well (Fedora:4 instead of FC4 for example). * add SUSE Linux 9.3 and SLES 9 targets * add Ubuntu target. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de

1 0

Java in "SUSE:SL-10.0/standard" but not "SUSE:SL-10.1/standard"
by Peter Nixon 23 May '06

23 May '06

OK. It now appears that java-1_5_0-sun-devel is available in "SUSE:SL-10.0/standard" (excellent...) but not "SUSE:SL-10.1/standard".. Can it be added to "SUSE:SL-10.1/standard" also? please? -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

1 0

rpm macros in Fedora_Core_5
by Daniel Bornkessel 23 May '06

23 May '06

Is it possible that some RPM-macros are missing in Fedora_Core_5? Up to now I came across _jvmdir _jvmjardir ... I think they should be there since they are used throughout the jpackage project which [I think] uses a lot Fedora for a build system -- I could be wrong though. Thanks, -- Daniel Bornkessel Tel: +49 911 740 53 161 Novell :: SUSE R&D :: Internal Tools / Java Packaging ______________________________________________________________________ :wq

4 6

Mandriva 2006: missing packages
by Daniel Bornkessel 23 May '06

23 May '06

Hi. Trying to build some packages, I got an expansion error on Mandriva2006: nothing provides gcc-java The package there is called 'gcc-java', I checked. Can we add it? Thanks, -- Daniel Bornkessel Tel: +49 911 740 53 161 Novell :: SUSE R&D :: Internal Tools / Java Packaging ______________________________________________________________________ :wq

2 2

expansion error (FC)
by Bernard Li 23 May '06

23 May '06

On Fedora Core (4 and 5), I'm getting expansion errors which shouldn't occur: nothing provides /usr/bin/symlinks (this should be provided by the symlinks package, perhaps the system does not currently support file based requires?) [x86_64] nothing provides libpng-devel (there should be a x86_64 RPM for libpng-devel) Thanks, Bernard

1 0

Fedora Extras for FC4/5
by Bernard Li 23 May '06

23 May '06

Hello there: I've just recently joined the list and have started using the build service - it is pretty neat! I was wondering if it will be possible to include Fedora Extras for FC4/5, they contain a bunch of extra RPMs not included in the standard distributions. Also, has any group built rrdtool-devel for FC? I need that for building the ganglia package. Thanks! Bernard

1 0

BuildRequires SuSE <-> RedHat...
by Marcus Schäfer 23 May '06

23 May '06

Hi, the build server builds my package (sax2) for SuSE dists just fine but to build for RedHat (FC5) I'm using a different spec file. The main reason for this are the package name differences within the BuildRequires statement. For example: SuSE: ghostscript-fonts-std FC5: xorg-x11-server-sdk The package structures on RedHat are very different from the SuSE ones. So it's in many cases not only the name which is different. How do I handle this within one spec file in the opensuse build service ? Thanks Regards Marcus -- Public Key available ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------

5 12

status update ..
by Adrian Schröter 19 May '06

19 May '06

Hi, we have updated the Factory distro in the BS yesterday, we have also renamed some project names (people did build against "openSUSE" because they thought it was a distribution, but it is only the tool set for the build service). This triggered some hundred build jobs and we seem to have a technical problem in the backends atm, which slow downs the build. So the turn around times of a build job are quite long atm, we will of course look in the backend problem and we will enable some more build hosts to become faster again. I hope we will be fine again tomorrow. (current state, 350 build jobs are in "waiting" state) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de

1 0

Strange problem
by Peter Nixon 12 May '06

12 May '06

Hi Guys I am attempting to rebuild the Postgresql package from Factory on SUSE 10.0 at: http://build.opensuse.org/package/show?package=postgresql&project=home%3Ape… I am getting the build error: error: File /usr/src/packages/SOURCES/postgresql-fpic.patch: No such file or directory However that file is most definitely in the list of "Files". Am I going insane or is there a problem here? Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

2 3

kernel builds
by Dmitry Mishin 11 May '06

11 May '06

Hi, is it possible to build SuSE kernels in buildservice? ----------------------------------------------------------------- I have the following modifications for kernel-bigsmp.spec: 23c23 < Release: 28 --- > Release: 1.1 ----------------------------------------------------------------- ----- building kernel-bigsmp.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- chmod: cannot access `/usr/src/packages/SOURCES/make-symsets': No such file or directory error: Architecture is not included: x86_64 full log may be accessed at home:openvz/kernel/ -- Thanks, Dmitry.

2 9

opensuse-commander
by Dr. Peter Poeml 11 May '06

11 May '06

Hi, I want to share with you a primitive script which allows copying files from and to the buildservice server. It is probably similar (and likely inferiour) to the opensuse-commandline tool from Christopher Hofmann http://build.opensuse.org/package/show?package=opensuse-commandline&project… and the primary reason I didn't build on it is that it wasn't accessible at the time I wanted to try it out ;) However, I also like the idea of having the functionality in a python library. It can be found here, and if anyone wants to extend it please contact me to get write access: http://svn.poeml.de/svn/osc http://svn.poeml.de/viewcvs/osc/ To explain what's currently implemented, here are usage examples: # list contents opensuse-commander.py ls opensuse-commander.py ls Apache opensuse-commander.py ls Apache subversion # show xml meta opensuse-commander.py meta Apache opensuse-commander.py meta Apache subversion opensuse-commander.py id username # check out sources mkdir subversion cd subversion opensuse-commander.py co Apache subversion [file] vi *.spec opensuse-commander.py diff Apache subversion [file] opensuse-commander.py ci Apache subversion file1 [file2...] (I hope I got that right, it is partly from memory) Regards, Peter -- SUSE LINUX Products GmbH Thought is limitation. Research & Development Free your mind.

3 5

Build management and dependencies
by Marc Lijour 10 May '06

10 May '06

Hi I am part of a team which is working on the development of a Linux distribution (such as SUSE), as part of the European EDOS project (http://www.edos-project.org) We have developed some tools to manage package dependencies which you may find useful. For example, anla (http://brion.inria.fr/anla/) a package exploration utility to spot and to trace dependency problems over time (currently working with a Debian package pool). anla depends on other tools such as ceve, a parser written in ocaml for deb, rpm and other files, and a SAT solver. One of the goals of the EDOS project is to maintain a set of packages on the server side (avoiding dependency issues), but we are also interested in "thinning" a distribution, that is producing a Linux "CD" (for example) containing a requested set of packages, and the minimal set of packages which are necessary to complete the dependency requirements, nothing more. Another interest of ours is the rebuilding of a distribution from scratch, in such a way that a user can reproduce the binaries shipped to him by using only the sources coming with them. The EDOS project also deals with the diffusion of the package (a P2P system is under development) and the testing domain (a portal is also being developed). We would like to know about the issues you may face in your build management project and we would be glad to bring our expertise. We also want to ensure that our tools will work for the SUSE user. All the best, Marc Lijour

2 1

expansion error on multiple BuildRequires
by Stefan Gerlach 09 May '06

09 May '06

Hi, When using multiple BuildRequires for different distributions like ------- %if %{suse_version} > 1000 BuildRequires: qt3-devel kdelibs3-devel %endif %if %{fedora_version} > 1 BuildRequires: qt-devel kdelibs-devel %endif ------- i always get "expansion error" for all distributions. is this a know issue or can this be fixed in any way? The same spec files works without a problem when building outside of the build service. BTW : it would be nice to know some details about the "expansion error". see https://bugzilla.novell.com/show_bug.cgi?id=154055 Regards, Stefan

4 4

Abstract package build description - SoC
by Rajagopal Natarajan 07 May '06

07 May '06

Dear OpenSuse-buildservice developers, I am interested in Abstract package build description and had applied for it. I would like to know who would be the possible mentor and would like to hear any comments regarding my application for the same. I would be available on IRC freenode server as tuxplorer. Hoping to work on the project. Thanks and regards, N.Rajagopal

2 4

Abstract package build description - Regarding SoC Application
by Rajagopal Natarajan 04 May '06

04 May '06

I've applied for "Abstract package build description" project through SoC. I had added a link to a diagram to explain the concept of my proposal.. I had made a small mistake while uploading the diagram, which I noticed and corrected. If any mentor had seen the application in the mean-time, plz excuse me for the same and kindly visit the link again. Sorry for the mistake and inconvenience. Thanks and regards, N.Rajagopal -- N. Rajagopal, Visit me at http://www.rajagopal.tk

1 0

expansion error ...
by Adrian Schroeter 03 May '06

03 May '06

Hi, the famous expansion error has received some improvements. The front-end does show now, which package can't get resolved. I have added also some mappings for the Fedora distributions, were the package names are different. The mappings are: Substitute: db db4 Substitute: db-devel db4-devel Substitute: te_latex tetex-latex Substitute: xorg-x11-devel xorg-x11-proto-devel xorg-x11-trans-devel Substitute: qt3 qt Substitute: qt3-devel qt-devel Substitute: kdelibs3 kdelibs Substitute: kdelibs3-devel kdelibs-devel Substitute: kdegames3 kdegames Substitute: openldap2 openldap Substitute: openldap2-devel openldap-devel Substitute: xorg-x11-Mesa-devel mesa-libGL-devel The Mandriva distro does still miss a number of -devel packages, which is causing the expansion error atm. Please notify us, when you run in a expansion error, where you know that the other distros do use different package names. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de

8 14

About the buildservice gui (SoC)
by Jonh Arson 01 May '06

01 May '06

Seen OpenSUSE and more specifically the build service is a registered organization for this year summer of code, i dunno much about QT (always looked for a reason to learn it actually) maybe more familiar with GTK and Gnome stuff. Seem to me doing a GUI interface for the service could be a really interesting project (learning experience too). Any way i could know who are the mentor at SUSE and if i get a chance to qualify.

2 1