Integrated: 8295111: dpkg appears to have problems resolving symbolically linked native libraries

[Alexey Semenyuk]

On Thu, 18 Apr 2024 19:56:43 GMT, Alexey Semenyuk  wrote:

> Pass a path with resolved symlinks to `dpkg -S` command. If it fails, try the 
> original path if they differ.
> 
> Testing on Ubuntu 24.04 passed. Successfully created a .deb package from 
> SwingSet2.jar with the not-empty list of dependencies. Before the fix the 
> list of required packages was empty. In jpackage log:
> 
> 
> [19:30:48.784] Running dpkg
> [19:30:49.118] Command [PID: 244104]:
> dpkg -S /usr/lib/x86_64-linux-gnu/libm.so.6
> [19:30:49.118] Output:
> libc6:amd64: /usr/lib/x86_64-linux-gnu/libm.so.6
> [19:30:49.118] Returned: 0
> 
> [19:30:49.118] /lib/x86_64-linux-gnu/libm.so.6 is provided by [libc6]
> 
> 
> It was looking for a package providing "/lib/x86_64-linux-gnu/libm.so.6" 
> library, but the actual argument to "dpgk -S" command was 
> "/usr/lib/x86_64-linux-gnu/libm.so.6".

This pull request has now been integrated.

Changeset: 32946e18
Author:Alexey Semenyuk 
URL:   
https://git.openjdk.org/jdk/commit/32946e1882e9b22c983cbba3c6bda3cc7295946a
Stats: 44 lines in 1 file changed: 19 ins; 3 del; 22 mod

8295111: dpkg appears to have problems resolving symbolically linked native 
libraries

Reviewed-by: almatvee

-

PR: https://git.openjdk.org/jdk/pull/18844

Re: Integrated: 8295111: dpkg appears to have problems resolving symbolically linked native libraries

[Michael Hall]

I don’t know what flavors you are looking to support but there seems to be 
somewhat different issues on a Raspberry Pi. I was just trying to use jpackage 
there.

I am getting errors like the command

dpkg -S /lib/aarch64-linux-gnu/libXau.so .6 
The file isn’t found

These actually appear to have entries in

/usr/lib/aarch64-linux-gnu

Which in turn appear to be symbolic links like…

/usr/lib/aarch64-linux-gnu/libXau.so .6 -> libXau.so 
.6.0.0

I am thinking I could try making symbolic links as a workaround myself.

Re: Integrated: 8295111: dpkg appears to have problems resolving symbolically linked native libraries

[Michael Hall]

I was apparently at least partly misunderstanding this. I thought I verified a 
missing file on one exception trace. I installed what appeared to be missing 
packages and that one no longer shows up.

I still get exception traces on some .so files which appear to be reporting 
errors on dpkg -S commands unable to determine the packages for some files. The 
files are in fact there. I was seeing these because I was running verbose. 
Trying some old stuff I still have to see if I could get jpackage to work. 
Without verbose it runs through indicating no errors. However, running the 
created deb file doesn’t appear to be creating an app that I can find. Nothing 
else seems to give me any information on what the actual install is doing. I 
did notice in the verbose output a lot of libjvm.so  is 
missing messages. 

Anyhow, for my current purposes the code doesn’t have to run as a Pi 
application. I can command line if I have to. Or I was thinking about modifying 
some of the application code to run standalone.

Thanks anyhow,

Mike

> On Apr 19, 2024, at 1:13 PM, Michael Hall  wrote:
> 
> I don’t know what flavors you are looking to support but there seems to be 
> somewhat different issues on a Raspberry Pi. I was just trying to use 
> jpackage there.
> 
> I am getting errors like the command
> 
> dpkg -S /lib/aarch64-linux-gnu/libXau.so .6 
> The file isn’t found
> 
> These actually appear to have entries in
> 
> /usr/lib/aarch64-linux-gnu
> 
> Which in turn appear to be symbolic links like…
> 
> /usr/lib/aarch64-linux-gnu/libXau.so .6 -> libXau.so 
> .6.0.0
> 
> I am thinking I could try making symbolic links as a workaround myself.
> 
> 
> 
> 
> 
>