Arch Linux User Repository

@rhysperry111 I'm actually just checking this software out, haven't started using it yet and that was just something I ran into straight away as I was trying to install this on my server. So I'll have to politely decline your offer.

I'm actually currently on a 2 week holiday, so don't have any device with me that has git access to the AUR. How do you feel about being made co-maintainer? I don't use komga myself anyway, so it's probably best to have somebody that can spot issues if they arise. All I really do is run a script that grabs the latest version from GitHub with some git commands, bumps the pkgver and updates the checksums blindly

Could this depend on java-runtime-headless instead? It appears to work just fine with just the headless package.

I probably won't update this package for another week because I managed to bork my laptop. I don't have a live USB and I can't get one until I get out of quarantine

By the way, when updating the main pkgver, don't forget to reset pkgrel back to 1. That one is usually only incremented when the pkgver stays the same but you want to upgrade the package itself.

Sure, thanks for the help. I'll add it now and make upstream aware

If you feel like adding a systemd service to make it easier to just install and run, here's a git patch

It adds these files:

 komga.env      | 13 +++++++++++++
 komga.service  | 17 +++++++++++++++++
 komga.sysusers |  1 +
 komga.tmpfiles |  4 ++++

Yeah, that should work fine, thanks

Ah, sorry. I made a mistake.

I think the latest commit has fixed it.

It doesn't have to do with using yay or some other package manager (unless they never reuse build directories).

You can reproduce it with just makepkg:

 - 1. Create a clean build dir
 - 2. Checkout to a previous commit (like the one updating to 0.40.0)
 - 3. `makepkg`
 - 4. Checkout to origin/master
 - 5. `makepkg` <- will fail unless you delete the existing `komga.jar`.