Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] lm_sensors should include a service
Date: Sun, 14 Aug 2022 04:14:38 +0200	[thread overview]
Message-ID: <20220814021438.DX5wAOGhuT9gV3YoAlecUy1uAF3xvrHgRpkQDEZre8c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27525@inbox.vuxu.org>

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

Closed issue by Mek101 on void-packages repository

https://github.com/void-linux/void-packages/issues/27525

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.9.16_1 x86_64-musl AuthenticAMD uptodate rFFFF
* package:  
  lm_sensors-3.6.0_1

### Expected behavior
At the end of the `sensors` setup via `sensors-detect`, the latter prints to enable the `lm_sensors` service to load the appropriate modules at boot time.

### Actual behavior
The output is:
```
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time.
You should now start the lm_sensors service to load the required kernel modules.
```
Not only the paths are wrong, but there also no sensors service under `/etc/sv/` to start

### Steps to reproduce the behavior
Run the `sensors-detect` command.


      parent reply	other threads:[~2022-08-14  2:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29  9:53 [ISSUE] lm_sensors service missing Mek101
2021-01-02  0:29 ` ericonr
2021-01-02  0:30 ` ericonr
2021-01-02  0:31 ` ericonr
2021-02-22 11:37 ` lm_sensors should include a service Mek101
2021-02-22 15:58 ` ericonr
2021-02-22 16:48 ` Mek101
2021-02-22 16:53 ` ericonr
2021-02-22 17:13 ` Mek101
2021-04-03 16:23 ` Mek101
2021-04-03 16:55 ` Mek101
2021-04-03 19:36 ` ericonr
2021-04-04  7:34 ` Mek101
2021-04-04 20:20 ` ericonr
2021-04-20 19:56 ` thegarlynch
2021-04-20 20:07 ` Mek101
2021-04-21 17:31 ` thegarlynch
2021-04-21 17:41 ` Mek101
2021-04-21 17:44 ` Mek101
2021-04-21 17:45 ` thegarlynch
2021-04-21 17:48 ` Mek101
2021-12-22 12:08 ` CatalinCsnMaster
2021-12-22 12:09 ` CatalinCsnMaster
2021-12-22 12:26 ` Mek101
2021-12-22 12:26 ` Mek101
2021-12-22 12:27 ` Mek101
2022-05-01  2:15 ` github-actions
2022-05-01 15:19 ` Mek101
2022-05-01 15:19 ` Mek101
2022-05-01 15:40 ` Mek101
2022-05-01 19:10 ` ericonr
2022-07-31  2:14 ` github-actions
2022-08-14  2:14 ` github-actions [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220814021438.DX5wAOGhuT9gV3YoAlecUy1uAF3xvrHgRpkQDEZre8c@z \
    --to=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).