Skip to content
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

Open
FriedrichFroebel opened this issue Jul 17, 2023 · 6 comments
Open

Provide valid Linux CI builds in Releases section as well #64

FriedrichFroebel opened this issue Jul 17, 2023 · 6 comments
Labels
enhancement New feature or request

Comments

@FriedrichFroebel
Copy link

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:

    qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
    This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    
    Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
    
    Aborted
    

By contrast: Building the package from source does not expose these problems.

@ghost ghost self-assigned this Aug 2, 2023
@ghost ghost added the enhancement New feature or request label Aug 2, 2023
@ghost
Copy link

ghost commented Aug 14, 2023

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

@FriedrichFroebel
Copy link
Author

FriedrichFroebel commented Aug 15, 2023

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.

@artelse
Copy link

artelse commented Apr 5, 2024

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.

@FriedrichFroebel
Copy link
Author

AFAIK not.

@FriedrichFroebel
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants