Re: [PR PATCH] [Closed]: New package: cpupower-gui-1.0.0

[github-actions[bot] <github-actions[bot]@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]

There's a closed pull request on the void-packages repository

New package: cpupower-gui-1.0.0
https://github.com/void-linux/void-packages/pull/45355

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

Addresses issue #45182.

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64
  - i686
  - armv6l
  - armv6l-musl

#### Help wanted

##### Polkit testing

<details><summary>Previous problem - now fixed</summary>
<p>

I'm having lots of trouble getting an authentication agent working in my sway WM system. I would thank anyone that uses a DE (or got polkit working in a WM) to test if they can set CPU frequencies from a regular user, without having to launch the whole app as root.

</p></details>

I managed to test polkit authentication on a live VoidLinux xfce image.

##### Runit services

<details><summary>Previous problem - now fixed</summary>
<p>

I already wrote a runit service but I keep getting the following error:
```
# sv once cpupower-gui
warning: cpupower-gui: unable to open supervise/ok: file does not exist
```
I can confirm that `/var/service/cpupower-gui/supervise` is a broken symlink, even after rebooting the system. After a reboot, the service doesn't produce any effects on the CPU frequencies, so I think it's not being started.

However, `runsv` seems to work, after which I start getting a different error:
```
# sv once cpupower-gui
fail: cpupower-gui: runsv not running
```

Does anyone more knowledgeable in runit know how I can fix this? Also, I think there's no great way to port user services from systemd, but again, I'd be happy anyone more informed would be willing to help.

</p></details>

The previous problem, now fixed, happened because I accidentally messed up `/var/service`'s permissions and runit got confused. I still don't know if it is possible to **port over systemd's user services**.