Open FriedrichFroebel opened 1 year ago
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:
rpm -qp scantailor.rpm
scantailor-advanced-1.0.19-1.x86_64
dpkg-deb -I scantailor.deb
new Debian package, version 2.0.
size 2041752 bytes: control archive=660 bytes.
222 bytes, 9 lines control
955 bytes, 11 lines md5sums
Architecture: amd64
Description: Interactive post-processing tool for scanned pages.
Maintainer: 4lex4 <4lex49@zoho.com>
Package: scantailor-advanced
Priority: optional
Section: devel
Version: 1.0.19
Installed-Size: 5754
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 libjpeg62-turbo
cannot be found.
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 AppImage build fails as well:
By contrast: Building the package from source does not expose these problems.