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: app-admin/metalog/
Date: Sat, 20 Apr 2019 18:43:12 +0000 (UTC)	[thread overview]
Message-ID: <1555785788.5aaac72e1c31b4d6dedeb0862cd32b8e7a526c31.zlogene@gentoo> (raw)

commit:     5aaac72e1c31b4d6dedeb0862cd32b8e7a526c31
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 20 18:41:42 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Apr 20 18:43:08 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5aaac72e

app-admin/metalog: arm stable wrt bug #682842

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="arm"

 app-admin/metalog/metalog-20181125.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-admin/metalog/metalog-20181125.ebuild b/app-admin/metalog/metalog-20181125.ebuild
index 3207814a7f0..86731a1f464 100644
--- a/app-admin/metalog/metalog-20181125.ebuild
+++ b/app-admin/metalog/metalog-20181125.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/hvisage/${PN}/archive/${P}.tar.gz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc x86 ~x64-cygwin ~x86-fbsd"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh sparc x86 ~x64-cygwin ~x86-fbsd"
 IUSE="unicode"
 
 RDEPEND=">=dev-libs/libpcre-3.4"


             reply	other threads:[~2019-04-20 23:30 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 18:43 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-01 20:30 [gentoo-commits] repo/gentoo:master commit in: app-admin/metalog/ Arthur Zamarin
2023-09-07 20:16 Sam James
2022-10-29 21:32 Sam James
2022-06-14  5:54 Jakov Smolić
2022-06-13 16:29 Sam James
2022-06-13  7:13 Agostino Sarubbo
2022-06-13  7:12 Agostino Sarubbo
2022-06-13  7:11 Agostino Sarubbo
2022-06-13  7:10 Agostino Sarubbo
2022-06-13  7:09 Agostino Sarubbo
2022-06-13  7:07 Agostino Sarubbo
2022-04-03  3:41 Sam James
2022-02-02 10:48 Sam James
2021-04-12  1:09 Sam James
2021-04-07 22:45 Sam James
2021-04-07 22:44 Sam James
2021-04-07 22:42 Sam James
2021-04-06 19:53 Sam James
2021-04-06 19:53 Sam James
2021-04-06 15:42 Sergei Trofimovich
2021-04-05 19:01 Thomas Deutschmann
2020-02-15 18:01 Patrick McLean
2019-05-05 18:57 Mikle Kolyada
2019-05-02 21:56 Mikle Kolyada
2019-05-02 21:56 Mikle Kolyada
2019-05-02 21:56 Mikle Kolyada
2019-04-26 20:54 Mikle Kolyada
2019-04-21 17:07 Sergei Trofimovich
2019-04-18 20:32 Thomas Deutschmann
2019-04-17 20:01 Sergei Trofimovich
2019-04-13 13:54 Mikle Kolyada
2019-04-13  5:11 Aaron Bauman
2019-02-28 14:38 Michael Haubenwallner
2018-12-20 16:17 Benda XU
2018-11-15 22:55 Patrick McLean
2018-01-11 23:27 Mike Frysinger
2017-12-17 15:06 Mikle Kolyada
2017-12-17 15:05 Mikle Kolyada
2017-11-27 19:46 Sergei Trofimovich
2017-11-23 11:54 Tobias Klausmann
2017-11-20 13:30 Manuel Rüger
2017-11-19 20:44 Sergei Trofimovich
2017-11-19 19:23 Sergei Trofimovich
2017-11-19 13:03 Sergei Trofimovich

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=1555785788.5aaac72e1c31b4d6dedeb0862cd32b8e7a526c31.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