Hello,
Is it possible to introduce additional build status for packages with
infeasible _constraints? Now they are just scheduled.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
Fedora 24 is near release. I have added the needed project
and it seems to be able to build on first look.
However, since it is not yet released, it is not yet added to the
simple list in webui.
But you can help testing by specifing it manual in your project xml.
Note: thanks to our new DoD functionality there is also a seperate
"update" repo available. But the default will remain to the standard repo.
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Ubuntu 16.04 moved a large part from main to universe:
https://lists.ubuntu.com/archives/ubuntu-devel-announce/2016-April/001179.h…
Things like docbook, texinfo, ... are now in universe, so they are not present in OBS.
In the past, I had to import only a few packages - this time, it looks like a larger pile.
Others will propably miss (the same) packages.
I understand, the complete universe can't be part of OBS for legal reason.
So if we can't add the whole universe, would it be possible to create a global Ubuntu 16.04 import project?
Each package is just a _service file to download the 2-3 source files from archive.ubuntu.org. That way
review of package additions are simple.
I offer to share the packages, that I need to import for my projects [which include po4a and wxWidgets3.0 and their dependencies].
Regards,
Martin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
JFYI for OBS developers
* I had to revert the phantomjs 1.9 -> 2.1 update.
2.1 fixed building for non-x86_64, but it broke also at least one
webui testcase and blocks deployment atm.
We need to find out the reason behind later on. The failure is
still visible for ppc64le for example, because the phantomjs 1.9
is not building there.
* ruby 2.3.0 -> 2.3.1 update.
I saw no effects of that so far.
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
We are running an own OBS instance of pretty old version 2.4.5, which we
are in process of updating currently.
Unfortunately we need to build Ubuntu 16.04 packages, while we are still
not updated.
Adding Ubuntu 16.04 to our project, gives the following error on all
packages displayed as "broken" on monitor page:
interconnect error: unknown element: download
Any ideas or is Ubunut 16.04 only possible with OBS 2.6?
Ralf
PS. I tried to get some pointers about best way for an updatable (local)
OBS installation in an other mail 3 weeks ago, but got no answers.
--
Ralf Becker
Director Software Development
Stylite AG
Isaac-Fulda-Allee 9 | Tel. +49 6131 32702-0
D-55124 Mainz | Fax. +49 6131 32702-70
Email: rb(a)stylite.de
www.stylite.de | www.egroupware.org
Managing Directors: Andre Keller | Ralf Becker | Gudrun Mueller
Chairman of the supervisory board: Prof. Dr. Birger Leon Kropshofer
VAT DE214280951 | Registered HRB 46224 Mainz Germany
Hello,
Now, I am trying to understand why
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/buil…
is failed for a year.
I would like to check a hypothesis that `build` used to build `build` is
outdated for armv7l and this leads to this unit-test failure.
I can bootstrap `build` for armv7l by disabling %check section, but then
I can not understand how to rebuild `build` using built `build`.
I mean:
[ 1s] Using BUILD_ROOT=/var/cache/obs/worker/root_3/.mount
[ 1s] Using BUILD_ARCH=armv7l:armv6l:armv5tel
[ 1s] Doing kvm build in /var/cache/obs/worker/root_3/root
[ 1s]
[ 1s]
[ 1s] armbuild18 started "build build.spec" at Sun Apr 24 08:07:22
UTC 2016.
[ 1s]
[ 1s] Building build for project 'openSUSE:Factory:ARM' repository
'standard' arch 'armv7l' srcmd5 '144599aaf128bbcccb04122b992978e1'
[ 1s]
[ 1s] processing recipe
/var/cache/obs/worker/root_3/.build-srcdir/build.spec ...
[ 1s] running changelog2spec --target rpm --file
/var/cache/obs/worker/root_3/.build-srcdir/build.spec
[ 1s] init_buildsystem --configdir
/var/run/obs/worker/3/build/configs --cachedir /var/cache/build
--prepare --clean --rpmlist /var/cache/obs/worker/root_3/.build.rpmlist
/var/cache/obs/worker/root_3/.build-srcdir/build.spec build
rpmlint-Factory ...
How could I control where did init_buildsystem came from?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
What is the prefered way to merge changes in the devel project?
osc bco pkg
cd home:user:devel:prj/pkg
osc up -u
edit pkg.spec
osc vc
osc commit
now devel:prj/pkg gets changes by someone else, and
home:user:devel:prj/pkg goes into state 'broken':
broken: conflict in file pkg.spec
Even if the changes are merged manually the pkg remains broken.
I think its required to just update the _link to point to HEAD.
Is there a command to do just that? osc repairlink says:
BuildService API error: source link is not broken
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello!
First of all than you for Ubuntu 16.04 support.
Console apps are built fine but X11 ones not:
[ 29s] [17/238] Can't locate Digest/MD5.pm in @INC (you may need to
install the Digest::MD5 module) (@INC contains: /.build /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at
/.build/Build.pm line 24.
[ 29s] BEGIN failed--compilation aborted at /.build/Build.pm line 24.
[ 29s] Compilation failed in require.
[ 29s] BEGIN failed--compilation aborted.
[ 29s] installing
[ 29s] Adding 'diversion of /usr/share/initramfs-tools/hooks/klibc to
/usr/share/initramfs-tools/hooks/klibc^i-t by klibc-utils'
[ 29s] [18/238] Can't locate Digest/MD5.pm in @INC (you may need to
install the Digest::MD5 module) (@INC contains: /.build /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at
/.build/Build.pm line 24.
[ 29s] BEGIN failed--compilation aborted at /.build/Build.pm line 24.
[ 29s] Compilation failed in require.
[ 29s] BEGIN failed--compilation aborted.
[ 29s] installing
[ 30s] /var/lib/dpkg/info/x11-common.postinst: line 13: update-rc.d:
command not found
[ 30s] /var/lib/dpkg/info/x11-common.postinst: line 16: invoke-rc.d:
command not found
[ 30s] dpkg: error processing package x11-common (--install):
[ 30s] subprocess installed post-installation script returned error
exit status 127
[ 30s] Errors were encountered while processing:
[ 30s] x11-common
[ 30s] exit ...
See more at
https://build.opensuse.org/package/live_build_log/home:DarkSS:deb/hzs-remin…
f.e.
--
Best regards,
Dmitriy Perlow
R&D chemical engineer
Lekpharm JLLC
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm using 'obs service rr $prj $pkg' to trigger an update.
In home:olh:testing-xen-unstable/libvirt the set_version part is not
processed anymore. This used to work two weeks ago. And this appears to
work in home:olh:xen-unstable/libvirt with the same _service file.
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
I have already one OBS installed server. Now I would like to configure
this OBS as a cluster, i.e. add a few new machines to it.
I have been installed OBS on another 2 machines (ISO from openbuildservice.org).
Would it be enough just to edit /usr/lib/obs/server/BSConfig.pm file
on the *main* machine and /etc/sysconfig/obs-server fine on the
*slave* systems?
I want that worker on *main* system continue builds.
All management should happening using *main* system (using this IP),
i.e. I'm going to disable as much as possible OBS services on another
systems.
Unfortunately I found only README.SETUP file (obs-api package) and
have no another documentation or examples or something like this. I
don't want to broke/hack OBS on *main* system. It's used in
production.
It would be great if somebody, who already configured OBS as a
cluster, tells what exactly should be done.
Cheers,
Alex
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org