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-portage/smart-live-rebuild/
Date: Fri,  7 Sep 2018 13:44:39 +0000 (UTC)	[thread overview]
Message-ID: <1536327851.52216403da652a2b423bf1d461e171373297fe30.zlogene@gentoo> (raw)

commit:     52216403da652a2b423bf1d461e171373297fe30
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Fri Sep  7 13:44:11 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Fri Sep  7 13:44:11 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52216403

app-portage/smart-live-rebuild: amd64 stable wrt bug #665402

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 app-portage/smart-live-rebuild/smart-live-rebuild-1.3.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-portage/smart-live-rebuild/smart-live-rebuild-1.3.6.ebuild b/app-portage/smart-live-rebuild/smart-live-rebuild-1.3.6.ebuild
index 9e516f44532..127e5c6c051 100644
--- a/app-portage/smart-live-rebuild/smart-live-rebuild-1.3.6.ebuild
+++ b/app-portage/smart-live-rebuild/smart-live-rebuild-1.3.6.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/mgorny/smart-live-rebuild/archive/v${PV}.tar.gz -> $
 
 LICENSE="BSD-2"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~mips ~x86 ~x86-fbsd"
+KEYWORDS="amd64 arm ~mips x86 ~x86-fbsd"
 IUSE=""
 
 RDEPEND=">=app-portage/gentoopm-0.2.1[${PYTHON_USEDEP}]"


             reply	other threads:[~2018-09-07 13:44 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 13:44 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 18:14 [gentoo-commits] repo/gentoo:master commit in: app-portage/smart-live-rebuild/ Michał Górny
2024-07-09 14:50 Michał Górny
2023-08-17  6:15 Sam James
2023-08-08 16:31 Sam James
2023-08-08 16:31 Sam James
2023-05-30  0:20 Sam James
2023-04-08 18:45 Michał Górny
2023-04-08 16:59 Arthur Zamarin
2023-04-02  8:15 Jakov Smolić
2023-02-19 19:55 Michał Górny
2022-12-06  0:33 Georgy Yakovlev
2022-08-10 14:20 Michał Górny
2022-06-05  7:15 Sam James
2022-06-05  6:56 Sam James
2022-03-24 21:27 Michał Górny
2022-03-24 19:03 Jakov Smolić
2022-02-02  7:25 Sam James
2022-01-24 19:19 Sam James
2021-06-04  9:55 Michał Górny
2021-03-28 12:59 Sam James
2021-03-28 12:59 Sam James
2021-03-28 12:59 Sam James
2021-03-28 12:59 Sam James
2021-02-19 16:42 Michał Górny
2021-02-19 16:11 Sam James
2021-02-19  2:54 Sam James
2021-02-19  1:51 Thomas Deutschmann
2021-01-15 12:19 Michał Górny
2021-01-07 23:19 Michał Górny
2020-09-27 16:20 Sam James
2020-05-30  7:16 Michał Górny
2020-05-30  7:16 Michał Górny
2020-02-11 11:38 Michał Górny
2019-12-05 20:58 Craig Andrews
2018-09-11  8:18 Michał Górny
2018-07-31 13:35 Michał Górny
2018-07-17 11:40 Michał Górny
2018-03-26 16:14 Michał Górny
2018-03-15 16:34 Mikle Kolyada
2018-02-01 20:37 Thomas Deutschmann
2018-01-08 22:07 Mikle Kolyada
2017-08-24 22:03 Michał Górny
2017-08-24 22:03 Michał Górny
2017-08-24 22:03 Michał Górny
2017-08-24 22:03 Michał Górny
2017-08-24 22:03 Michał Górny
2017-04-22  9:56 Pacho Ramos
2015-10-22 17:50 Mike Gilbert

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=1536327851.52216403da652a2b423bf1d461e171373297fe30.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