March 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Problem accepting submitreq
by Christian 06 Mar '09

06 Mar '09

Hi, got submitreq 7572, but no mail about it. I just recognized it on web interface. tried to accept, but christian@chrisw:~/OBS/home:computersalat:KMP/broadcom-sta> osc -A https://api.opensuse.org submitreq accept 7572 Server returned an error: HTTP Error 403: Forbidden No permission to change state of request 7572 (type submit) What's wrong ? Kind regards Chris -- 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] submit-request #7151 for server:proxy/squid3
by Christian 06 Mar '09

06 Mar '09

Hi, I would be happy if someone could accept/decline. Kind Regards Chris -- 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] Thoughts on OBS as a git bisect build cluster
by Brandon Philips 06 Mar '09

06 Mar '09

Hello- I want to create a web based tool where users could do git bisections themselves by plugging in starting hashes (provided by a developer most likely) and get an RPM out. Then as they test they come back to the website to report their test results, good or bad, to get the next rpm to test. Now, the most intensive part would be doing all of the builds and checkouts. Something that I think OBS could handle nicely :D First, is this use of OBS is acceptable? If so the next challenge is avoiding lengthy and expensive uploads to the OBS. I have thought up a few strategies for doing such and would appreciate feedback: 1. Create an OBS project with a base version of the project tarball e.g. Kernel v2.6.28, then generate a patch with: $ git diff v2.6.28...<$BISECTHASH> Then branch this OBS project to create a project that will build the RPM for the user with this git diff patch applied. 2. Create an OBS project with a tar snapshot of the external git repo and submit it to an OBS project. Then create an OBS branch from this project for each git bisection step and submit some control file that tells the spec file what hash to build. 3. Have a spec file that does a clone from some internal mirror of the external git tree and does the bisect locally. (Can you get to the internet when building inside a VM?) For #1 and #2 I would need a way to submit a patch to a branched project _without_ doing a full checkout of the tarball again. How would I change one file in an OBS branch without downloading the whole repo? What do people think? Any other strategies to create something like this that uses OBS on the backend? Cheers, Brandon -- 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] "excluded" packages
by Adam Tauno Williams 06 Mar '09

06 Mar '09

I'm working on my project in obs <https://build.opensuse.org/project/show?project=server%3AOpenGroupware> and I've got all the packages building for a couple of distributions but two packages appear as excluded. These packages aren't even complicated in that they don't do anything but bundle some scripts. Is there anywhere that documents the reasons a package may be excluded? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

Re: [opensuse-buildservice] OBS: Who uses Download on Demand or Cross Build - small survey
by Martin Mohring 05 Mar '09

05 Mar '09

adrian.crutchfield(a)gmail.com wrote: > Yes > Yes > Yes > > I'm actually working to get Base:build packages built for ARM. > What challenges as of yet did you run into? We have already discussed the performance accelerator, because OBS with QEMU is quite slow (factor 4-8 slowdown ca. in average). We have already two solutions for this in the backhand. > Late > InSearchOf > -----Original Message----- > From: Martin Mohring <martin.mohring(a)opensuse.org> > > Date: Thu, 22 Jan 2009 22:44:57 > To: <opensuse-buildservice(a)opensuse.org> > Subject: [opensuse-buildservice] OBS: Who uses Download on Demand or Cross Build - small survey > > > Hi, > > a short Discussion on the IRC channel inspired me to ask this question > to all on the mailing list: > > - Who knows what Download on Demand is inside OBS > - Who uses the Cross Development Feature for ARM architecture already > now (although OBS 1.5 is not yet officially released) > - Who of you is using Pre Release Packages for OBS from > openSUSE:Tools:Devel or openSUSE:Tools:Unstable > > Feedback is very welcome to improve usability or potential Bugs. > > Kind regards, Martin Mohring > > OBS / Maintainer Development Packages - OBS Testing > > -- 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] osc 0.114
by Peter Poeml 05 Mar '09

05 Mar '09

I have updated the osc package; it's now at version 0.114. Get it from openSUSE:Tools, as usual. While updating the NEWS file, I realized how many people have been working on this, and was amazed how much has happened. I'm sure there's a lot that you'll appreciate as well: 0.114: - the .oscrc config handling has been cleaned up: * use "apiurl" for everything now (== <protocol>://<host>) * added aliases support for [apiurl] sections in the ~/.oscrc. Example: [http(s)://foobar] ... aliases = foo, bar => "osc -A foo <cmd>" will do the same as "osc -A http(s)://foobar ls" * "scheme" and "apisrv" are deprecated and will produce a warning * when writing a new ~/.oscrc, store the apiurl in the conffile (bnc#478054) * fixed bug that made osc ask for credentials when -A was used (bnc#478054) * fixed crash upon password entry (first startup) (bnc#478052) - osc build: * make product builds work * speed up by using a cookie when fetching the binaries (bnc#477690) * support for VM (kvm or xen) builds * obsolete the need to configure download server, get it from the build service instance instead. * be a bit more verbose if the linked package isn't expanded (bnc#470948) - osc branch: * --develproject option fixed (the API calls it 'ignoredevel' instead of 'nodevelproject') * --revision option added - osc jobhistory: new command to see build job history of a project or a package - osc results/rresults: option -l, --last-build added (show last build results) - osc linkpac: fix failure when -A<url> is used (bnc#479156) - osc commit: don't scare users if they want to commit a nonexistent file (bnc#469167) - osc diff: bugfix to make --pretty option work - 11.1 added to the osc project template Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] Mandriva 2009 - postgres-devel
by Johannes Weberhofer, Weberhofer GmbH 05 Mar '09

05 Mar '09

Hello, I have a problem with building packages for Mandriva 2009. When the postgresql-devel is Required for building, I get the following message: "nothing provides postgresql8.3-devel = 8.3.4-4mdv2009.0 needed by postgresql-devel" I have checked a Mandrive spec for apache-mod_auth_pgsql, and they use the package postgresql-devel there. Do you have any idea how to solve this problem? Best regards, Johannes -- |--------------------------------- | weberhofer GmbH | Johannes Weberhofer | information technologies | Austria, 1080 Wien, Blindengasse 52/3 | | Firmenbuch: 225566s, Handelsgericht Wien | UID: ATU55277701 | | phone : +43 (0)1 5454421 0 | email: office(a)weberhofer.at | fax : +43 (0)1 5454421 19 | web : http://weberhofer.at | mobile: +43 (0)699 11998315 |----------------------------------------------------------->> -- 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] --prefer-pkgs and requires and provides
by Petr Mladek 04 Mar '09

04 Mar '09

Hi, are there any plans to take the provides and requires of the preferred packages in account? I get the following error: --- cut --- $> osc build --local-package --prefer-pkgs=/tmp/prefer-rpms-5993 SLED_10 i586 OpenOffice_org-ure.spec Building OpenOffice_org-ure.spec for SLED_10/i586 Getting buildinfo from server buildinfo is broken... it says: expansion error: nothing provides OpenOffice_org-bootstrap = 3.0.99.0 --- cut --- even when the package OpenOffice_org-bootstrap-3.0.99.0 is available in the /tmp/prefer-rpms-5993. I see that this feature was mentioned at http://lists.opensuse.org/opensuse-buildservice/2007-05/msg00011.html but probably newer implemented ;-) Heh, I would be happy even for a workaround. It might help when the server mentions the valid dependencies (bdep tags) in the buildinfo together with the error. I could locally hack osc to ignore the expansion errors of OOo packages. JFYI, here is my workflow: The OpenOffice.org build is currently split into 19 spec files. I have some helper scripts that allow to rebuild everything on a local machine. I have just updated the scripts to use "osc build" instead of "abuild". It does not work because of the above mentioned problem. Note that I update the package version quite often because of API/ABI changes. The local building is important for me because I needed to get full rebuilds in a predictable time. It is especially important for factory where the normal build might be blocked several days. Also the local build trees are very useful for debugging and testing of new changes. Thanks in advance. -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic 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

3 2

[opensuse-buildservice] Packages stay too long in the state finished
by Petr Mladek 04 Mar '09

04 Mar '09

Hi, I wonder if it is a known issue that the packages stay very long time in the stay "finished" today. It slowdowns down a lot build of the dependant packages. For example, I have troubles with the packages in the project home:pmladek:ooo:test. The package OpenOffice_org-bootstrap is "finished" but not "succeeded" => the build of OpenOffice_org-ure is not started. I have seen some packages that stayed in the state "finished" several hours today. Note that many build hosts are idle, no packages are waiting in the queue, see https://build.opensuse.org/monitor. Is the scheduler overloaded or so? -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic 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

2 1

[opensuse-buildservice] osc patch
by Flavio Castelli 04 Mar '09

04 Mar '09

Hello, I wrote a small patch for osc. It simply adds a new variable inside the Linkinfo class. This variable holds the rev value specified inside the _link files. I have handled it because an osc plugin I wrote needs this field. As you can see the code is really simple. Cheers Flavio

2 1

[opensuse-buildservice] Subject of submit request mails changed
by Klaas Freitag 04 Mar '09

04 Mar '09

Hi, as requested in https://bugzilla.novell.com/show_bug.cgi?id=469168 I just changed the subjects of the submit request mails. I thought the reporter is right that for example this: [obs submit-request 7521] openSUSE:Factory:Contrib/schemik: accepted by prusnak is a more structured and useful subject. I hope you agree, Klaas BTW - there is a quite human useable admin interface for the hermes messages. I am happy to give interested people admin rights to work on the templates. Let me know if you know somebody ;-) -- 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] Re: [opensuse-svn] r6699 - in trunk/buildservice/src/clientlib/python/osc/osc: . util
by Peter Poeml 04 Mar '09

04 Mar '09

On Wed, Mar 04, 2009 at 03:15:14PM -0700, Novell Forge SVN wrote: > Author: Marcus_H > Date: 2009-03-04 15:15:11 -0700 (Wed, 04 Mar 2009) > New Revision: 6699 > > Added: > trunk/buildservice/src/clientlib/python/osc/osc/util/ > trunk/buildservice/src/clientlib/python/osc/osc/util/__init__.py > trunk/buildservice/src/clientlib/python/osc/osc/util/ar.py > Log: > - added ar module: this can be used to read ar archives. This will be > used later to extract files from a debian package which uses this > format. Currently we only support the GNU format (note: maybe > something is still missing but it's sufficient for our needs) One step further towards injection of rpm^Wdeb requires injection? Nice :-) (Marcus and I discussed offline a bit, whether this should become a Python module in its own. Maybe it still can become one later. Maybe my (comparatively stupid) cpio bits could accompany this...) > Added: trunk/buildservice/src/clientlib/python/osc/osc/util/ar.py > =================================================================== > --- trunk/buildservice/src/clientlib/python/osc/osc/util/ar.py (rev 0) > +++ trunk/buildservice/src/clientlib/python/osc/osc/util/ar.py 2009-03-04 22:15:11 UTC (rev 6699) > @@ -0,0 +1,154 @@ I see one thing missing here, or rather I don't see it: A copyright and license header. I guess one should be present, in particular because this module looks a little bit detached (in the sense of independent) from the rest of the code. > +import os > +import re > +import sys > +import StringIO > +import stat > + > +class ArError(Exception): > + """Base class for all ar related errors""" > + def __init__(self, fn, msg): > + Exception.__init__(self) > + self.file = fn > + self.msg = msg > + > + def __str__(self): > + return 'ar error: %s' % self.msg > + > +class ArHdr(): > + """Represents an ar header entry""" > + def __init__(self, fn, date, uid, gid, mode, size, fmag, off): > + self.file = fn.strip() > + self.date = date.strip() > + self.uid = uid.strip() > + self.gid = gid.strip() > + self.mode = stat.S_IMODE(int(mode, 8)) > + self.size = int(size) > + self.fmag = fmag > + # data section starts at off and ends at off + size > + self.dataoff = int(off) > + > + def __str__(self): > + return '%16s %d' % (self.file, self.size) > + > +class ArFile(StringIO.StringIO): > + """Represents a file which resides in the archive""" > + def __init__(self, fn, uid, gid, mode, buf): > + StringIO.StringIO.__init__(self, buf) > + self.name = fn > + self.uid = uid > + self.gid = gid > + self.mode = mode > + > + def saveTo(self, dir = None): > + if not dir: > + dir = os.getcwd() > + fn = os.path.join(dir, self.name) > + f = open(fn, 'wb') > + f.write(self.getvalue()) Ah, so this can actually save a part from the archive to disk? > + f.close() > + os.chmod(fn, self.mode) > + uid = self.uid > + if uid != os.geteuid() or os.geteuid() != 0: > + uid = -1 > + gid = self.gid > + if not gid in os.getgroups() or os.getegid() != 0: > + gid = -1 > + os.chown(fn, uid, gid) > + > +class Ar(): > + """ > + Represents an ar archive (only GNU format is supported). > + Readonly access. > + """ > + hdr_len = 60 > + hdr_pat = re.compile('^(.{16})(.{12})(.{6})(.{6})(.{8})(.{10})(.{2})', re.DOTALL) Interesting approach - I would have used struct.unpack for this, I guess. > + > + def __init__(self, fn): > + self.filename = fn > + self.hdrs = [] > + self.ext_fnhdr = None > + # file object: will be closed in __del__() > + self.__file = None > + > + def __del__(self): > + if self.__file: > + self.__file.close() > + > + def _appendHdr(self, hdr): > + # GNU uses an internal '//' file to store very long filenames > + if hdr.file.startswith('//'): > + self.ext_fnhdr = hdr > + else: > + self.hdrs.append(hdr) > + > + def _fixupFilenames(self): > + """ > + support the GNU approach for very long filenames: > + every filename which exceeds 16 bytes is stored in the data section of a special file ('//') > + and the filename in the header of this long file specifies the offset in the special file's > + data section. The end of such a filename is indicated with a trailing '/'. > + Another special file is the '/' which contains the symbol lookup table. > + """ > + for h in self.hdrs: > + if h.file == '/': > + continue > + # remove slashes which are appended by ar > + h.file = h.file.rstrip('/') > + if not h.file.startswith('/'): > + continue > + # handle long filename > + off = int(h.file[1:len(h.file)]) > + start = self.ext_fnhdr.dataoff + off > + self.__file.seek(start, os.SEEK_SET) > + # XXX: is it safe to read all the data in one chunk? I assume the '//' data section > + # won't be too large > + data = self.__file.read(self.ext_fnhdr.size) > + end = data.find('/') > + if end != -1: > + h.file = data[0:end] > + else: > + raise ArError('//', 'invalid data section - trailing slash (off: %d)' % start) > + > + > + def read(self): > + """reads in the archive. It tries to use mmap due to performance reasons (in case of large files)""" > + if not self.__file: > + import mmap > + self.__file = open(self.filename, 'rb') > + try: > + self.__file = mmap.mmap(self.__file.fileno(), 0, prot=mmap.PROT_READ) > + except EnvironmentError, e: > + if e.errno == 19: > + print >>sys.stderr, 'cannot use mmap to read the file, falling back to the default io' Wise... we had this before... > + else: > + raise e > + else: > + self.__file.seek(0, os.SEEK_SET) > + data = self.__file.read(7) > + if data != '!<arch>': > + raise ArError(self.filename, 'no ar archive') > + pos = 8 > + while (len(data) != 0): > + self.__file.seek(pos, os.SEEK_SET) > + data = self.__file.read(self.hdr_len) > + if not data: > + break > + pos += self.hdr_len > + m = self.hdr_pat.search(data) > + if not m: > + raise ArError(self.filename, 'unexpected hdr entry') > + args = m.groups() + (pos, ) > + hdr = ArHdr(*args) > + self._appendHdr(hdr) > + # data blocks are 2 bytes aligned - if they end on an odd > + # offset ARFMAG[0] will be used for padding (according to the current binutils code) > + pos += hdr.size + (hdr.size & 1) > + self._fixupFilenames() > + > + def get_file(self, fn): > + for h in self.hdrs: > + if h.file == fn: > + self.__file.seek(h.dataoff, os.SEEK_SET) > + return ArFile(h.file, h.uid, h.gid, h.mode, > + self.__file.read(h.size)) > + return None Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] Old cmake version is used
by Matthias Fehring 04 Mar '09

04 Mar '09

Hello list, I have a sub project in my build service home project, where I build packages for KDE4. https://build.opensuse.org/project/show?project=home:buschmann23:KDE4 I have a repository layout there like in KDE:KDE4:Community. The repositories use my main home project and KDE:KDE4:*:Desktop as base repos. My problem is now, that for the openSUSE_11.0_KDE4_Factory_Desktop repository every time the cmake version from openSUSE:11.0 ist used, and not that from devel:tools:building project, which is a base repo for KDE:KDE4:Factory:Desktop/openSUSE_11.0. Why does this happen? Best greetings Buschmann ---------------------------------------------------------------------------------- openSUSE Member - de.opensuse.org Sys-Op http://en.opensuse.org/User:Buschmann23

1 0

[opensuse-buildservice] osc and security
by Joop Boonen 03 Mar '09

03 Mar '09

I've checked out ~/.oscrc I saw that my password can be found in plain text. As someone who would be able to read this file would be able to change packages that I have created. I'm rather worried about it. The package could easily be piggy backed with mall ware. I'm wondering wouldn't it be possible to put an encrypted password? Or even better to work with ssh keys? An other option would be that the password wouldn't be saved. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 9

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 03 Mar '09

03 Mar '09

present: abauer, mls, froh, adrian, poeml sent in status: Martin Mohring, Markus Hüwe absent: freitag * Status round * PDB migration status Status round ============ mls: * fixing build number syncing in 1.5 branch * working on backend support part for repairing broken source links abauer: * Updated openSUSE hermes and fixed RSS feed support. * Created proposal for attribute support in OBS as part of PDB migration. poeml: * Worked on new zypper support for factory. * New OBS Mirror in US. * download redirector redirects to fedora server for package download of Fedora project. * Mirror database speed improvements. adrian: * repaired broken signing host. * started to collect features for this year in FATE. Hüwe: - tracked down backend bug fixed in -r 6613 - fixed osc bug #477690: build: use a cookie when fetching the binaries fixed in -r 6614 - work on "inject rpm data for buildinfo calculation" feature Mohring: - debugged/fixed obs svn trunk bug fixed in -r 6613 (another famous 1 liner) - working on bringing maemo.org SDK 4.1 and later 5.0 prereleases (with support from Jan-Simon Möller) to work in "test OBS" - brought "test OBS" back to work (moved servers + tracking down svn trunk breakage) - packaged and tested openSUSE:Tools:Devel/obs-all-svn @ up to svn trunk -r 6614 - packaged and tested openSUSE:Tools:Devel/qemu-svn @ svn trunk -r 6654 PDB Migration ============= * Andreas created proposal for attribute system, we will discuss it later this week. * Other requirements like package drop requests have been added to Fate. -- 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

[opensuse-buildservice] HowTo find or create a RHEL 3 build-config-file
by Matthias Kerk 02 Mar '09

02 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, For my old systems I need some RHEL 3-Packages. Those packages I'd like to build with my local-OBS. Unfortunately, there is no Configfile in /usr/lib/obs/server/build/configs for RedHat. I wonder if there are any existing configfiles for RHEL 3 available? What do I have to keep in mind when manually creating such configfiles? Are there any differences between the build process and the making of configfiles for !SuSE and for RHEL? Best regards and thanks in advance, Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmrxGcACgkQTG9/zWWjsBvdmACdHUmIeKXjIududI0ZzMlezeIh Q80AmwULgOm+s9uT7eDdHVpN8qM+fhDd =Aw8E -----END PGP SIGNATURE----- -- 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] project "server:ltsp" deleted by mistake
by Jigish Gohil 02 Mar '09

02 Mar '09

Hi One of the maintainer of server:ltsp project has deleted it by mistake, can it be restored? If not please re-create it, we will upload the packages again. Thanks -J -- 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] broken signing in the last 24h hours
by Adrian Schröter 01 Mar '09

01 Mar '09

JFYI, our sign host broke down (harddisc error, blocking raid IO) somewhen on saturday. It is repaired now, but the OBS package building was very slow for a while and it published also some unsigned packages and repos. However, everything is fixed again, all current running builds should get signed again. bye adrian -- 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

[opensuse-buildservice] %kde4_runtime_requires failed
by Sascha 'saigkill' Manns 01 Mar '09

01 Mar '09

Hello Mates, actually the using of %kde4_runtime_requires failed: File must begin with "/": Requires: File must begin with "/": kdebase4-runtime File must begin with "/": >= File must begin with "/": 4.2.0 File must begin with "/": kdebase4-runtime File must begin with "/": < File must begin with "/": 4.2.60 Has anyone an idea what the error is? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1