I am getting:
==> Validating source files with sha256sums...
coolercontrol-0.15.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Seems like binaries were updated while keeping the same version number
Git Clone URL: | https://aur.archlinux.org/coolercontrol.git (read-only, click to copy) |
---|---|
Package Base: | coolercontrol |
Description: | A program to monitor and control your cooling devices |
Upstream URL: | https://gitlab.com/coolercontrol/coolercontrol |
Licenses: | GPL-3.0-or-later |
Conflicts: | coolercontrol |
Provides: | coolercontrol |
Submitter: | codifryed |
Maintainer: | codifryed (caferen) |
Last Packager: | caferen |
Votes: | 33 |
Popularity: | 3.22 |
First Submitted: | 2023-02-07 21:45 (UTC) |
Last Updated: | 2024-11-03 21:33 (UTC) |
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 Next › Last »
I am getting:
==> Validating source files with sha256sums...
coolercontrol-0.15.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Seems like binaries were updated while keeping the same version number
Can confirm, build works with lto enabled.
As reported the makepkg lto option can conflict with cargo's own setting in this project. I've adjusted the pkgbuild file so that this won't conflict anymore and after quite a bit of testing I've enabled full lto (previously thin lto) as the default in cargo - which will take effect on the next patch release 0.15.1. The compilation will then take a bit more time, but it looks to produce decent results for this binary.
NoXPhasma - you should now be able to enable lto again in your makepkg file without issue. (tested working with 0.15.0-3)
aha, cool you found the issue.
Sorry, I'm always using rustup, my bad, you should be fine with the rust
package then.
I do have thin lto enabled in the cargo build for a bit more optimization. I will play around with it and possibly remove that option if it helps mitigate this issue.
I've found the cause, it was because I've had lto in the /etc/makepkg.conf
enabled:
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)
Once I've disabled it (which is arch default) the build worked:
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug !lto)
Would this be a bug in coolercontrol, or is it expected?
It's the first time I try to install this AUR package, I've installed the older coolero AUR package before. I use yay -S coolercontrol
and I've done a clean build as well.
When I try to install rustup, it is in conflict with rust. So that is no option.
My desktop is cinnamon.
One option to try:
rustup toolchain install stable
to make sure your rust toolchain is completely up-to-date.
then remove, clean, and try to compile again.
Just installed it on a fresh EndeavorOS Gnome install. No issue. What desktop are you running?
Just did an update, clean, and reinstalled. No error. Did it work for you before? There might be some dev dependency missing on certain systems... I'll try it on a clean system and see if I can track it down.
Thanks for the log.
For me, the build always fails with error: linking with
ccfailed: exit status: 1
.
Full log: https://pastebin.com/5WJzUPS5
The python-starlette dependency just introduced a change that breaks compatibility with the current python-fastapi. Waiting on a fix.
A temporary workaround is to downgrade python-starlette:
pacman -U https://archive.archlinux.org/packages/p/python-starlette/python-starlette-0.23.1-1-any.pkg.tar.zst
Update this seems to be fixed now.
Pinned Comments
codifryed commented on 2024-09-22 19:02 (UTC)
With the release of 1.4.1 CoolerControl has now been spit up into several packages. This requires users to uninstall and then reinstall the application.
See: https://gitlab.com/coolercontrol/coolercontrol/-/issues/347
There's an upside, there's now a binary AUR package
coolercontrol-bin
for less compile time!codifryed commented on 2023-02-07 22:54 (UTC) (edited on 2024-01-06 23:57 (UTC) by codifryed)
Post-installation steps:
Then open the desktop application.