Hi All,
we are currently facing some database issues. Therefore api.opensuse.org is down.
We are working on it. Details will follow.
Thanks and sorry for the trouble.
Kind regards,
Marco
--
Marco Strigl
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I am having trouble when signing my packages
# sign /srv/obs/jobs/x86_64/hw\:\:RHEL_7\:\:test-4486c61b9673b52a1e1c930e9e958fb6\:dir/xxxx-2.10.2-1.1.x86_64.rpm
gpg: [don't know]: 1st length byte missing
gpg: keydb_search failed: Invalid packet
gpg: skipped "xxxx@localhost": Invalid packet
gpg: signing failed: Invalid packet
I've tried regenerating gpg key with the same result.
Helgi Waag
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I've ported my application showimage to KF5 and when building on OBS I get the following
error in the install step:
[ 57s] ~/rpmbuild/BUILD/showimage-1.10
[ 57s] + %suse_update_desktop_file showimage
[ 57s] /var/tmp/rpm-tmp.oi5c9p: line 32: fg: no job control
[ 57s] error: Bad exit status from /var/tmp/rpm-tmp.oi5c9p (%install)
Is suse_update_desktop_file still available and still to be used as described here ?
https://en.opensuse.org/openSUSE:Packaging_guidelines#.25suse_update_deskto…
Full log is here:
https://build.opensuse.org/package/live_build_log/home:martinkoller/showima…
--
Best regards/Schöne Grüße
Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
Geschenkideen, Accessoires, Kulinarisches: www.lillehus.at
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
The submit request notifications are delayed or missing. I have no
chance to follow the process.
For example for this one I got an email one day later
https://build.opensuse.org/request/show/445689
BTW could we replace these relative timestamps on the webinterface
like "wrote 1 day ago" by absolute and more precise ones like "%F %T"?
IMO this "some time ago" thing is a really annoying fashion all over the
web nowadays.
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi
I try to compile some Perl-Packages for SLES11 SP4 but getting the Error
unresolvable: conflict for provider of perl(version) >= 0.87
This
https://lists.opensuse.org/opensuse-buildservice/2013-10/msg00060.html
is not working. I have set the same Attributes as in the original Perl
Project:
jan@tablette:~/src/osc/home:janhebler:tools-backport/perl-Module-Metadata>
osc meta prjconf
Ignore: perl-Compress-Raw-Zlib:perl
Ignore: perl(Compress::Raw::Zlib):perl
Prefer: perl-version
Ignore: perl-version:perl
Ignore: perl(version):perl
jan@tablette:~/src/osc/home:janhebler:tools-backport/perl-Module-Metadata>
but this does not help. Any hints?
Thank You
Jan
I am trying to update an OBS server, currently running 2.3.8 on SLES11
I am able to update to 2.4 with database migration, but can't get LDAP
to work. This is not a problem: on my test machine I was then able to
upgrade to 2.5 successfully, with working LDAP.
However, on my live server, the database migration fails:
# RAILS_ENV="production" rake db:migrate
Mysql2::Error: Table 'obs_api.delayed_jobs' doesn't exist: SHOW FULL
FIELDS FROM
`delayed_jobs`/srv/www/obs/api/app/models/configuration.rb:95:in
`delayed_write_to_backend'
Any help or advice greatly appreciated. I really hate running such an
old version of OBS
--
Magnus Lewis-Smith
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
Could the OpenSUSE Build Service add support for targeting ARM
(armhfp, aarch64) for Fedora, in addition to OpenSUSE? It doesn't have
to be active by default or anything, but it'd be great if I could
target both OpenSUSE and Fedora for building packages for ARM
architectures using OBS.
Thanks in advance and best regards,
Neal
--
真実はいつも一つ!/ Always, there's only one truth!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On Wed, Dec 14, 2016 at 10:49 AM, Robert Munteanu
<robert.munteanu(a)gmail.com> wrote:
> I tried a Leap 42.2 image, I think it was one similar to
>
> openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2016.11.25-Build1.9.raw.xz
I tried this and it boots! And the network was configured via dhcp.
I also tried a recent Tumbleweed release, but the boot stopped shortly
after loading initrd.vmx. I'm fine with Leap. Even if a 32-bit
openSUSE of some sort on the Raspberry would be nice.
The only thing I have noted thus far is that the default gateway does
not get set, even though it is in /etc/sysconfig/network/routes (via
yast). I have added it to /etc/rc.d/after.local
Also, /etc/os-release would be great if it indicated the Raspberry. I
guess I should only depend on seeing that arch is aarch64
It is:
NAME="openSUSE Leap"
VERSION="42.2"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.2"
PRETTY_NAME="openSUSE Leap 42.2"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
I think further discussions are not for this list. Now to find a more
appropriate forum for openSUSE and the Raspberry.
I'm back with openSUSE on the Raspberry, at least.
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I have just installed SLES on my Raspberry PI 3. It seems to be
working great. I had previously been trying openSUSE on this device,
but it is always dead. Which seems odd because there is only one
version of the PI 3. So I cannot see how it can work for some and not
others. Anyway, SLES works great.
My goal is to try to get a hardware interface running on openSUSE
(porting some local embedded code to what will be a kernel driver).
So, I thought I would play with the SLES until the openSUSE variant
works.
Part of this post is being happy to report that SLES works. The other
part is to ask a question or two about SLES and OBS. I'm not certain
this is the best place to ask my question. But I am trying to find my
way around.
When I tried to build some libraries, various include files were
missing. Which is expected. So, I thought I would install the various
-devel packages. I had expected them to be in the repositories that
SLES enabled when I registered it. Oddly, there are almost no -devel
packages. Like the one that contains X11/keysym.h
Which brings me to my question:
Since Leap is supposed to have brought SUSE and openSUSE closer
together, should I be able to use OBS repositories with SLES? If so,
must I restrict myself to SLES repos? That is, might I be able to
install packages from Factory? I see that SLES is not enabled for most
of OBS.Where is a good source of SLES repositories? Beyond the three
that SLES enables upon registration.
--
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,
In the following project the cmake script probes for SSSE3 support in
the compiler and refuses to build:
[ 297s] -- Performing Test HAVE_SSSE3 - Failed
[ 297s] CMake Error at 3rdParty/hyperscan/cmake/arch.cmake:23
(message):
[ 297s] A minimum of SSSE3 compiler support is required
[ 297s] Call Stack (most recent call first):
[ 297s] 3rdParty/hyperscan/CMakeLists.txt:248 (include)
The build randomly fails on some workers, works on others:
Works:
https://build.opensuse.org/package/live_build_log/home:andreas_baumann/stru…
Doesn't work:
https://build.opensuse.org/package/live_build_log/home:andreas_baumann/stru…
So my suspission is that some workers run on old machines.
My question: is there a way have special build tag like
BuildRequires: worker_has_ssse3
to build packages - which require it - on never hardware?
The other alternative I see is to use cross-compilation from
SSSE3/non-SSSE3 hosts to SSSE3-hosts..
..or of course to press "Trigger Rebuild" on failed builds till
they find a more modern worker. ;-)
Greetings
Andreas
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org