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: net-libs/libmbim/
Date: Wed,  5 Dec 2018 07:34:13 +0000 (UTC)	[thread overview]
Message-ID: <1543995220.1713ba46c70a7ba7b6b3545781e5eb8060ed80b2.zlogene@gentoo> (raw)

commit:     1713ba46c70a7ba7b6b3545781e5eb8060ed80b2
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Wed Dec  5 07:20:29 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Wed Dec  5 07:33:40 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1713ba46

net-libs/libmbim: ppc stable wrt bug #670024

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

 net-libs/libmbim/libmbim-1.16.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-libs/libmbim/libmbim-1.16.2.ebuild b/net-libs/libmbim/libmbim-1.16.2.ebuild
index ed8e6fea370..b2159d5d442 100644
--- a/net-libs/libmbim/libmbim-1.16.2.ebuild
+++ b/net-libs/libmbim/libmbim-1.16.2.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://www.freedesktop.org/software/libmbim/${P}.tar.xz"
 
 LICENSE="LGPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~mips ~ppc ppc64 x86"
+KEYWORDS="~alpha amd64 arm ~arm64 ~mips ppc ppc64 x86"
 IUSE="static-libs udev"
 
 RDEPEND=">=dev-libs/glib-2.32:2


             reply	other threads:[~2018-12-05  7:34 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  7:34 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-09  8:23 [gentoo-commits] repo/gentoo:master commit in: net-libs/libmbim/ Sam James
2024-10-08 18:12 Sam James
2024-10-07  2:52 Sam James
2024-05-31  8:02 Andreas Sturmlechner
2024-05-29 11:48 Sam James
2023-07-30 20:45 Ionen Wolkens
2023-07-29 11:51 Pacho Ramos
2023-07-09 12:29 Matt Turner
2022-10-31 14:28 Matt Turner
2022-10-29 17:44 Matt Turner
2022-05-31  9:24 Jakov Smolić
2022-05-28  5:05 Sam James
2022-05-24 11:14 WANG Xuerui
2022-04-28 15:31 Matt Turner
2022-01-24 22:43 Matt Turner
2022-01-24 14:49 Sam James
2022-01-24 14:46 Sam James
2022-01-24  3:39 Sam James
2022-01-20 10:02 Jakov Smolić
2022-01-20  9:42 Arthur Zamarin
2021-12-19  2:00 Matt Turner
2021-11-08  7:45 Sam James
2021-11-06  3:58 Sam James
2021-10-04  1:24 Sam James
2021-08-08 19:46 Marek Szuba
2021-08-04 21:57 Matt Turner
2021-07-26  7:15 Matt Turner
2021-07-24 17:08 Sam James
2021-07-11 20:48 Sam James
2021-07-11  2:31 Sam James
2021-07-10 15:40 Sam James
2021-06-06 21:49 Matt Turner
2021-05-29 15:27 Sam James
2021-05-28 19:20 Sam James
2021-05-28 19:11 Sam James
2021-04-13 16:20 Matt Turner
2021-04-12 22:12 Sam James
2021-04-12 22:12 Sam James
2021-03-30  3:19 Matt Turner
2021-03-21 14:28 Matt Turner
2021-03-12 15:28 Sam James
2021-03-12  8:04 Mikle Kolyada
2021-03-11  2:35 Sam James
2021-01-08  2:46 Matt Turner
2021-01-08  2:34 Matt Turner
2020-09-24 19:53 Aaron Bauman
2019-12-08  5:32 Matt Turner
2019-11-28 10:57 Agostino Sarubbo
2019-11-28 10:55 Agostino Sarubbo
2019-11-26 20:11 Aaron Bauman
2019-11-26 12:27 Agostino Sarubbo
2019-11-26  0:58 Thomas Deutschmann
2019-05-21  3:17 Aaron Bauman
2019-04-01 12:29 Tony Vroon
2019-04-01 12:06 Tony Vroon
2018-12-04 16:27 Mikle Kolyada
2018-11-06  7:41 Mikle Kolyada
2018-11-04 19:14 Thomas Deutschmann
2018-08-22 14:56 Tony Vroon
2017-06-26  7:56 Alexis Ballier
2017-03-31 12:56 Michael Weber
2017-03-31 10:20 Michael Weber
2017-02-17  5:57 Markus Meier
2017-01-24 11:46 Agostino Sarubbo
2017-01-19  3:31 Mike Frysinger
2016-12-21 18:56 Tobias Klausmann
2016-11-15 18:24 Mike Frysinger
2016-09-17 14:09 Tony Vroon
2016-03-31 13:31 Tony Vroon
2016-03-31 11:27 Alexey Shvetsov
2015-11-09  4:58 Jeroen Roovers
2015-10-05  5:26 Jeroen Roovers

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=1543995220.1713ba46c70a7ba7b6b3545781e5eb8060ed80b2.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