Comment 2 for bug 1914774

so, this is very weird.

We used to install binary "cpupower" from linux-tools via this package for the hwe kernel:

linux-tools-generic-hwe-18.04

but this seems to have changed somewhere in between, the file list on packages.ubuntu.com

only lists:

/usr/share/doc/linux-tools-generic-hwe-18.04/changelog.gz
/usr/share/doc/linux-tools-generic-hwe-18.04/copyright

see, e.g.:
https://packages.ubuntu.com/bionic-updates/amd64/linux-tools-generic-hwe-18.04/filelist
linked from:
https://packages.ubuntu.com/bionic-updates/linux-tools-generic-hwe-18.04

I believe this is, because it's a meta/virtual package?

nevertheless I found how to install "cpupower" it seems it moved to the following package (adjust kernel subversion as needed):

https://packages.ubuntu.com/bionic-updates/linux-hwe-5.4-tools-5.4.0-80

but this is also strange for several reasons:

first, afaik you need to install the version for your specific installed kernel, but the package name leads to bad sed-magic in install scripts like:

apt install linux-hwe-5.4-tools-$(uname -r | sed 's#-generic$##')

this is obviously bad, but I could live with that.

what is really really weird though, is the installation path of the cpupower binary:

root@server:~# /usr/lib/linux-hwe-5.4-tools-5.4.0-104/cpupower --help
Usage: cpupower [-d|--debug] [-c|--cpu cpulist ] <command> [<args>]
Supported commands are:
        frequency-info
        frequency-set
        idle-info
        idle-set
        set
        info
        monitor
        help

Not all commands can make use of the -c cpulist option.

Use 'cpupower help <command>' for getting help for above commands.

root@server:~# type cpupower
-su: type: cpupower: not found

it is not installed in $PATH at all, which is really contracdicting the upstream makefile, imho?

see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/power/cpupower/Makefile

am I holding it wrong? is there another package which installs cpupower in the correct path?

why was the packaging changed, mid release? This breaks every workflow around the provided tools.