[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-09-19 Thread Frederik Hartmann
I have verified the fix with the latest stable jenkins release. It was in fact changed and local libjni/jna is no longer required. Since the bug is fixed the only remaining question is if the handing of the system.so approach is a good idea and I think that this might not be the best place for thi

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-09-19 Thread Frederik Hartmann
Tiago, thanks for having a look! It seems that this issue was fixed on 1.136 (https://jenkins.io/changelog/) The s390x libs haven't been included in the shipped library prior to, a system install was required at that time. Anyhow, the locally installed libraries should be available and in the pa

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-09-05 Thread Frederik Hartmann
I'm trying to run Jenkins installed from the official Jenkins repository. SO far no Jenkins installation has worked out of the box and my mention that I can install a fresh system was an offering to you to replay the installation and make sure that no changes remain and I have the full installatio

[Bug 1787668] Re: ubuntu-release-upgrader crashed with KeyError: "The cache has no package named 'ubuntu-desktop'"

2018-08-29 Thread Frederik Hartmann
I hope that it will be backported to 16.04 as well, without applying this fix to an upgrade to 18.04 isn't possible. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787668 Title: ubuntu-r

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-08-28 Thread Frederik Hartmann
No problem! Issue 1 could be the result of a band-aid fix to get the system working at all, so let's keep that back for the moment. Regarding issue 2: I'm able to set up a fresh system with Jenkins on s390x. What information would you need to be able to reproduce this issue? -- You received thi

[Bug 1787668] Re: ubuntu-release-upgrader crashed with KeyError: "The cache has no package named 'ubuntu-desktop'"

2018-08-21 Thread Frederik Hartmann
The package 'ubuntu-desktop' doesn't exist for 16.04 on s390x where I encountered this error. Adding a bionic repository to sources.list without upgrading works as a hacky workaround since this package exists in bionic and the failing check is simply a verification if this package is installed.

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-07-18 Thread Frederik Hartmann
The only "duplicate" link there was, was the link I mentioned before. If the link is removed the error message is removed, however the library becomes unusable to java applications. Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-s390x/libjnid

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-07-17 Thread Frederik Hartmann
I have added my current apt upgrade log here to give you a broader context. The status of my system is added as well. The issue is here: /sbin/ldconfig.real: Can't link /usr/lib/s390x-linux-gnu//build/libjna- java-pvBsvy/libjna-java-4.5.1/build/native-linux- s390x/libjnidispatch.system.so to libj

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

2018-07-16 Thread Frederik Hartmann
Sure! 1. the specific steps to reproduce this bug Install package 2. which Ubuntu versions that are affected I was able to reproduce the bug on the following versions: 16.04 on s390 18.04 on s390 Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1662813] [NEW] Libjna-jni uses wrong path on package installation on s390x

2017-02-08 Thread Frederik Hartmann
Public bug reported: libjna-jni uses the wrong path for linking the library /usr/lib/s390x-linux-gnu/libjnidispatch.so on the z Systems s390x architecture, therefore applications relying on this library are unable to link to it, even if the package is installed. Creating the link manually fixes