Closed ennerf closed 11 months ago
Is this an issue on later versions of Ubuntu as well?
The reason for the change was to fix things on newer Ubuntus, see here:
Building on 22.04 has the same issue when installing on 20.04. I don't have newer test machines on hand. If you have one, you can try build 133 built on 22.04:
wget https://hebifiles.z13.web.core.windows.net/download/scope/snapshot/hebi-robotics-scope_1.9.0-133_amd64.deb
sudo apt install ./hebi-robotics-scope_1.9.0-133_amd64.deb
I mean does the deb install on ubuntu's newer than 20.04?
I rarely use Ubuntu, and my test machines are all on 20.04, so I can't easily test it.
OK, we'll take a look, I thought the change was compatible with 20 LTS as well as the other newer releases but perhaps not, or perhaps something regressed. It's specific to apps that use javafx.media
on Ubuntu 20, as far as I know, which most of our users aren't doing.
I just double-checked, but I'm not using javafx.media
either. Logged jlink command:
Linking a distribution JVM for Java 21 targeting linux.amd64.glibc
$ jlink '--strip-native-commands' '--no-man-pages' '--no-header-files' '--compress=1' '--add-modules' 'ALL-MODULE-PATH' '--limit-modules' 'jdk.accessibility,java.base,java.desktop,java.logging,java.datatransfer,java.xml,java.scripting,java.instrument,java.management,java.prefs,java.net.http,jdk.unsupported,jdk.crypto.cryptoki,java.sql,jdk.jdwp.agent,jdk.jshell,jdk.zipfs,jdk.jfr,jdk.httpserver,javafx.base,javafx.controls,javafx.fxml,javafx.graphics,javafx.swing,hydraulic.conveyor.launcher,dev.hydraulic.conveyor.control' '--compress=2' '--no-header-files' '--no-man-pages' '--strip-debug' '--vm=server'
I did some more testing, and removing the dependencies via app.linux.debian.control.Depends = [ ]
fixes the issue for my particular app
Conveyor | Ubuntu 20.04 | Ubuntu 22.04 |
---|---|---|
9.2 | ok | ok |
11.4 | fails | ok |
11.4 + no deps | ok | ok |
I tried the generated sample javafx app and it can install OK for me on my Ubuntu 20 VM so maybe there is a configuration difference between the two setups. Is it possible that you don't have the universe
repository enabled? Media codecs and Linux often don't work well due to licensing hangups.
Arguably we should only be applying this hack if javafx.media
is actually used, but it's done via static config and seemed harmless to always depend on. I'm not sure how far this should be considered a Conveyor bug vs just Ubuntu being user unfriendly. The whole concept of a core vs a "universe" vs a "multiverse" repository is pretty obscure.
Yes, I'm testing on a stock install without extra repositories. I'm not fond of the behavior, but it's not a big issue as long as I can easily disable it. If it has to be static, maybe it could work as a include required("/stdlib/jvm/javafx/media.conf")
config?
Thanks for looking into it.
I'm having some issues with Linux builds when building with Conveyor versions 9.3 through 11.4. The last working version was 9.2. It happened with
ubuntu-latest
on GH-Actions as well as local builds on 20.04.Creating and installing a debian package:
Issue:
Is there any log output that'd be helpful?