• Bug#894906: linux-cpupower: provide a systemd service and a default con

    From Francesco Poli@21:1/5 to All on Mon Mar 10 19:40:02 2025
    XPost: linux.debian.kernel

    On Sat, 28 Dec 2024 17:52:44 +0100 Francesco Poli wrote:

    [...]
    Please, pretty please, ship the three files with the 'linux-cpupower' package, setting the systemd service disabled by default.

    Let's fix this bug once and for all!
    [...]

    Is there any chance to see the three files included in the
    'linux-cpupower' package?

    Please my previous [message], for more details.

    [message]: <https://bugs.debian.org/894906#94>


    Thanks for your time and patience.


    --
    http://www.inventati.org/frx/
    There's not a second to spare! To the laboratory! ..................................................... Francesco Poli .
    GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEygERR5zS79/7gjklPhwn4R9pv/4FAmfPLqIACgkQPhwn4R9p v/5LHw/+M0d2aOLvgQLuicoJSaWu7Tdl8k7KmK/WOD2QOAL6uunt4w6R66WJ7jcK gB9e99Zv2eE8v9ziWjXj4LgMSM6GkXEpB5LB3PKxGvlSDnLOvpZpngTN1MP7VCG2 pzcnP09ALUHtxyflH1xFXRiYQnmHFKuuwxUYY4xVReDmzhqhA3mZF7njbF9gin+C mXfrMpbtD1R6SV+vFyuunUnCEjg/DwLqthztLxTtRQHdx9lFIpYeOx8PkaiBsDmb zEloEs8AjOQAACKbz4TuQGpcbm7UzQwsh5Im0bKHjQYQUvvWUnS8QSbYzU3NTtLz XOfGFvx4NP+b/2fzmpDG2+djTw8HfZVm8OqXQmX4KGE3+tkHX5t2DD/goy+j6dMt i9Tn6i7uKneIqBz+zvdqPLGa08j+4oALw5j+JSHVp+H/qbhBorcuGQHrBSbL0S1M 1V4zKutx97he9QJkR0xqv+Zh5cgxsByrK/ZqkOrrWck+gTJV2ioN3oTw+V6XCVRV VxjISCi9XAvVWz1ejlitSE8Zj+DpKIC+1qnaFsOfearAQf3DoLRxZNmy0r5GExZx Uyy4R/wHWv4a0hu4oPVZbgLNTmzN8CfeDHFSuUKbuTOEeapi7k80fEa/rlYs07gl jJ6fNhmL1v4HDDNVA6Av59J+arhQcvQJ
  • From Salvatore Bonaccorso@21:1/5 to Francesco Poli on Mon Mar 17 21:30:02 2025
    XPost: linux.debian.kernel

    Hi Francesco,

    On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:
    On Sat, 28 Dec 2024 17:52:44 +0100 Francesco Poli wrote:

    [...]
    Please, pretty please, ship the three files with the 'linux-cpupower' package, setting the systemd service disabled by default.

    Let's fix this bug once and for all!
    [...]

    Is there any chance to see the three files included in the
    'linux-cpupower' package?

    Please my previous [message], for more details.

    [message]: <https://bugs.debian.org/894906#94>


    Thanks for your time and patience.

    Let me try to quickly summarize the status here (don't shoot the
    messenger):

    From a src:linux maintenance point of view I think we would still
    continue to decline shipping some scripts in packages produced, but
    there might be a chance we ship them if they are maintained upstream
    as examples (FWIW, this is very similar argument as it holds for which
    patches we accept to cherry-pick, only what is reviewed and accepted
    upstream and is applied in at least a upper version)

    My proposal to you would be: Do upstream the scripts as part of the tools/power/cpupower source. If they get accepted we might include them
    as part of upstream as well in the produced packages.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Poli@21:1/5 to All on Tue Mar 18 18:40:01 2025
    XPost: linux.debian.kernel

    On Mon, 17 Mar 2025 21:21:53 +0100 Salvatore Bonaccorso wrote:

    [...]
    On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:
    [...]
    Is there any chance to see the three files included in the
    'linux-cpupower' package?
    [...]
    Let me try to quickly summarize the status here (don't shoot the
    messenger):

    From a src:linux maintenance point of view I think we would still
    continue to decline shipping some scripts in packages produced, but
    there might be a chance we ship them if they are maintained upstream
    as examples (FWIW, this is very similar argument as it holds for which patches we accept to cherry-pick, only what is reviewed and accepted
    upstream and is applied in at least a upper version)

    My proposal to you would be: Do upstream the scripts as part of the tools/power/cpupower source. If they get accepted we might include them
    as part of upstream as well in the produced packages.

    Hello Salvatore,
    thanks for your followup.

    I can try, hoping that the answer won't be "this is a job for distros,
    not for upstream!"...

    Where do I start from?
    By sending a message to the [linux-pm] mailing list?

    [linux-pm]: <https://lore.kernel.org/linux-pm/>

    Please let me know, thanks for your time.


    --
    http://www.inventati.org/frx/
    There's not a second to spare! To the laboratory! ..................................................... Francesco Poli .
    GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEygERR5zS79/7gjklPhwn4R9pv/4FAmfZrRkACgkQPhwn4R9p v/7mNA//bs50DQi4bVP9Y//xR+tpCVwHxYGUYeBQrKL77uBsU5haTgdC288NsnlN 7/BT0Y+tbIA6ez0bxi1Qb9HK0/1S/YuTVzFkEbpIDpVHF5pGGj9lW18NVgG0V5W5 zWKB/wZFPQyBNqP7My3FQiOeSAW/w7DPiRT/V0KSiNta0sicoiWV8NgPYoh0v1mX 9usmlfc33e/xboVx3aeFrAIViR30pYSWCpr2WBbOBslnYXRl0VBNQ7PW6himCmfQ EsDAEkyorr/fRKhb/5U6QSkTrj2xr5JLGbG3VSeZUPpKgUe0E/zYW9/iFS7dmd5X 1TRirf/BsiiCRUBU2WV980ddFYfYZyfy7m2qDQ45nxXayFzoBNbHPOVSoF1boJIJ 357ysCyacOB6iaskiRlKie/++Icm32mlVnbbsiA90l6XoOwYNG2rNHV45zfrEhgv 98B/IobIl44zje5VjNCXZi+wVdlRHBcAsa4Z0YkWoeG7kaO7mSljUrIwamJ9OJAp Befj98GL6V8dvw0/cIIYajIlakqxhOQL8+/R6c/qniX4Qyqf3RqlahViT5K1cm7S UZr8CoxkSEzrwbijL2mhA+PpA3+7VX6jz83jpTM6ozgG8E+s0Ica4dsp/CFT4r25 oyHJewLeEg5XPN3KJWy44XGRXLILRLp6
  • From Salvatore Bonaccorso@21:1/5 to Francesco Poli on Fri Mar 21 13:30:02 2025
    XPost: linux.debian.kernel

    Hi Francesco,

    On Tue, Mar 18, 2025 at 06:27:52PM +0100, Francesco Poli wrote:
    On Mon, 17 Mar 2025 21:21:53 +0100 Salvatore Bonaccorso wrote:

    [...]
    On Mon, Mar 10, 2025 at 07:25:37PM +0100, Francesco Poli wrote:
    [...]
    Is there any chance to see the three files included in the 'linux-cpupower' package?
    [...]
    Let me try to quickly summarize the status here (don't shoot the messenger):

    From a src:linux maintenance point of view I think we would still
    continue to decline shipping some scripts in packages produced, but
    there might be a chance we ship them if they are maintained upstream
    as examples (FWIW, this is very similar argument as it holds for which patches we accept to cherry-pick, only what is reviewed and accepted upstream and is applied in at least a upper version)

    My proposal to you would be: Do upstream the scripts as part of the tools/power/cpupower source. If they get accepted we might include them
    as part of upstream as well in the produced packages.

    Hello Salvatore,
    thanks for your followup.

    I can try, hoping that the answer won't be "this is a job for distros,
    not for upstream!"...

    Where do I start from?
    By sending a message to the [linux-pm] mailing list?

    [linux-pm]: <https://lore.kernel.org/linux-pm/>

    Please let me know, thanks for your time.

    That is where I would start as well. Or more specific looking what "get_maintainer.pl" gives me:

    $ ./scripts/get_maintainer.pl ./tools/power/cpupower/
    Thomas Renninger <trenn@suse.com> (maintainer:CPU POWER MONITORING SUBSYSTEM) Shuah Khan <shuah@kernel.org> (maintainer:CPU POWER MONITORING SUBSYSTEM)
    "John B. Wyatt IV" <jwyatt@redhat.com> (maintainer:CPU POWER MONITORING SUBSYSTEM)
    John Kacur <jkacur@redhat.com> (maintainer:CPU POWER MONITORING SUBSYSTEM) linux-pm@vger.kernel.org (open list:CPU POWER MONITORING SUBSYSTEM) linux-kernel@vger.kernel.org (open list)

    That means apart from using the linux-pm mailinglist, add as well as recipients the respecive maintainers responsible.

    Hope that helps you to start, feel free to as well CC the Debian bug
    so that (or at least point out when you have started the discussion
    upstream so that we can mark the bug forwarded).

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)