Hi Werner,
Please wait for the 20160613 build, it should fix this issue. Seems the
build system was caching some things so my change did not apply.
Best regards
Lars
On 13.06.2016 09:01, Werner Flamme wrote:
Hi Lars,
I erased version 20160610, because it wouldn't work as desired.
But with
Hi Lars,
I erased version 20160610, because it wouldn't work as desired.
But with 20160612 it looks very similar:
# omd sites
/omd/versions/1.31.20160612/bin/python: error while loading shared
libraries: libpython2.7.so.1.0: cannot open shared object file: No such
file or directory
# ldd
Hi,
the issue will be fixed in next daily. It affected all RPM packages.
Best regards
Lars
Am 2016-06-10 12:31, schrieb Werner Flamme:
Hello OMDlers,
I just did a "zypper up", which pulled omd-daily and, as a dependency,
omd-daily-1.31.20160610 (from
Hi Werner,
please run this command and send me the output:
ldd /omd/versions/1.31.20160610/bin/python
For me it shows something like this:
> ldd /omd/versions/2016.06.10.cee/bin/python
linux-vdso.so.1 => (0x7ffd8fbd6000)
libpython2.7.so.1.0 =>
Hi Werner,
I think you problem has to do with the implementation of python 2.7
directly inside OMD. If you take a look at the git repo you will see many
changes the last days and also many bug fixes :)
I would recommend to stay at your version what was working.
Best regards
Andreas
Werner
Sven Nierlein [10.06.2016 12:35]:
> Hi,
>
> you cannot install the sp3 rpm on sp4. Unfortunatly, there are no sp4 packages
> yet. But you could try to build the rpms manually.
>
> Cheers,
> Sven
Hi Sven,
you do not tell me that there is libpython2.7 for SLES 11 SP3 (which is
out of
Hello OMDlers,
I just did a "zypper up", which pulled omd-daily and, as a dependency,
omd-daily-1.31.20160610 (from
http://labs.consol.de/repo/testing/sles11sp3/x86_64, which is defined as
a repository).
My next step was "omd sites", but then I had to stop:
