public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/hamlib/
Date: Tue, 27 Nov 2018 21:55:48 +0000 (UTC)	[thread overview]
Message-ID: <1543355712.f6073e44b944a0772ae56f433ed1af4da2761cae.whissi@gentoo> (raw)

commit:     f6073e44b944a0772ae56f433ed1af4da2761cae
Author:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 27 21:42:24 2018 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Tue Nov 27 21:55:12 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6073e44

media-libs/hamlib: x86 stable (bug #672074)

Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 media-libs/hamlib/hamlib-3.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-libs/hamlib/hamlib-3.3.ebuild b/media-libs/hamlib/hamlib-3.3.ebuild
index fc21384c733..81acd1872d2 100644
--- a/media-libs/hamlib/hamlib-3.3.ebuild
+++ b/media-libs/hamlib/hamlib-3.3.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://www.github.com/${PN}/${PN}/releases/download/${PVR}/${P}.tar.gz
 
 LICENSE="LGPL-2 GPL-2"
 SLOT="0"
-KEYWORDS="~amd64 ~x86 ~x86-fbsd"
+KEYWORDS="~amd64 x86 ~x86-fbsd"
 IUSE="doc perl python tcl"
 
 RESTRICT="test"


             reply	other threads:[~2018-11-27 21:55 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 21:55 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-29  7:08 [gentoo-commits] repo/gentoo:master commit in: media-libs/hamlib/ Thomas Beierlein
2024-04-14 13:31 Thomas Beierlein
2024-03-14 19:21 Sam James
2024-03-14 19:21 Sam James
2024-01-16  8:48 Thomas Beierlein
2024-01-15 18:18 Sam James
2024-01-15 18:18 Sam James
2023-08-15 22:42 Conrad Kostecki
2023-08-15 22:42 Conrad Kostecki
2023-07-30  7:46 Thomas Beierlein
2023-06-10 13:35 Sam James
2023-06-10 13:35 Sam James
2023-04-16 15:23 Thomas Beierlein
2023-02-16 10:01 Sam James
2023-02-16 10:01 Sam James
2023-01-13 18:11 Thomas Beierlein
2023-01-03 15:21 Thomas Beierlein
2023-01-03 15:21 Thomas Beierlein
2023-01-02 16:37 Thomas Beierlein
2022-12-21 13:16 Thomas Beierlein
2022-11-27  9:13 Thomas Beierlein
2022-11-17  7:09 Thomas Beierlein
2022-05-08 11:30 Thomas Beierlein
2022-04-17 18:35 Arthur Zamarin
2022-04-12 21:18 Jakov Smolić
2022-04-12 18:44 Arthur Zamarin
2022-01-29 18:50 Sam James
2022-01-29 18:50 Sam James
2021-12-07  6:50 Thomas Beierlein
2021-12-04  8:34 Thomas Beierlein
2021-12-03 17:58 Thomas Beierlein
2021-11-11 18:55 Jakov Smolić
2021-11-11 17:57 Jakov Smolić
2021-09-18 14:51 Thomas Beierlein
2021-09-18 14:51 Thomas Beierlein
2021-08-05 14:08 Sam James
2021-08-03 12:35 Agostino Sarubbo
2021-06-24  5:46 Thomas Beierlein
2021-05-26 17:02 Thomas Beierlein
2021-04-22 12:11 Sam James
2021-04-22 12:08 Sam James
2021-03-11 14:39 Thomas Beierlein
2021-03-11 14:39 Thomas Beierlein
2021-02-06 12:19 Thomas Beierlein
2020-12-29 17:56 Thomas Beierlein
2020-12-16 19:11 Thomas Beierlein
2020-12-04 17:23 Thomas Beierlein
2020-12-02 14:24 Mikle Kolyada
2020-11-18 19:33 Thomas Beierlein
2020-10-05 16:14 Thomas Beierlein
2020-09-08  5:55 Thomas Beierlein
2020-05-07 15:17 Michał Górny
2020-03-25 14:15 Thomas Beierlein
2020-03-18 20:36 Rick Farina
2018-12-13 14:23 Mikle Kolyada
2018-09-30 18:56 Thomas Beierlein
2018-07-09 13:54 Mikle Kolyada
2018-07-06 13:43 Thomas Deutschmann
2018-04-02  8:39 Thomas Beierlein
2018-01-09 17:56 Thomas Beierlein
2017-03-11 19:15 Thomas Beierlein
2017-03-11 19:15 Thomas Beierlein
2017-02-12 15:30 Agostino Sarubbo
2017-01-03 10:16 Thomas Beierlein
2016-01-07 16:38 Thomas Beierlein
2016-01-06 13:34 Agostino Sarubbo
2016-01-02 16:28 Agostino Sarubbo
2015-09-19 16:42 Thomas Beierlein

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=1543355712.f6073e44b944a0772ae56f433ed1af4da2761cae.whissi@gentoo \
    --to=whissi@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