openSUSE Build Service May 2007

buildservice@lists.opensuse.org

54 participants
71 discussions

[opensuse-buildservice] linking to packages built with the build service

by Robert Schiele

Hello! Currently there is no way to link to a package built on the build service because if we do so this link will break on every rebuild since the release number will change. Because of that I recommmend to automatically create symbolic links without the version number as we have in the update directories on ftp.suse.com. For example: zypper.rpm -> zypper-0.6.15-0.1.i586.rpm If we do so we can just link to http://software.opensuse.com/download/.../packagename.rpm. This link will never break due to an automatic rebuild. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."

14 years, 4 months

[opensuse-buildservice] Factory java-devel expansion error

by Peter Nixon

SUSE_Factory expansion error have choice for java-devel: java-1_4_2-cacao-devel java-1_4_2-gcj-compat-devel -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 5 months

[opensuse-buildservice] RFC: osc support for SLES9 / Python 2.3

by Dr. Peter Poeml

SLES9 ships with Python 2.3. With my latest code changes, I noticed that I changed things in a way incompatible to Python 2.3 (using decorators). (I basically noticed this because byte-compiling failed according to the build log, although the build didn't actually fail due to that. I saw it by pure luck.) This can easily be fixed, so I removed the decorators and started to test osc on SLES9, and found more problems on the way. Python 2.3 didn't have a cookielib module, and it is not easy to add it because parts of it live integrated in the urllib2 module. Still, it is straightforward to just skip cookie support if not available. But there were further problems, which prevent the current codebase from working with Python 2.3. I fixed some further issues, and got as far as to a working 'osc build'. However, the next problem I'm facing is that I can't commit files (gets an internal server error back), and since urllib2 is not as easy to debug as newer versions, I stopped there for now. Overall, the situation gives me the impression that osc hasn't been working on SLES9 lately, or maybe since a long time, and nobody did ever complain about it. The download statistics show 6 or 7 osc package downloads in the last 50 days for SLES9. What do you think. Is it worth pursuing this further? Or should we maybe simply no longer build osc for SLES9? All other platforms in the buildservice seem to have Python 2.4 or newer. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development

14 years, 5 months

[opensuse-buildservice] osc commands for showing/editing metadata

by Dr. Peter Poeml

Hi, while looking at adding support for editing project configuration, I thought that I'd like to organize osc subcommands that show or change metadata in a more consistent way. I have written down some ideas, that involve some renaming, and I'm wondering what would make most sense to most people: 1) current: new (read): new (write): usermeta,edituser showuser edituser meta,editmeta showpacmeta editpacmeta meta,editprj showprj editprj meta,editpac showpac editpac updatepacmetafromspec editpac --fromspec - showprjconf editprjconf This swamps the "osc help" output with new commands... but they will at least appear together, since alphabetically sorted... 2) Only have a "showmeta" and a "editmeta" subcommand, which take their own subcommand specifying what kind of metadata to work on: showmeta user showmeta prj showmeta prjconf showmeta pac editmeta user editmeta prj editmeta prjconf editmeta pac [--fromspec] 3) Or maybe even put them under a single subcommand, "meta": meta [--edit] user meta [--edit] prj meta [--edit] prjconf meta [--edit] pac Anyone has an opinion on that? Thanks, Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development

14 years, 6 months

[opensuse-buildservice] modification of the release tag

by Dries Verachtert

Hello, Where can i find the piece of code which alters the release tag of the spec file? Is there maybe a way to avoid or influence this behaviour? For example the following is logged in the build log: I have the following modifications for aget-openSUSE_10.2.spec: 10c10 < Release: 5.2.opensuse10.2.rf --- > Release: 17.1 How is the '17' and the '1' calculated? Is it possible to append or prepend something? kind regards, Dries --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

[opensuse-buildservice] BuildRequires and Requires handling in OBS (was: [opensuse-packaging] automatic backporting of Factory packages)

by Pavol Rusnak

Hi all! A week ago there was a discussion on packaging ml about "backporting of Factory packages" initiated by Stanislav Brabec. He wrote that he has script to handle BuildRequires and Requires replacements in spec files. (That means, automatic adding of %if %suse_version when needed). We learned that BuildService already does this but only for BuildRequires. Stanislav Brabec wrote: > It would be nice to adapt Requires, too. It's not so complicated and the > fixing rule is exactly the same as BuildRequires need, so it should be > trivial. What about Requires? Any news on this issue? It would be really great if BuildService took care of both BuildRequires and Requires changes. More and more -devel packages are being created in Factory and -devel packages tend to require another -devel packages, which complicates building against older repositories. Global package mapping should be made publicly visible and there should be an easy way how to add new mappings to this global list (contact to competent person is sufficient). -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

[opensuse-buildservice] BuildService and the :

by Dirk Stoecker

Hello, I asked myself, why the buildservice uses the ":" as seperation character? This makes some trouble in commandline, as : must always be escaped and also it looks strange from users side. Wouldn't it be better to introduce "/" in it's full meaning? The repositories are already stored hierarchical on the download servers. Having the same in the buildservice would be nice. E.G. my home:dstoecker:perl would be nice to have as link perl in home:dstoecker. (or better home/dstoecker/perl). I know that would probably be a bigger change right now, but it would make the buildservice compatible to the general Unix path conventions. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

[opensuse-buildservice] Update to rrdtool in Fedora Core 6 repository?

by Bernard Li

I am currently trying to build the Ganglia package: http://build.opensuse.org/package/show?package=ganglia&project=OSCAR It requires rrdtool for build -- however, the version in the FC6 repository is 1.0.50 but the current version in FC6 extras is 1.2.23-3.fc6: http://download.fedora.redhat.com/pub/fedora/linux/extras/6/i386/ Can this be updated? In general, when/how often are these packages updated? On a slightly different topic, my ganglia spec file builds both arch-specific and noarch packages (ganglia-gmond and ganglia-gmetad are arch-specific, ganglia-web is noarch). How can I get both types of packages built in the BS? Thanks, Bernard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

[opensuse-buildservice] kdebase3 3.5.7 build

by Günther J. Niederwimmer

Hello, have any a hint, for building the x86_64 32bit kdebase3 ? On my system I have allways (i586, x86_64, baselibs) a error: Bad exit status from /var/tmp/rpm-tmp.30274 (%build) I have the last build from repositories ? -- mit freundlichen Grüssen / best Regards Günther J. Niederwimmer --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

[opensuse-buildservice] osc copypac fails

by Herbert Graeber

Hi, Darix asked me to copy another users project into devel:languages:haskell using "osc copypac". But this worked only partially. It creates the project and added the user m4r3k as maintainer, but it failed copying the files: > herbert@sirius:~> osc copypac home:m4r3k hugs98 devel:languages:haskell > Sending meta data... > Copying files... > hugs98-plus-Sep2006.tar.gz > Traceback (most recent call last): > File "/usr/bin/osc", line 10, in <module> > sys.exit( osc.main() ) > File "/usr/lib64/python2.5/site-packages/osc/cmdln.py", line 240, in main > return self.cmd(args) > File "/usr/lib64/python2.5/site-packages/osc/cmdln.py", line 263, in cmd > retval = self.onecmd(argv) > File "/usr/lib64/python2.5/site-packages/osc/cmdln.py", line 379, in onecmd > return self._dispatch_cmd(handler, argv) > File "/usr/lib64/python2.5/site-packages/osc/cmdln.py", line 1109, in >_dispatch_cmd > return handler(argv[0], opts, *args) > File "/usr/lib64/python2.5/site-packages/osc/commandline.py", line 292, in > do_copypac > dst_apiurl, dst_project, dst_package) > File "/usr/lib64/python2.5/site-packages/osc/core.py", line 1125, in > copy_pac > get_source_file(src_apiurl, src_project, src_package, n, > targetfilename=n) > File "/usr/lib64/python2.5/site-packages/osc/core.py", line 953, in > get_source_file > buf = f.read(BUFSIZE) > File "/usr/lib64/python2.5/socket.py", line 308, in read > data = self._sock.recv(recv_size) > File "/usr/lib64/python2.5/httplib.py", line 529, in read > s = self.fp.read(amt) > File "/usr/lib64/python2.5/httplib.py", line 1023, in read > s = self._read() > File "/usr/lib64/python2.5/httplib.py", line 999, in _read > buf = self._ssl.read(self._bufsize) >socket.error: (104, 'Connection reset by peer') Cheers, Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

14 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service May 2007