Hi,
I wrote a little script to check for problems with devel package definition
and found only one, then I also checked for the old devel project and found
TONS of problems, so I created a wiki page not to spam the mailing list.
I also found two cases where you could save a package with broken devel
package definition - those are fixed now. So I hope once we have the current
list of problems fixed, we're safe :)
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Well I decided to include the mandriva %mklibname macro directly into
the specfile but this errors too, though I do not know how.
Interestingly 2009.1 and 2010.0 give a slightly different error for
x86_64 too which is odd:
the macro is:
%mklibname(ds) %{_lib}%{1}%{?2:%{2}}%{?3:_%{3}}%{-s:-static}%{-d:-devel}
The errors for 2009.1 and 2010.0 respectively are (note lib64 in 2010
and lib in 2009.1):
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define
'jobs 4' --define 'disturl
obs://build.opensuse.org/home:aapgorilla/Mandriva_2009.1/dec1a08a2bf0050485…'
/home/abuild/rpmbuild/SOURCES/qt4.spec
error: line 1: Unknown tag: lib%{1}(ds) lib%{1}
mount: / is busy
System halted.
+ exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define
'jobs 4' --define 'disturl
obs://build.opensuse.org/home:aapgorilla/Mandriva_2010/dec1a08a2bf005048576…'
/home/abuild/rpmbuild/SOURCES/qt4.spec
error: line 1: Unknown tag: lib64%{1}(ds) lib64%{1}
mount: / is busy
System halted.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi, all the servers seem idle and my packages won't start building, is
something wrong?
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi, all
I'm find another questions on obs about cycly building.
Describe my step once again:
1. create a new project GTES:11:U6,
which is a subproject of GTES:11
2. use a script (see attachment: osc_add_srpm)
to upload more than 1000 package into GTES:11:U6
3. add a standard Repository for GTES:11:U6
Then, the auto build beginning ...
Last, I've found that build for many pkgs,
'BuildRequires' another pkgs, and that pkgs
haven't be build yet. But that pkgs could
be found in standard Repository!
For example, the 'bc' package. I've found it's
status is 'blocked',and clcked the blocked link
on webclient, could be see following info:
--------------------------------
autoconf,automake,binutils,bzip2,db4,device-mapper,
flex,gcc,libgomp,libtermcp-devel
===============================
I'm thought that it means haven't those rpms in
current project's repository. But I'm sure those
rpms exist in 'standard' Repository of current project!
How obs to find those rpms it need when build some pkgs ?
Many docs of obs have said that it would be found in current
project's repository itself,then found it in 'standard'
Repository (which add for current project for a base build
repository) if haven't found in repository itself.
Another question, in my project, own more than 1000 pkgs be
build and start at same time. Any status of project is
uncertainty ! For example, the 'succeeded' status was one number,
and switch to another number next times , the most confusion is
the number wasn't increased allow one order. The other status
is the same, 'failed', 'expansion', 'error', 'broken', 'blocked',...
I known it was because of the cycle building. but It could not
uncertainty endless :-)
Thanks,
----
Jian Lee [ http://jianlee.ylinux.org ]
hi,
it seems we get an outage of the opensuse buildservice as christmas
present. we will try to fix it as soon as possible.
Stay tuned for more and sorry for the inconvenience.
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
Would it be possible to get a more recent version of Java on OBS?
The latest OpenJDK (1.7.0-ea-b77) is the only JRE which both doesn't
crash with Eclipse, and doesn't crash when compiling. (for me; I'm
keeping my fingers crossed though, I'll probably run into another bug
sooner than later).
If no one wants this mainstream, can someone tell me how I might
put binary RPM's (the openjdk site provides i586 and x86) on OBS? It
seems building java from source is kinda tricky.
Thanks much,
Nicholas — ntung at ntung — https://ntung.com
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
hi,
Too many srpms in my project have a old description about
BuildRequires in the spec file like that:
--------------------
BuildPrereq: /usr/bin/perl
==========================
but the /usr/lib/build/Build.pm have nothing to support this
description.
The /usr/lib/build/expanddeps just get the
BuildRequires,Requires,Provides of every pkgs. and the pkg which would
be build could not get a BuildRequires like "/usr/bin/perl" from those
infomation.
If to do this, must add a infomation of "rpm -ql XXX.rpm" to depends
file.
-------------------
F:... XXX.rpm
P:... `rpm -ql XXX.rpm`
R:...
I:...
===================
Is there a better idea ?
Thanks,
----
Jian Lee [ http://jianlee.ylinux.org ]
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
in some baselibs.conf, one can for example find:
tcpd
arch ppc package tcpd-devel
This causes tcpd-devel.ppc to be made available as
tcpd-devel-32bit.ppc64. The question would be, why would one want to
limit tcpd-devel to ppc?
thanks,
Jan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I sent this email two hours ago, retrying.
Hi, is the build service down? I've tried to connect for the last two
hours both from the web interface and osc. Osc gives HTTP Error 400: Bad
Request and the web interface gives a 504 gateway timeout.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org