October 2013 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Need information about failing _constraint
by Dirk Müller 07 Oct '13

07 Oct '13

Hi, is there any way to figure out why a constraint is non-fulfillable? for this one: https://build.opensuse.org/package/show/openSUSE:13.1/llvm it seems the constraint is never fulfilled for the qemu workers (aarch64, armv6l), while it works fine for native workers (armv7l). Strangely enough, a similar constraint in glibc-testsuite (that also checks for hypervisor==kvm) seems to work fine. Any idea why it is not fulfilled? There are certainly workers available (idle even) that would fulfill the constraint. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] macros (e.g. %{buildroot} are expanded to NULL ("")...
by David Haller 05 Oct '13

05 Oct '13

Hello, basically, the subject says it all... E.g. %config(noreplace) %{_sysconfdir}/%{name}/vche.conf results in [ 50s] error: Installed (but unpackaged) file(s) found: [ 50s] /vche/vche.conf [ 50s] RPM build errors: [ 50s] File not found: /home/abuild/rpmbuild/BUILDROOT/vche-1.7.2-210.1.i386/etc/vche/vche.conf [ 50s] Installed (but unpackaged) file(s) found: [ 50s] /vche/vche.conf There's several other weird errors along that line (%buildroot not being expanded in %install, and whatnot ..) -dnh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Programa de desarrollo de competencias gerenciales
by Universidad Matias Delgado 04 Oct '13

04 Oct '13

PROGRAMA DE DESARROLLO DE COMPETENCIAS GERENCIALES 2013 ¿Quieres ser un mejor Jefe en tus areas de trabajo? Informate sobre nuestros Programa de desarrollo de competencias Gerenciales. puedes escribirnos a:maestriasmatias@ujmd.edu.sv ¡Porque somos #1 en formacion profesional!

1 0

[opensuse-buildservice] Question about the new comment feature
by Greg Freemyer 03 Oct '13

03 Oct '13

In a devel project I maintain I got a SR that I wasn't sure about. I added a comment to it with my question. Does that comment automatically get emailed to the originator of the SR? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] tomcat7 update missing on the mirrors
by Darin Perusich 02 Oct '13

02 Oct '13

I've just ran across this and I'm not really sure what's going on or how to proceed. An update for tomcat 7 on OpenSUSE 12.3 was release back on 7 August 2013 which brought it up to version tomcat-7.0.35-2.9.1. Earlier I went to install the tomcat-admin-webapps package and it failed because due to a version requirement, version 7.0.35-2.2.1 is what it was trying to install. I do run a local mirror and thought maybe it was out of sync but then I checked http://download.opensuse.org/update/12.3 there are no tomcat update packages available. Something tells me packages should just disappear like this. Should I file a bug for this, is this a maintenance or OBS issue? I have about a dozen+ tomcat servers which could be effected by this so I'd like to get to the bottom of it asap. http://lists.opensuse.org/opensuse-updates/2013-08/msg00013.html -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] OBS build against Fedora Updates?
by Tim Serong 02 Oct '13

02 Oct '13

Hi All, I hit a problem late last week doing a Hawk build in network:ha-clustering:Stable against Fedora 19, namely that OBS builds against Fedora 19 GA, but if I install Hawk on a Fedora 19 test VM with all updates applied, Hawk doesn't run because it was built against libcib.so.2, whereas Pacemaker in Fedora updates supplies libcib.so.3. I hacked around this in Hawk by having it try to dlopen() both of libcib.so.2 and libcib.so.3, as I'm only calling a couple of functions and their signatures apparently didn't change, but it's a bit nasty. Then, the other day, I was trying to get sbd builds in network:ha-clustering:Stable (as cluster-glue requires sbd, and we want to be able to provide builds of all this stuff for Fedora as well as openSUSE, largely to facilitate uptake of crmsh and hawk), and I hit the same problem again. Building sbd against Fedora GA links to libcrmcluster.so.2 and libcib.so.2, but Fedora Updates has libcrmcluster.so.4 and libcib.so.3. Someone already opened a bug requesting OBS build against Fedora Updates (although that was Fedora 18, it was a while ago): https://bugzilla.novell.com/show_bug.cgi?id=804202 Can anyone suggest a solution to this? Is it possible to get OBS to build against Fedora Updates somehow? Because without this ability I'm having a hard time seeing using OBS for viable Fedora builds of HA clustering packages, unless we build the whole stack ourselves, which I'd rather not do (yet more maintenance work for no real benefit, given a viable Pacemaker and Corosync already ship in the base Fedora distro). Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] I suspect that my chromium package build is going wrong
by James Bond 01 Oct '13

01 Oct '13

This is the package I'm trying to build https://build.opensuse.org/package/show/home:evantonsuse/chromium Build process worked for almost 10 hours, the last message I saw in the build log was the one related to the linking of the chromium binary I think (that's when I've got out of memory error when trying to build locally, so that's the reason why I've tried to build using the build service). After that the timestamps in the build log suddenly started over and judging by the content of the log, the build process started from the beginning again. I've got no package. The build is shown as still going. Could somebody have a look and tell me what's going on, please? Thanks. PS: I am trying to rebuild chromium because of a few reasons: - the official 32bit chromedriver binary for linux doesn't work on debian wheezy because it's compiled against a newer version of glibc - there's a chromium debian package, but there's no package for chromedriver - source code of chromedriver is part of chromium source code tree At this moment it looks like the build process is running for the third time already. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

Fwd: [opensuse-buildservice] I suspect that my chromium package build is going wrong
by James Bond 01 Oct '13

01 Oct '13

---------- Forwarded message ---------- From: James Bond <evanton(a)tut.by> Date: 2013/10/1 Subject: Re: [opensuse-buildservice] I suspect that my chromium package build is going wrong To: Raymond Wooninck <tittiatcoke(a)gmail.com> >Currently network:chromium builds indeed the chromium package for openSUSE distro's, but it doesn't any SUSE specific patches, etc to the source tarball. I see chromium 31 there, chromium in debian repository is an older version. chromedriver is tricky since it has requirements about the version of chromium. A version (or a few versions) mismatch between chromedriver and chromium can lead to chromedriver not working at all with that version of chromium. I know this for a fact since I've bumped into this problem while trying to get them to work in another linux distribution. That's why I have thought it is a good idea to attempt building chromedriver from the same version of source code that was used to build the chromium package for the debian repository. >If I understood you correctly, then the only thing you want is to build the chromedriver? Correct. As stated above, there's no chromedriver package in the debian repository (and I don't know why, it would be so much easier if chromedriver would be just one apt-get install command away!). >If that is correct, then why do you build the full chromium build? I have looked for hints here: http://packages.ubuntu.com/raring/chromium-chromedriver . This is the chromedriver package for ubuntu, yet chrome is specified as build target in rules file. I am just trying to guide myself using reasons that look like common sense to me, I have zero prior experience building debian packages. To me, just adding chromedriver as additional target looked like the minimum change I have to make manually to the build scripts. 2013/10/1 Raymond Wooninck <tittiatcoke(a)gmail.com>: > On Tuesday 01 October 2013 15:16:51 James Bond wrote: >> correct me if I'm making a wrong assumption) that openSUSE:Factory is >> a project that builds packages for OpenSUSE and network:chromium is a >> project for building Linux binaries that are distribution agnostic. My > > Currently network:chromium builds indeed the chromium package for openSUSE > distro's, but it doesn't any SUSE specific patches, etc to the source tarball. > >> project is making use of the vanilla source code chromium tarball + >> Debian patches and is trying to build a package for the 32bit Debian >> Wheezy - same version of chromium as the one in the repository, the >> only difference between it and the chromium package from the Debian >> repository being that I'm trying to also compile chromedriver and >> bundle it into the package. > > If I understood you correctly, then the only thing you want is to build the > chromedriver ? If that is correct, then why do you build the full chromium > build ? Building chromium will not give you the chromedriver as that this need > to be explicitly indicated and build separately. The outcome of the > chromedriver build is a single executable which could be packaged separately > (same as happens on openSUSE). You can then decide whether or not to install > that particular package. > > Regards > > Raymond > -- > To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1