Arch Linux User Repository

There is now a version of this package that will give you the released version instead of latest Git: https://aur.archlinux.org/packages/fw-fanctrl

There was a recent issue with the package build failing due to a missing .whl file. A workaround has been put in place.

Further discussion will happen in https://github.com/TamtamHero/fw-fanctrl/issues/111 for a longer-term fix.

The --dest-dir "${pkgdir}" \ is causing a problem, because .service is using PYTHON_SCRIPT_INSTALLATION_PATH which is set to PYTHON_SCRIPT_INSTALLATION_PATH="$DEST_DIR$PREFIX_DIR/bin/fw-fanctrl" and something like

ExecStart=/usr/bin/python3 "/home/user/.cache/paru/clone/fw-fanctrl-git/pkg/fw-fanctrl-git/usr/bin/fw-fanctrl" --output-format "JSON" run --config "/etc/fw-fanctrl/config.json" --silent 

Ends up in the systemd service file.

DEST_DIR is used several time in that install.sh script for copying of some some stuff, so in most cases it is correct. I think, we may have to patch the resulting service file or solve it with upstream.

Opened issue: https://github.com/TamtamHero/fw-fanctrl/issues/129

@Mikescher Good catch, thank you! Not sure why I put it into makedepends instead of depends but I've fixed it now.

I think python-jsonschema should be a normal dependency, instead of a make-only dependency.

Otherwise I get an error executing fw-fanctrl in Configuration.py [1].
The dependency was added last week in commit b7309 [2]

[1] https://github.com/TamtamHero/fw-fanctrl/blob/main/src/fw_fanctrl/Configuration.py
[2] https://github.com/TamtamHero/fw-fanctrl/commit/e4bfe9fd9eda386dbf6bc3975ee5013705fb7e09#diff-2ba53b33af817afae5d7a93641c6addefcdd3853d4453f584784eec793fc3a74R6

There is now a version of this package that will give you the released version instead of latest Git: https://aur.archlinux.org/packages/fw-fanctrl

There was a recent issue with the package build failing due to a missing .whl file. A workaround has been put in place.

Further discussion will happen in https://github.com/TamtamHero/fw-fanctrl/issues/111 for a longer-term fix.

@Nashenas I've reverted the enabling of pytest for now. Will need to check which dependencies I need for this to work properly at a later point.

The latest version is failing for me. It has an unspecified build dependency on the python-pytest package. I installed it manually but it still fails with:

Successfully built fw_fanctrl-1.0.0-py3-none-any.whl
==> Starting check()...
============================================================ test session starts ============================================================
platform linux -- Python 3.13.1, pytest-8.3.4, pluggy-1.5.0 -- /usr/bin/python
cachedir: .pytest_cache
rootdir: /home/user/.cache/paru/clone/fw-fanctrl-git/src/fw-fanctrl
configfile: pyproject.toml
collected 0 items

=========================================================== no tests ran in 0.03s ===========================================================
==> ERROR: A failure occurred in check().
    Aborting...
error: failed to build 'fw-fanctrl-git-1.0.0.r4.b37bd3b-6':

The issue with the missing bin script has been solved.

In detail: Problem was the order of install steps - the remaining part of the install script being used deleted the file due to legacy procedures.

I plan in the coming days to coordinate to which degree I should continue to rely on the script but for now this package is back working.

I am a bit tied down by a headache and limited free time. I'll check into it this evening German time to see what's the problem.

Interestingly, for me the bin script is still part of the package when I build it. (EDIT: That was my mistake for not building the package from a clean state.)

latest package update results in an empty /usr/bin directory. This means the fw-fanctrl command is no longer found and the service fails to start

temporary workaround: python3 -m fw_fanctrl