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 <http://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 <mik3h...@gmail.com> 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 <http://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 <http://libxau.so/>.6 -> libXau.so > <http://libxau.so/>.6.0.0 > > I am thinking I could try making symbolic links as a workaround myself. > > > > > >