August 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Subscription
by Ciro Iriarte 14 Aug '07

14 Aug '07

Anyone knows if the BuildService subscription circuit still works?, i asked for an account weeks ago and i'm still getting "Errorcode: unconfirmed_user". Ciro --------------------------------------------------------------------- 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] Projects with subdirectories
by Joe Croft 14 Aug '07

14 Aug '07

Hi, I'm a newb to the build service and am trying to add a project with subdirectories. The files in the main directory of the project added without problems (none that I didn't work through) but when I try to add files from the subdirectory (QcjData) I get the error: error: "QcjData" is not an osc working copy How do I add subdirectories to my project? -joe --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 10

[opensuse-buildservice] Support for --changelog removed from osc build
by Andrew Beekhof 14 Aug '07

14 Aug '07

Hi, I just noticed that support for --changelog was removed from "osc build" This breaks local debian builds for people using {package}.changes (since there will be no entry describing the release). Can it please be added back? andrew --------------------------------------------------------------------- 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] spec files
by Razi Khaja 14 Aug '07

14 Aug '07

Can anyone point to any good resources for writing spec files? Thanks Razi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 6

[opensuse-buildservice] Re: openSUSE build service - mldonkey removal
by Dirk Stoecker 14 Aug '07

14 Aug '07

On Tue, 14 Aug 2007, Adrian Schroeter wrote: > I had to remove mldonkey in your projects for legal reasons. Please do not > submit it again. > > We maintain a list of software, which can't get maintained in the openSUSE > build service at: > > http://en.opensuse.org/Application_Black_List > > Please check or ask back if you are unsure. What is illegal with mldonkey? It is a normal P2P software, has no cracking possibilities and does not violate patents. I don't see a valid reason to remove it (or I would not have added it at all). It is the second time that a decision from above destroys lots of work done (the first was removal of SuSE9.3 from one day to the other) and I don't find this very nice. The minimum I expect in such cases is a) Explaining the reason. "This is illegal" is no reason. What is illegal? b) A discussion before explaining your point of view and giving the chance to find contra to it. c) A time to react to any deletions before they occur including fixing the offending packages if possible or backup the data before deleting. IT IS VERY DISCOURAGING TO INVEST LOTS OF WORK INTO SOMETHING AND THEN SEE THIS WORK VANISH WITHOUT VALID REASON. For the bugtracker of openSUSE there is a quality assurance helping to fix such issues. Implement the same for BuildService. It is nice to have such a service, but if it is not reliable I have other things to do. 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

1 0

[opensuse-buildservice] "Illegal" software, which can be hosted at *.opensuse.org
by Adrian Schröter 14 Aug '07

14 Aug '07

Hello, sorry for the cross-post, discussion on opensuse-project only please. I had to remove a number of software packages in the last days from the openSUSE Build Service for legal reasons. I do maintain also a list of this software, which is known (to our legal folk) to be illegal at this place: http://en.opensuse.org/Application_Black_List sorry for this, but please to not slap the messenger ... adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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] Please delete Project home:dstoecker:perl
by Dirk Stoecker 13 Aug '07

13 Aug '07

Hello, please delete project home:dstoecker:perl. 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

2 5

[opensuse-buildservice] Automatical substitutions
by Dirk Stoecker 13 Aug '07

13 Aug '07

Hello, For Suse 10.1 my requirement camlp4 is automatically replaced by ocaml. How can I prevent this (as I rebuild ocaml in the same project and thus really require camlp4)? 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

5 9

[opensuse-buildservice] RFC: osc support for SLES9 / Python 2.3
by Dr. Peter Poeml 13 Aug '07

13 Aug '07

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

1 1

[opensuse-buildservice] Problem with patching spec file: gconf2-rpm-macros and %gconf_schemas_prereq
by Michel Salim 10 Aug '07

10 Aug '07

Hello, I'm trying to rebuild pidgin for openSUSE 10.2, and noted that it uses %gconf_schemas_prereq, which is not available in stock 10.2 (it is in GNOME:unstable and openSUSE 10.3/Factory). I imported gconf2-rpm-macros from GNOME:Community, and then uploaded the following patch file for pidgin, marking it as a patch to the spec. However, building still fails when parsing the spec file, when %gconf_schemas_prereq is encountered. Moreover, gconf2-rpm-macros is never installed by the build server! Which was the problem: the version detection, or the way I created the patch? Also, what does the following do: || 0%{?opensuse_bs} Presumably %suse_version does not work on build service, and the opensuse_bs is a work-around? Won't it cause problem (for pidgin anyway) if I were to build it for, say, 10.3, if it tries to BuildReq: on gconf2-rpm-macros just because the package is built on the build server? --- pidgin.spec.old 2007-08-06 10:08:01.000000000 +0700 +++ pidgin.spec 2007-08-09 00:09:23.000000000 +0700 @@ -52,6 +52,9 @@ %if %suse_version >= 1021 || 0%{?opensuse_bs} BuildRequires: avahi-compat-howl-devel silc-toolkit-devel %endif +%if %suse_version <= 1020 +BuildRequires: gconf2-rpm-macros +%endif BuildRoot: %{_tmppath}/%{name}-%{version}-build %gconf_schemas_prereq Thanks, -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6