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

Alexander Matveev almatvee at openjdk.org
Thu Apr 18 21:06:55 UTC 2024


On Thu, 18 Apr 2024 19:56:43 GMT, Alexey Semenyuk <asemenyuk at openjdk.org> 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".

Looks good.

-------------

Marked as reviewed by almatvee (Reviewer).

PR Review: https://git.openjdk.org/jdk/pull/18844#pullrequestreview-2009895564


More information about the core-libs-dev mailing list