I updated to .6 but 2 env vars are still broken, NZBHYDRA_DISABLE_WRAPPER_CHECK and NZBHYDRA_FORCE_GENERIC. The 2nd I patched for .5, but I don't feel like patching back the first one so we'll wait.

@gee Ah, I see. The only thing I do is check whether the package builds and whether nzbhydra starts up fine after installing the built package. Should be enough to catch any packaging error, but if you can't do that because of java then it doesn't make much sense really.

@jkhsjdhjs sure, but I don't use those because of java (I've updated to latest Java which at least in the past did not work with nzbhydra) so it'll be hard to know if it the changes are fine.

@gee: Very nice, dropped these patches for nzbhydra2 and nzbhydra2-bin as well. Btw would you mind co-maintaining these packages? I think it would be great if all of these packages were updated at the same time, by whoever has time to update them first.

@ashaman-crypto alright it wasn't that much more work so I pushed it in the meantime.

@jkhsjdhjs as you can see I dropped 2 patches, and should soon be able to drop the last one too.

@ashaman-crypto we know we're out of date, but the latest doesn't include all the stuff we need so we'll wait on .6 which will be out soon hopefully.

Feel free to propose the other changes upstream if you have the time. Btw regarding the package update: it's better to export NZBHYDRA_DISABLE_WRAPPER_CHECK in the nzbhydra2.sh script, as it is then also exported when nzbhydra is ran manually, without the systemd service.

We got the ARM build so I updated the package and we don't need to keep the OG wrapper anymore. Do you want to request the other env variables to drop some patches or would you rather I do it?

Hey, didn't update this package yet as the arm64 build is not part of the release assets. Let's see if it will be added in the near future.