@aquariopath Is that solved?

I've packaged that on GitHub.

Maybe it would be a good idea to add this approach to the Help Center. So anyone can search for "automount" on Solus and will find that approach.

The PKGBUILD in the AUR is also adding this dedicated directory.

They are retitled.

Rebase

The package that you can download there is iscan: https://dev.getsol.us/source/iscan/

Thank you, @algent and @joebonrichie for all your help so far. :)

In D11824#199391, @algent wrote:

is python3 now below python- or before?

Now it is fine. python3 is after python-

you're right. I took a quick look at the Makefiles and they intentionally put them to /etc/ - I don't know. But it would nice to change that. I've found the PKGBUILD of ArchLinux. They do the same, I think: https://github.com/archlinux/svntogit-community/blob/packages/apcupsd/trunk/PKGBUILD

Reorder dependencies

Reorder dependencies.

Relocate homepage

Add MAINTAINERS.md

Add MAINTAINERS.md

Add MAINTAINERS.md

Add MAINTAINERS.md

Add MAINTAINERS.md

Update source link

Update source link

Update source link

Change source link

Updating source link

Fix package.yml according to joebonrichie

In T9402#187661, @JoshStrobl wrote:

Just a reminder that we are in need of a new maintainer for this package. If you use paperwork(-backend,gui) then I would encourage you to come forward, get engaged in our packaging process, and update paperwork to the latest release possible. Otherwise, this package is at risk at being deprecated from the repository.

All new dependencies are ready for review.

Removed python3 dev env from rundeps

Split utils and removed python3 dev env. Works with out-of-the-box binary.

Updated package.yml to remove tests

The term package relies on stdin for testing itself. That cannot work in chroot of solbuild:

For python-coveralls we have a problem:

I had to build it against main profile. Unfortunately the unstable profile does not work. The build issues are included in the previous comment.

Thank you @JoshStrobl, the issue is solved.

Adressing the license issue

I think it would introduce a major maintenance problem as the maintainer of the solus repository have to ensure that new package, that build against the several python3 version would be updated accordingly. So the repository have to provide compatible packages for the several python versions, as the version support varys from python package to python package.

I've working with Solus at work and I've compiled Python 3.6 for local use.

In T9655#186332, @DasJott wrote:

I tried the flatpak version on my Laptop with HiDPI and it looks awful. Seems they also compiled it with a wrong version of wx.
Seems to not be trivial...

In T5551#181001, @nils wrote:

In practice, it seems to work well just to have the multi function printer in the group "lp". Scanning then works if the user is allowed to print (is member of lp). Other distributions seem to deal with the issue this way.

OVMF_CODE.fd and OVMF_VARS.fd tested with QEMU according to given test plan.

Separated docs subpackage

List of data.tar.gz can be found on https://download.openpaper.work/. There you can find the corresponding tar.gz. file for the version branch/tag.

Tried to make data for help files, but the building has cyclic dependency to paperwork-gtk itself.

Unfortunately the help files are not packaged. For that the Makefiles have the make data target. So I have the make the data in build process. For that I need imagemagick and pdflatex.

Rename to paperwork and "Depends on"

Add "Depends on"

Add "Depends on"

Cleanup package.yml and use patch for _version.py