-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide valid Linux CI builds in Releases section as well #64
Comments
Hello, @FriedrichFroebel Are you using ubuntu as distribution? The binaries the CI system creates are built on ubuntu-latest, you need to use ubuntu as well. I'm investigating the other issues you mention. EDIT: The rpm and deb packages metadata seem to be fine:
|
I tested this on a distro based upon Ubuntu 22.04 (AFAIK it only does some irrelevant changes), which should correspond to ubuntu-latest. The issue is not about the metadata itself, but about them being incomplete/sparse and not declaring any Qt dependencies for example, which AFAIK need to be present on the system for the builds to work. |
Has this been resolved and is it possible to download it somewhere? I think it would be great as it will draw in more users to this latest scantailor fork. |
AFAIK not. |
I would actually prefer an AppImage to be available as this does not require an installation. Besides this: The Debian builds do not work on Ubuntu 22.04 as |
For now, it seems like CI does some Linux builds, but only uploads them as build artifacts which expire after some time and are not accessible without being logged in to GitHub. It probably would make more sense to provide them in the Releases section as well.
Before doing so, they might require some more fixes/documentation:
The Debian package metadata is mostly empty and the requirements seem to be undeclared?
The RPM package metadata seems to be similar.
The regular build fails with just "Illegal instruction".
The AppImage build fails as well:
By contrast: Building the package from source does not expose these problems.
The text was updated successfully, but these errors were encountered: