Hello All,
I'm running a private instance and I'd like to enable networking on my
workers so they can build some java apps, via maven, which need to
download pom's/war's from the net. I ask google but he wasn't much
help so I'm hoping someone here can help;-)
How can I go about doing this?
--
Later,
Darin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I try to add a new board to openSUSE:Factory:ARM. I did this already in
the past and for doing that I had to modify the JeOS package and add
links to it with JeOS-<boardname>. Those links are no more in
openSUSE:Factory:ARM, instead of this the JeOS package contains now a
"_multibuild" file, which is generated by the pre_checkin.sh script. I
added my board to pre_checkin.sh. But how to trigger now the build of my
new added board image instead of the native JeOS image?
In the past I just called "osc build factory armv7l" in the
JeOS-<boardname> linked package to build it local, and I committed it to
my work project to build it in obs.
osc --version
0.155.0
Br,
Frank
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I suffer from a libqt5-qtbase build, that is performing perfectly well on a
local build, but fails on OBS for 13.2 due to a failing glob:
File not found by glob: /home/abuild/rpmbuild/BUILDROOT/libqt5-
qtbase-5.7.1-10.1.x86_64/usr/lib64/libQt5EglFsKmsSupport.so.*
https://build.opensuse.org/package/live_build_log/home:frispete:PyQt5/libqt…
although it is excluded explicitly for 13.2:
%if 0%{?suse_version} != 1320
%{libqt5_libdir}/libQt5EglFsKmsSupport.so.*
%endif
Line 1025:
https://build.opensuse.org/package/view_file/home:frispete:PyQt5/libqt5-qtb…
I cannot see, what's wrong with this clause. Do you? (Yes, I know, it's a lame
expression, but I don't build for older versions anyway..)
While at it, I tried to build the package locally with --vm-type=kvm in order
to get the build behaving even more like the BS builds, but that fails due to
OOM. How can I get the osc kvm build respect the _constraints of this package?
Thanks in advance,
Pete
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Not sure what the correct list is to report mirror issues, but
http://tux.rainside.sk/opensuse/ is empty.
laf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I have a script that makes a list of all the RPMs that must be
installed to satisfy a directory full of binary programs. The RPMs are
already installed. The purpose of the script is to get the list of
RPMs so they can easily be installed on a different system.
I have no trouble finding the name of the RPM with the needed libraries.
For example,
rpm -q --queryformat "%{NAME}\n" --whatprovides /usr/lib/libsndfile.so.1
reports:
libsndfile1
So, "zypper in libsndfile1" does the deed.
My problem is when I want to install the -devel package as well. In
this case, I need to install libsndfile-devel. Note the missing '1' in
the name.
My question is, given that I know the name of the library RPM, how can
I derive the name of the -devel package? Sometimes it is just to add
-devel to the name. Sometimes not.
Is there some brilliant way to do this reliably?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi List,
there's somthing strange with one of our invis-Server
Download-Repositories. After adding openSUSE Leap 42.2 as a build target
in "spins:invis:common" the packages are builded, but there's no
Download-Repo.
The URL
http://download.opensuse.org/repositories/spins:/invis:/common/openSUSE_Lea…
ends up in an 404.
Any idea why?
Stefan
--
www.invis-server.org
Stefan Schäfer
Ludwigstr. 1-3
63679 Schotten
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
OBS 2.7.3 released
==================
This release fixes several bugs. For more details please look into the ReleaseNotes attached to this mail.
Updaters from any OBS 2.7.0 release can just upgrade the packages
and restart all services. Updaters from former releases should
read the README.UPDATERS file.
OBS update are available from the following projects:
https://build.opensuse.org/project/show/OBS:Server:2.7
The appliance can be downloaded from
http://openbuildservice.org/download
Details from the Release Notes of 2.7.3:
========================================
Feature backports:
==================
* none
Changes:
========
* Compability with OBS 2.8 remote instances
Bugfixes:
=========
* [api] Project meta data was corrupted after undelete
* [api] Raising access and sourceaccess permissions as admin is working again
* [backend] Download on demand sync fixes
* [webui] Fixed revert to a specified source revision
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all,
I have an OBS installation 2.7.2 which got installed as 2.3(?) and updated over the years.
I'm building SLES11-SP{1,2,3,4}, SLES12{-SP1,-SP2}, CentOS-7 against local SMT / mrepo mirrors.
It is connected to openSUSE.org OBS via OBS interconnect. Some projects are also building against
openSUSE.org:CentOS:CentOS-6/standard
My "problem" now is: I cannot get rid of the unneeded i586 architecture.
No matter what I do with the web frontend or "osc api -e /configuration", it keeps coming back.
Also stopping everyhting, editing configuration.xml and then restarting the services does not get rid of it reliably.
Does it hide somewhere in the database?
How to get rid of it?
The problem with it is, that it is cluttering web interfaces (the statistics on the status monitor page are always for
i586 default...) and that just adding a repository to a project actually adds the repo as x86_64 and i586.
My playground obs instance at home, just building for Leap42.1 to prove bugs for mls is running without i586 just fine,
so I know it must be possible.
Thanks for any hints,
seife
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
