- openSUSE Build Service

[opensuse-buildservice] 'assert’ was not declared in this scope
by Richard Bos 12 May '07

12 May '07

Does soneone know, what can be done to prevent or solve the error below: xml.cpp: In member function ‘int xml::push_parser_context::parse(char*, int)’: xml.cpp:283: error: ‘assert’ was not declared in this scope make[2]: *** [xml.o] Fout 1 The file to be compiled xml.cpp: ......... extern "C" { #include <libxml/parser.h> #include <libxml/tree.h> #include <libxml/relaxng.h> } namespace xml { ..................... 280 if (context_ == 0) 281 { 282 context_ = xmlCreatePushParserCtxt(handler_, data_, buffer, size, file name_); 283 assert(context_ != 0); 284 return 0; 285 } 286 else 287 return xmlParseChunk(context_, buffer, size, size == 0); 288 } Commenting out 'assert' results in a succesful compile. -- TIA, Richard Bos We are borrowing the world of our children, It is not inherited from our parents. --------------------------------------------------------------------- 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] Quick question on signing and importing RPMs
by linuxnoob＠wi.rr.com 11 May '07

11 May '07

Hey, all. Two quick newbie questions. I've read all the documentation I can find, from the wiki pages to the api.opensuse.org docs, and I'm still unsure how to do the following tasks via the build service's web interface: 1. How do I take the GPG key I've created and sign packages with it? I can't tell where it should even be uploaded, much less how I should go about signing said packages via the web interface. 2. How do I take a package from another project and have the build service install it before building my package? I'm thinking specifically of Riggwelter's "giblib" package, which apparently isn't available from the standard repos. I've linked it into to my home project, but even though I have "giblib" and "giblib-devel" in the BuildRequires of my spec, it can't find the rpms to install. Thanks in advance. :) ~~ Andrew D. (andrewd18) --------------------------------------------------------------------- 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] how to edit Substitute / Prefer / Ignore?
by Stanislav Brabec 11 May '07

11 May '07

Hallo. Latest Factory changes require a lot of ugly hacks in nearly all packages in GNOME:STABLE. I guess, that it could be fixed in the Build Service repository configuration in Substitute / Prefer / Ignore tags. But I don't see any way how to edit them without direct access to the BS machines. To be changed: prefer pkg-config over pkgconfig for > 1020 and GNOME:UNSTABLE (soon in GNOME:STABLE, too) libexpat-devel -> replace by expat for <= 1020 dbus-1-glib-devel -> replace by dbus-1-devel dbus-1-glib for < 1020 texlive-devel and texlive -> replace by tetex for <= 1020 python-gtk-devel -> replace by python-gtk for < 1020 libqt4-devel -> replace by qt-devel for < 1020 libbz2-devel -> replace by bzip2 for <= 1020 And maybe also several bug-fixes (missing dependencies in older versions): NetworkManager-glib -> add also NetworkManager-gnome for < 1020 There were more fixes, but these should cover most %if %suse_version in the GNOME:UNSTABLE. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 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 5

[opensuse-buildservice] Buildservice and multiple repositories
by Dirk Stoecker 11 May '07

11 May '07

Hi, I already wrote a mail about this topic, but as I read the same in a heise forum yesterday I try again. The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation. My suggestions would be to add a typo of meta repository, where the packes are only stored, but cannot be built. - You have a meta repository, which has no built feature - Packages are either imported into it or exported from the original repositories. - Conflicts are not resolved, but only marked in the original and the meta package. - Adding packages should be easy. Reason: Some all-in-one packages without the PacMan problems. 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

4 5

[opensuse-buildservice] preferred rpms and ccache
by Michael Wolf 09 May '07

09 May '07

Yo In home:maw, I have two packages which may be of interest to other people using the build service. First is a patched version of osc. It has two patches. One patch, pubkey-instructions.patch, is pretty straightforward, and I think it should be committed to svn. Another patch, preferred-rpms.patch, lets you run osc with the environment variable OSC_PREFERRED_RPMS set. This allows you to run builds with your own packages - it's useful when you update foo, and then get to work on bar, upon which foo depends. Sure, foo will be rebuilt automatically by the build service, but sometimes it takes a while; this way you can keep on working. As is, it's pretty hacky and kind of dumb (osc will download the packages needed to build your package even if that package already exists in your preferred rpms directory), but it might be useful to other people anyway. It's been very useful for me, at any rate. (Is there already a better way to do this? I couldn't find it...) Second is a patched version of ccache. This links /usr/local/bin/{gcc,cc,g++,c++} to /usr/bin/ccache. The result is that ccache is transparently invoked when building, no need modify your .spec or anything like that. Also, the default cache size is raised to 3G and ccache's directory goes into /.ccache. To use, you currently need my patched osc; put the ccache package into your preferred rpms directory and build away. At the risk of stating the obvious, I don't advise installing this package outside of osc build roots. Together, these make building large packages (such as firefox) and groups of many packages with lots of interdependencies (such as gnome) much faster. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Accessing a buildservice backend directly with osc
by Dr. Peter Poeml 07 May '07

07 May '07

Hi, today I tried accessing the buildservice backend directly with osc. It *should* be possible now, since the requests are mostly (all?) passed through unaltered to the backend. It seemed to work well. This means that, for a local buildservice instance, one could get by without the api/frontend, if the permission and user handling is not needed. Might be handy for a simplified single-user setup. (It won't work for the openSUSE buildservice, because the backend is not publicly exposed.) Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development

1 1

[opensuse-buildservice] Disappearing Buildrequires on zlib-devel
by Dr. Peter Poeml 07 May '07

07 May '07

Hi, I have a Buildrequires on zlib-devel: Name: stunnel BuildRequires: openssl openssl-devel zlib-devel %if 0%{?suse_version:1} BuildRequires: tcpd-devel %else BuildRequires: gcc-c++ tcp_wrappers %endif The buildinfo does swallow the "zlib-devel" somehow: % osc buildinfo SUSE_Linux_Factory x86_64 | grep zlib <dep>zlib</dep> <bdep name="zlib" preinstall="1" version="1.2.3" release="48" arch="x86_64" project="SUSE:Factory" repository="standard" /> <pdep>zlib</pdep> This looks like a bug to me. The buildconfig has no suspicious replacements or stuff: % osc buildconfig SUSE_Linux_Factory x86_64 | grep zlib Preinstall: permissions popt pwdutils readline rpm sed tar zlib Required: gettext glibc libtool ncurses perl rpm zlib Ignore: mediawiki:php-session,php-gettext,php-zlib,php-mysql,mod_php_any Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development

2 2

[opensuse-buildservice] Build Requires a package being built
by Andrew Wafaa 04 May '07

04 May '07

Not sure if the subject makes sense to anyone other than my self, but I'll try and explain... I'm trying to build Midgard which has several packages that make up the whole application, nothing unusual with that. The problem I have is that instead of having three or four seperate SRPMs etc I was hoping to create just the one and use the same spec file. I am failing at the first hurdle as some of the packages require midgard-core-devel which is to be built as part of the suite. Is there a way that I can ask the obs to do this? Thanks and regards, Andy -- Andrew Wafaa Tel: +44 (0)7974 074546 e-Mail: andrew(a)forcev.net --------------------------------------------------------------------- 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] Improvement suggestion
by Dirk Stoecker 04 May '07

04 May '07

Hi, the build log has lots of lines like "installing readline-5.0-7.2" Could that be changed, so that a text is added, where the package comes from? Mainly interesting for me is the fact whether it is from the current project, from the base system, ... Thought maybe other are interested in the fact which directory the file comes from. 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 1

[opensuse-buildservice] perl-Net-DNS
by Dirk Stoecker 03 May '07

03 May '07

Hello, now I have another problem at: http://build.opensuse.org/package/live_build_log?package=perl-Net-DNS&repos… This is the openSUSE:Factory module built for SUSE 9.3 (and perl 5.8.8). It fails in test stage with: t/01-resolver-opt..........ok t/01-resolver..............Can't call method "sockaddr" on an undefined value at t/01-resolver.t line 83. # Looks like you planned 44 tests but only ran 42. # Looks like your test died just after 42. dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 43-44 Can anyone help me (probably knowing the reason), or do I need did deep into the test and build system to find out, what's wrong? 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