On Thu, 2016-02-18 at 23:29 -0800, malattia@gmail.com wrote:
> From: Mattia Dongili <malattia@linux.it>
>
> They'll eventually replace cpufrequtils and libcpufreq{0,-dev} so the
> structure of the packages is the same.
[...]
This is not passing the proper build flags:
W: libcpupower0: hardening-no-relro usr/lib/libcpupower.so.0.0.0
W: linux-cpupower: hardening-no-relro usr/bin/cpupower
W: linux-cpupower: hardening-no-relro usr/sbin/cpufreq-bench
W: linux-cpupower-dbgsym: debug-file-with-no-debug-symbols usr/lib/debug/.build-id/40/fd11393c987a84eaf7a98448d72ec8d8f87414.debug
W: libcpupower0-dbgsym: debug-file-with-no-debug-symbols usr/lib/debug/.build-id/ed/bc6af9a235be2cc306d10b33632fa4dd071a3b.debug
There are some other lintian warnings that should be easy to fix:
W: linux-cpupower: script-with-language-extension usr/bin/cpufreq-bench_plot.sh
W: linux-cpupower: manpage-has-bad-whatis-entry usr/share/man/man1/cpupower-frequency-info.1.gz
W: linux-cpupower: manpage-has-bad-whatis-entry usr/share/man/man1/cpupower-frequency-set.1.gz
W: linux-cpupower: manpage-has-bad-whatis-entry usr/share/man/man1/cpupower-idle-info.1.gz
W: linux-cpupower: manpage-has-bad-whatis-entry ... use --no-tag-display-limit to see all (or pipe to a file/program)
Ben.
Attachment:
signature.asc
Description: This is a digitally signed message part