Hello everyone,
I have a question/problem with Perl packages and BuildRequires when
building for SLES(SP2).
The problem comes up with multiple packages when trying to build them
for SLES, let's look at perl-HTTP-BrowserDetect from
devel:languages:perl for example.
The spec files includes:
---
BuildRequires: perl(Module::Build) >= 0.3601
---
and the build log clearly states (see
https://build.opensuse.org/package/rawlog?arch=x86_64&package=perl-HTTP-Bro…)
that it is being installed:
---
installing perl-Module-Build-0.36.07-4.1
---
but still, the build fails with:
---
Module::Build version 0.3601 required--this is only version 0.280801 at
Build.PL line 5.
---
As far as I understand, "Module::Build" v0.280801 is already installed
by default under SLES11SP2 and the newer required version 0.3607 is not
found OR the older version is found first by the script "Build.pl".
A second example would be "perl-POE-Test-Loops" which requires a version
of Test::More/Test::Simple >=0.94, but this is not found although
installed (i.e. only an older version is found), see log here:
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=perl-…
How do I circumvent this problem?
Thanks for your help!
Hello
With the opensuse build service [obs] getting more usage every day
I wonder if this would make a diffence :-
1. Use solid state disks [ssd] to improve build times of package rpms
on, perhaps point the BuildRoot or _tmppath to the ssd's
Reason for asking.
Improve the packaging times during busy times on obs.
Cheers Glenn.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
having just updated to OBS 1.3, my API is now running under https (not a
bad idea).
I have created a PRIVATE certificate following the README.
---------------
mkdir /srv/obs/certs
openssl genrsa -out /srv/obs/certs/server.key 1024
openssl req -new -key /srv/obs/certs/server.key \
-out /srv/obs/certs/server.csr
openssl x509 -req -days 365 -in /srv/obs/certs/server.csr \
-signkey /srv/obs/certs/server.key -out /srv/obs/certs/server.crt
cat /srv/obs/certs/server.key /srv/obs/certs/server.crt \
> /srv/obs/certs/server.pem
----------------------
I see that with osc (version 0.134.1)
if the privately signed certificate is create with a Common Name (CN)
which is not the server name, osc refuses to chat with the API. That is
bit strick as :
- CN name is normally free of use
- In that mode access via IP address is not possible any more
- auto recovery system with shadow server configuration cannot be done.
That is very strange as it seems that when the certificate with an
official root, the common name is not critical.
Any clue how to overcome that issue ?
Regards
-- Dominig
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
On Fedora (15/16)
BuildRequires: portaudio-devel
gives me this:
[...]
installing portaudio-19-12.fc15
warning: .init_b_cache/portaudio.rpm: Header V3 RSA/SHA256 Signature,
key ID 069c8460: NOKEY
error: unpacking of archive failed on
file /usr/lib64/libportaudio.so.2.0.0;4f24be4b: cpio: read failed - Bad
file descriptor
error: portaudio-19-12.fc15.x86_64: install failed
[...]
Local build works.
This is the package where is happens
https://build.opensuse.org/package/show?package=FreeMat&project=home%3Arudi…
but I'll work around it so the logs may be gone.
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
ANy plans to get this working again? I'm at a loss as to how to get it going
though I had branched the project etc. Frankly, I'm figuring out the build
service, and think monoosc would go a long way to fostering a quicker
understanding.
--
Roger Luedecke
openSUSE Ambassador
Ind. Repairs and Consulting
**Looking for a C++ etc. mentor***
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Is there a way to tell the build service to include package libfoo-devel
in the build environment for a given package without making it a
buildrequires in the spec?
Or is there a BuildRecommends or
use-if-available-but-no-error-if-not-available?
--
bkw
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I added some lines to my project config to ease RHEL6/CentOS6
packaging and was told by Ismail Dönmez that it maybe useful to
integrate them at a higher level. So here they are:
%if 0%{?centos_version} >= 600 || 0%{?rhel_version} >= 600
Substitute: libxerces-c-devel xerces-c-devel
Substitute: pkg-config pkgconfig
Substitute: libexpat-devel expat-devel
%endif
One more question while I am here:
Does anyone know if the package lists for CentOS and RHEL always
differ (for instance concerning xerces-c) or whether this is a build
service peculiarity?
Regards,
Michael
Hi,
I see there were some issues with publishing recently which are fixed
according to the OBS portal. But I'm actually waiting for published
build results which have finished building almost 24 hours ago.
How can I publish them finally?
Wolfgang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org