Hi, all! (Again)
In my search to get an OBS instance which can compile for sh4
architecture I found ST Linux, a _metadistro_ based on Fedora/Red Hat
which offers a cross compiler for sh4 and a basic environment for it.
So I search if ST Linux is supported by OBS, and I found this wiki
article: http://en.opensuse.org/openSUSE:Build_Service_Testing
In that article, ST Linux appears as supported and, I supposed,
tested, but I can't find another reference, so I come here to ask you
if someone knows anything about ST Linux into OBS.
Thanks, again!
--
Francisco Javier Cuadrado
SPAIN-CHINA-HONG KONG-POLAND
Spain Main: +34-910005436
Centro Empresarial Eisenhower
C/ Cañada Real de Merinas, 25
Edificio 7 - oficina 1ºC
28042 Madrid
http://www.iunika.com
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all
Can anyone spot the reason I'm having this error?
osc build RedHat_RHEL-5 enzo.spec --no-verify -p RedHat_RHEL-5-x86_64/
Building enzo.spec for RedHat_RHEL-5/x86_64
Scanning the following dirs for local packages: RedHat_RHEL-5-x86_64/
Getting buildinfo from server and store to
/mnt/home:pathscale/enzo/.osc/_buildinfo-RedHat_RHEL-5-x86_64.xml
Getting buildconfig from server and store to
/mnt/home:pathscale/enzo/.osc/_buildconfig-RedHat_RHEL-5-x86_64
buildinfo is broken... it says:
unresolvable: nothing provides glibc-devel-32bit, nothing provides
glibc-32bit
----
osc ls -b RedHat:RHEL-5 -r standard | grep glibc
compat-glibc-2.3.4-2.26.i386.rpm
compat-glibc-headers-2.3.4-2.26.i386.rpm
glibc-2.5-49.i686.rpm
glibc-common-2.5-49.i386.rpm
glibc-devel-2.5-49.i386.rpm
glibc-headers-2.5-49.i386.rpm
glibc-utils-2.5-49.i386.rpm
compat-glibc-2.3.4-2.26.x86_64.rpm
compat-glibc-headers-2.3.4-2.26.x86_64.rpm
glibc-2.5-49.x86_64.rpm
glibc-common-2.5-49.x86_64.rpm
glibc-devel-2.5-49.x86_64.rpm
glibc-headers-2.5-49.x86_64.rpm
glibc-utils-2.5-49.x86_64.rpm
----
ls RedHat_RHEL-5-x86_64/*.rpm
RedHat_RHEL-5-x86_64/enzo-3.9.99-0.x86_64.rpm
enzo has a two stage build process for various reasons so I need to
locally build a package and then the 2nd time around specify the -p dir/
option.. The 2nd pass is when I'm having problems and not sure why I'm
getting this error. I hope someone knows why and if possible can
provide a fix or work-around.
Thanks
./C
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
admin@lape:~/OBS/home:computersalat:branches:network/atftp> osc sr -m
"some bugfixes" -s 50222
There are already following submit request: 50222.
Supersede the old requests? (y/n/c) y
Server returned an error: HTTP Error 403: Forbidden
set state to superseded from accepted, superseded or declined is not
allowed.
I could supersede my Request (now 50528), but why do I get an error ?
--
Christian
---------------------------------------------------
Der ultimative shop für Sportbekleidung und Zubehör
http://www.sc24.de
---------------------------------------------------
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I'm working on a little project on the suse build service:
home:cavallo71:opt-python-interpreters
opt-python-svn85227
This is a special /opt based python version pulled from the
svn repository: it is based on python 2.7.x (so it carries its own
libpython2.7.so.1.0).
On a OpenSuSE factory the virtual machine build process pulls the initial
dependency list including libpython2.7.so.1.0: this is available both from
the (I suppose) base distro and from mine /opt based repository (there are
multiple opt-python-svnXXXXX one for each subversion checkout).
This will return the following error message:
"have choice for libpython2.7.so.1.0 needed by python-base: opt-python-svn84368
opt-python opt-python-svn84091 opt-python- svn83620 opt-python-svn83132
opt-python-svn84276 libpython2_7-1_0"
The build fails since few days ago, so I suppose something has changed
in the repos resolution order recently.
Thanks,
Antonio Cavallo
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello!
I'm currently trying to build new mediawiki packages which are FHS compliant. I've nearly finished it, but I have one tiny problem:
Included in the sources there is one small tool which must be compiled and is therefore architecture depended. Therefore the main package should go into a noarch RPM, a small sub-package into an architecture specific RPM.
It seems, build support something like this since OSS 11.3, but only the other way round: The sub-package can be noarch (which makes sense for docs I think). Putting the following into the spec:
Name: mediawiki
...
%if %{?suse_version} >= 1130
BuildArch: noarch
%endif
...
%package texvc
%if %{?suse_version} >= 1130
BuildArch: %{arch}
%endif
...
leads into
error: line 62: Only noarch subpackages are supported: BuildArch: %{arch}
Do you see a way how to handle this problem nicely except splitting up the package into two packages, one for the scripts, one for the binary?
Thank you and best regards,
Johannes
--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Unfortunately I see the same error...
Thank you for your response,
Johannes
Am 13.10.2010 05:02, schrieb nmarques:
> Try "%package -n texvc" ("%files -n", "description -n", for the
> 'sub'-package), be mindful that if you do such (-n) the package won't
> inherit the prefix on the name.
>
> Building a new package from the same spec should clear that out.
>
> peace,
> nmarques
>
>>
>> Do you see a way how to handle this problem nicely except splitting up the
>> package into two packages, one for the scripts, one for the binary?
>>
>> Thank you and best regards,
>> Johannes
>>
>>
>> --
>> Johannes Weberhofer
>> Weberhofer GmbH, Austria, Vienna
>> --
>> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
>> For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
>>
>>
>
>
>
--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I've changed some of my .spec files to allow building in Fedora 13 in
OBS, and the results are quite nice, though there's a couple of things I
seek guidance:
* How to make usage of rpmlint in Fedora builds? I've noticed that
rpmlint doesn't run for F13 builds. Is there anyway I can place the
rpmlint config file from Fedora and make it run through it?
* What is the problem with {?dist}? (the usual .fc13.). Though the
packaged built locally are generated properly the ones built on OBS do
not get the .fc13. Was this intended? (not much of an issue though).
* How to add extra repositories? I'm not sure why, but qmake-qt4
package isn't being picked up for Fedora. How would one configure OBS to
grab packages from a Fedora Mirror ?
Thanks in advance,
Nelson.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
the personal navigation bar is quite confusing currently. This patch renames
the link to the user's home project to 'Home project' and adds another link to
the user page named by the users login. This should clarify the purpose of the
links and aligns them to what is found in the bottom left.
Should also be more future prov in case the user page should be expanded with
some social stuff (e.g. like 'My contributions').
--
Mit freundlichen Grüßen,
Sascha Peilicke
http://saschpe.wordpress.com
Hi,
python-qt3 keep in broken state for all targets since yesterday:
https://build.opensuse.org/project/monitor?project=home%3Afrispete%3APyQt-n…
and no rebuilds are possible, although a local build finishes
successfully, and the build logs looks fine!
What can I do?
Stumbled,
Pete
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org