From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sass-rails/
Date: Wed, 18 May 2016 08:56:00 +0000 (UTC) [thread overview]
Message-ID: <1463561744.e06e863ce75c0f21a9546b3c0e33ddf291aacfb6.grobian@gentoo> (raw)
commit: e06e863ce75c0f21a9546b3c0e33ddf291aacfb6
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Wed May 18 08:55:44 2016 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Wed May 18 08:55:44 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e06e863c
dev-ruby/sass-rails: marked ~amd64-linux
Package-Manager: portage-2.2.28
dev-ruby/sass-rails/sass-rails-3.2.6.ebuild | 2 +-
dev-ruby/sass-rails/sass-rails-5.0.4-r1.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-ruby/sass-rails/sass-rails-3.2.6.ebuild b/dev-ruby/sass-rails/sass-rails-3.2.6.ebuild
index 3a2cecf..39ab5ff 100644
--- a/dev-ruby/sass-rails/sass-rails-3.2.6.ebuild
+++ b/dev-ruby/sass-rails/sass-rails-3.2.6.ebuild
@@ -15,7 +15,7 @@ HOMEPAGE="https://github.com/rails/sass-rails"
LICENSE="MIT"
SLOT="3.2"
-KEYWORDS="~amd64 ~arm ~x86 ~x64-macos ~x86-solaris"
+KEYWORDS="~amd64 ~arm ~x86 ~amd64-linux ~x64-macos ~x86-solaris"
IUSE=""
diff --git a/dev-ruby/sass-rails/sass-rails-5.0.4-r1.ebuild b/dev-ruby/sass-rails/sass-rails-5.0.4-r1.ebuild
index 0e7e1a7..75ebe18 100644
--- a/dev-ruby/sass-rails/sass-rails-5.0.4-r1.ebuild
+++ b/dev-ruby/sass-rails/sass-rails-5.0.4-r1.ebuild
@@ -16,7 +16,7 @@ SRC_URI="https://github.com/rails/sass-rails/archive/v${PV}.tar.gz -> ${P}.tar.g
LICENSE="MIT"
SLOT="$(get_version_component_range 1-2)"
-KEYWORDS="~amd64 ~arm ~x86"
+KEYWORDS="~amd64 ~arm ~x86 ~amd64-linux"
IUSE=""
next reply other threads:[~2016-05-18 8:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 8:56 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-18 6:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/sass-rails/ Hans de Graaff
2023-08-30 5:25 Hans de Graaff
2023-07-10 7:36 Hans de Graaff
2023-04-15 7:28 Hans de Graaff
2023-04-08 7:04 Hans de Graaff
2023-04-07 18:11 Sam James
2023-03-29 14:36 Sam James
2023-03-29 13:04 Sam James
2022-05-15 7:50 Hans de Graaff
2021-07-06 19:41 Hans de Graaff
2020-07-26 5:52 Hans de Graaff
2019-10-13 6:38 Hans de Graaff
2019-08-17 5:44 Hans de Graaff
2019-05-06 17:58 Hans de Graaff
2018-05-19 7:51 Hans de Graaff
2018-03-25 17:58 Sergei Trofimovich
2018-03-18 12:57 Sergei Trofimovich
2018-02-24 8:49 Hans de Graaff
2018-02-07 5:52 Thomas Deutschmann
2018-01-24 7:02 Hans de Graaff
2017-12-09 7:55 Hans de Graaff
2017-11-16 7:05 Hans de Graaff
2017-08-24 5:49 Hans de Graaff
2017-07-03 9:12 Alexis Ballier
2017-07-02 5:43 Hans de Graaff
2017-06-02 5:38 Hans de Graaff
2017-05-03 19:03 Hans de Graaff
2017-05-03 18:30 Hans de Graaff
2017-02-25 8:19 Hans de Graaff
2016-07-23 8:15 Hans de Graaff
2016-07-18 6:49 Hans de Graaff
2016-07-11 5:20 Hans de Graaff
2016-07-06 5:33 Hans de Graaff
2016-07-06 5:33 Hans de Graaff
2016-04-16 13:08 Manuel RĂ¼ger
2016-02-16 21:14 Hans de Graaff
2016-01-17 9:10 Hans de Graaff
2015-09-04 5:07 Hans de Graaff
2015-09-04 5:07 Hans de Graaff
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=1463561744.e06e863ce75c0f21a9546b3c0e33ddf291aacfb6.grobian@gentoo \
--to=grobian@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