public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/libsigrok/
Date: Tue, 10 Jan 2017 14:55:59 +0000 (UTC)	[thread overview]
Message-ID: <1484059985.e62fd5ee3d38f1232749054ee8aee9f1b74ede49.ago@gentoo> (raw)

commit:     e62fd5ee3d38f1232749054ee8aee9f1b74ede49
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 10 14:53:05 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Jan 10 14:53:05 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e62fd5ee

sci-libs/libsigrok: amd64 stable wrt bug #601152

Package-Manager: portage-2.3.0
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 sci-libs/libsigrok/libsigrok-0.3.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sci-libs/libsigrok/libsigrok-0.3.0.ebuild b/sci-libs/libsigrok/libsigrok-0.3.0.ebuild
index 014ca61..ab4dab2 100644
--- a/sci-libs/libsigrok/libsigrok-0.3.0.ebuild
+++ b/sci-libs/libsigrok/libsigrok-0.3.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -11,7 +11,7 @@ if [[ ${PV} == "9999" ]]; then
 	inherit git-r3 autotools
 else
 	SRC_URI="http://sigrok.org/download/source/${PN}/${P}.tar.gz"
-	KEYWORDS="~amd64 ~x86"
+	KEYWORDS="amd64 ~x86"
 fi
 
 DESCRIPTION="provide basic hardware drivers for logic analyzers and input/output file format support"


             reply	other threads:[~2017-01-10 14:56 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 14:55 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-31 19:27 [gentoo-commits] repo/gentoo:master commit in: sci-libs/libsigrok/ Sven Wegener
2024-08-31 16:00 Sven Wegener
2024-07-14  8:06 Viorel Munteanu
2024-07-14  8:06 Viorel Munteanu
2024-07-13 15:31 Arthur Zamarin
2024-06-11 20:45 Sam James
2024-06-11 17:58 Sam James
2024-06-11 17:17 Sam James
2024-06-11 17:17 Sam James
2023-02-26 20:03 Sven Wegener
2023-02-26 20:03 Sven Wegener
2023-02-26 20:03 Sven Wegener
2023-02-26 20:03 Sven Wegener
2022-08-27  8:03 Sam James
2022-06-22 18:37 Arthur Zamarin
2022-06-22 16:02 Arthur Zamarin
2022-06-07  7:59 Joonas Niilola
2022-06-07  6:34 Joonas Niilola
2022-05-01  7:28 Sven Wegener
2022-01-08 15:47 Sven Wegener
2022-01-08 15:47 Sven Wegener
2022-01-08 15:47 Sven Wegener
2021-07-02  8:22 Joonas Niilola
2021-04-19 20:54 Sam James
2021-02-19 19:32 Thomas Deutschmann
2021-02-18  7:23 Sam James
2020-11-16 22:31 Sven Wegener
2020-11-16 22:31 Sven Wegener
2020-11-16 22:31 Sven Wegener
2020-11-16 22:31 Sven Wegener
2020-07-06 18:16 Andreas Sturmlechner
2020-07-06 18:16 Andreas Sturmlechner
2020-07-06 18:16 Andreas Sturmlechner
2020-07-06 18:16 Andreas Sturmlechner
2020-07-06 18:16 Andreas Sturmlechner
2020-02-09 16:36 Michał Górny
2020-01-16  6:39 Michał Górny
2019-12-31 15:13 Sven Wegener
2019-12-31 15:13 Sven Wegener
2019-04-12 17:30 Sven Wegener
2019-04-12 15:45 Sven Wegener
2019-04-12 15:45 Sven Wegener
2018-12-08 21:34 Sven Wegener
2018-11-03 11:03 Sven Wegener
2018-10-11  7:24 Sven Wegener
2018-10-11  7:13 Sven Wegener
2018-04-11  9:40 David Seifert
2017-12-10 16:11 Sven Wegener
2017-12-10 16:11 Sven Wegener
2017-12-10 16:11 Sven Wegener
2017-11-07 22:13 Sven Wegener
2017-07-01 20:52 Sven Wegener
2017-03-22 21:13 Thomas Deutschmann
2016-08-03 11:41 Sven Wegener
2016-08-03 11:41 Sven Wegener
2016-08-03 11:41 Sven Wegener
2016-08-03 11:41 Sven Wegener
2016-01-10 11:17 Sven Wegener
2016-01-10  9:59 Sven Wegener
2015-12-19 17:15 Sven Wegener
2015-12-19 17:15 Sven Wegener
2015-12-19 17:14 Sven Wegener
2015-12-19 17:14 Sven Wegener
2015-12-19 17:14 Sven Wegener

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=1484059985.e62fd5ee3d38f1232749054ee8aee9f1b74ede49.ago@gentoo \
    --to=ago@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