------- Comment From <email address hidden> 2017-02-24 07:55 EDT-------
(In reply to comment #3)
> default desc
The 'cpupower' script in the linux-tools-common package uses command lsb_release. But the linux-tools-common package doesn't Depend on package lsb-release which provides the lsb_release command.
So on a system with linux-tools-common installed but not lsb-release:
sudo cpupower -c all frequency-set -g performance
/usr/bin/cpupower: line 32: lsb_release: command not found
WARNING: cpupower not found for kernel 4.4.0-21
linux-tools-common should probably Depends or at least Recommends lsb-release.
------- Comment From <email address hidden> 2017-02-24 07:55 EDT-------
(In reply to comment #3)
> default desc
The 'cpupower' script in the linux-tools-common package uses command lsb_release. But the linux-tools-common package doesn't Depend on package lsb-release which provides the lsb_release command.
So on a system with linux-tools-common installed but not lsb-release:
sudo cpupower -c all frequency-set -g performance
/usr/bin/cpupower: line 32: lsb_release: command not found
WARNING: cpupower not found for kernel 4.4.0-21
linux-tools-common should probably Depends or at least Recommends lsb-release.
$ grep lsb `which cpupower` `lsb_release -cs`
codename=
$ dpkg -S `which lsb_release` lsb_release
lsb-release: /usr/bin/
$ dpkg -S `which cpupower`
linux-tools-common: /usr/bin/cpupower
$ apt-cache depends linux-tools-common
linux-tools-common
Machine Type = Firestone
---Steps to Reproduce---
See description.
---uname output---
Linux dlfire5 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:09:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
---Debugger---
A debugger is not configured
default desc