public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/lm_sensors/
Date: Tue,  9 Oct 2018 08:40:51 +0000 (UTC)	[thread overview]
Message-ID: <1539074407.9596b35686a81b8e2bd883604c11696893752615.zlogene@gentoo> (raw)

commit:     9596b35686a81b8e2bd883604c11696893752615
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Tue Oct  9 08:40:07 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Tue Oct  9 08:40:07 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9596b356

sys-apps/lm_sensors: amd64 stable wrt bug #668094

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11

 sys-apps/lm_sensors/lm_sensors-3.4.0_p20180923.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/lm_sensors/lm_sensors-3.4.0_p20180923.ebuild b/sys-apps/lm_sensors/lm_sensors-3.4.0_p20180923.ebuild
index 65e82e0df66..1079358ad8d 100644
--- a/sys-apps/lm_sensors/lm_sensors-3.4.0_p20180923.ebuild
+++ b/sys-apps/lm_sensors/lm_sensors-3.4.0_p20180923.ebuild
@@ -19,7 +19,7 @@ LICENSE="GPL-2+ LGPL-2.1"
 # SUBSLOT based on SONAME of libsensors.so
 SLOT="0/4.4.0"
 
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~mips ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~mips ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux"
 IUSE="contrib sensord static-libs"
 
 COMMON_DEPS="


             reply	other threads:[~2018-10-09  8:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09  8:40 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-12 14:28 [gentoo-commits] repo/gentoo:master commit in: sys-apps/lm_sensors/ Michał Górny
2019-04-21  1:38 Lars Wendler
2019-04-20 17:57 Mikle Kolyada
2019-02-22 12:04 Mikle Kolyada
2019-02-13 10:59 Mikle Kolyada
2019-02-12 21:03 Sergei Trofimovich
2019-02-10  9:32 Sergei Trofimovich
2019-02-09 19:35 Sergei Trofimovich
2019-02-09 18:36 Thomas Deutschmann
2018-11-28 12:50 Lars Wendler
2018-11-11 22:37 Thomas Deutschmann
2018-11-11 11:18 Mikle Kolyada
2018-10-15 18:43 Sergei Trofimovich
2018-10-13  6:56 Tobias Klausmann
2018-10-12 19:08 Sergei Trofimovich
2018-10-09 21:24 Thomas Deutschmann
2018-10-09  5:12 Matt Turner
2018-10-09  5:12 Matt Turner
2018-09-26 22:49 Thomas Deutschmann
2018-09-26 22:49 Thomas Deutschmann
2018-08-24  1:10 Thomas Deutschmann
2018-08-03  1:19 Thomas Deutschmann
2018-04-16 12:53 Thomas Deutschmann
2018-04-16 12:53 Thomas Deutschmann
2018-04-13 23:22 Aaron Bauman
2018-03-15 16:03 Mikle Kolyada
2018-03-03 13:12 Tobias Klausmann
2018-01-06 14:25 Sergei Trofimovich
2018-01-03 19:51 Sergei Trofimovich
2018-01-02 23:34 Mikle Kolyada
2017-10-03 15:03 Thomas Deutschmann
2017-10-03 14:25 Thomas Deutschmann
2017-06-19 20:07 Alexis Ballier
2017-01-08 18:19 Markus Meier
2016-12-20 12:37 Thomas Deutschmann
2016-12-17  8:54 Aaron Bauman
2016-11-24  9:50 Tobias Klausmann
2015-09-24 10:36 Agostino Sarubbo
2015-09-20  8:44 Jeroen Roovers
2015-09-06 12:42 Agostino Sarubbo

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=1539074407.9596b35686a81b8e2bd883604c11696893752615.zlogene@gentoo \
    --to=zlogene@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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