Package Details: ryzen-ppd 0.4.1-2

Git Clone URL: https://aur.archlinux.org/ryzen-ppd.git (read-only, click to copy)
Package Base: ryzen-ppd
Description: Power management daemon for AMD Ryzen Mobile processors
Upstream URL: https://github.com/xsmile/ryzen-ppd
Licenses: GPL3
Submitter: xsmile
Maintainer: xsmile
Last Packager: xsmile
Votes: 2
Popularity: 0.000000
First Submitted: 2021-07-28 15:34 (UTC)
Last Updated: 2024-05-12 14:39 (UTC)

Latest Comments

xsmile commented on 2024-05-12 14:36 (UTC)

Same here. I don't see the issue with the current Python version and the package from the official repositories anymore.

I will revert to the non git variant.

dreieck commented on 2024-05-08 22:59 (UTC) (edited on 2024-05-08 23:35 (UTC) by dreieck)

The git variant is needed due to upstream issue #138 and the package from the official repositories will not work in this case.

I tested with python-dbus-next, and I do not see any issue/ error coming up:

ryzen-ppd -v: 

[DEBUG] power_source: ac, profile: custom, update_rate_s: 4.00, platform_profile: performance
[DEBUG] monitored stapm_limit has changed: 30.0 != 28.001
[DEBUG] stapm_limit: 30000
[DEBUG] fast_limit: 30000
[DEBUG] slow_limit: 28000
[DEBUG] apu_slow_limit: 17000
[DEBUG] tctl_temp: 96
[DEBUG] apu_skin_temp_limit: 64
[...]

So it seems a "sometimes only"-issue?

(I think you mean issue #138 of python-dbus-next.)

Maybe a versioned dependency is better:

depends=('python-dbus-next>=0.2.3.r32') -- this will for now be only satisfied by python-dbus-next-git, but also by a new release of python-dbus-next, or by whatever maybe patched release somebody comes up with.

I reported by email to the maintainer of python-dbus-next about the issue and that upstream has fixed it in their git repository, but failed to provide a release, and asked if he can make a newer version of the Arch Linux package python-dbus-next based on a specific git commit.

xsmile commented on 2024-05-06 15:40 (UTC)

The git variant is needed due to upstream issue #138 and the package from the official repositories will not work in this case.

Technically you are right, though. The python-dbus-next dependency will be satisfied either way.

dreieck commented on 2024-05-06 11:45 (UTC)

Do you you really need to depend on the -git variant of python-dbus-next?

Otherwise, please change the dependency python-dbus-next-git to python-dbus-next -- so the user is not forced to use the (orphaned) -git package from the AUR but can also use the package from the official Arch Linux repositories: The user has a choice then which variant to use.

Regards!