Summary: | sys-apps/lm_sensors-3.1.1 init script demands config file, but runs without one | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ta2002 <throw_away_2002> |
Component: | New packages | Assignee: | Thomas Deutschmann (RETIRED) <whissi> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | polynomial-c |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ta2002
2010-03-01 00:21:41 UTC
We will drop the check as part of a requested change from bug 490502. Now in tree:
> commit 9ba6c0d353dd2ad3936fe35095588648b472f188
> Author: Thomas Deutschmann
> Date: Fri Sep 16 14:36:11 2016 +0200
>
> sys-apps/lm_sensors: Version bump to snapshot release from 2016-07-25; Package now uses module-load service
>
> Changes:
> ========
> - Based on latest unreleased changes (snapshot release from 2016-07-25;
> updated/added detection for Fintek F81768, Nuvoton NCT6793D, Microchip
> MCP9808 and Mark F71868A chips; various fixes for sensors-detect, see
> https://git.io/v6Wig for all changes)
>
> - sensors-detect now writes to "/etc/modules-load.d/lm_sensors.conf" and
> uses a config file protection mechanism like known from emerge (i.e.
> after making changes you have to call tools such as dispatch-conf,
> cfg-update or etc-update to merge the changes;
> new "--no-gentoo-config-protect" parameter will disable config file
> protection)
>
> - Due to previous change lm_service service no longer loads modules. You
> have to use mechanism your init system provides to do that (i.e. make
> sure your init system's modules-load service is enabled).
>
> - Ebuild is now multilib compatible (see bug 529684)
>
> - Runscripts no longer passes config file as argument. While this removes
> the possibility to use different configurations per default services it
> allows you to use "/etc/sensors.d" (see bug 490502 and bug 307249)
>
> - Runscripts improved in general. I.e. if you start fancontrol service
> without a valid config (so that fancontrol doesn't start and exit with
> an error) you will now know at least, that the service didn't start.
> Now you will also have reliable status functions to know service state.
>
> Gentoo-Bug: https://bugs.gentoo.org/592916
> Gentoo-Bug: https://bugs.gentoo.org/529684
> Gentoo-Bug: https://bugs.gentoo.org/490502
> Gentoo-Bug: https://bugs.gentoo.org/307249
>
> Package-Manager: portage-2.3.0
|