public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rubyzip/
Date: Fri, 10 Mar 2017 12:53:27 +0000 (UTC)	[thread overview]
Message-ID: <1489150388.560ce727e4f9b204daab17995bf3ff96cf157449.ago@gentoo> (raw)

commit:     560ce727e4f9b204daab17995bf3ff96cf157449
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 10 12:53:08 2017 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Fri Mar 10 12:53:08 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=560ce727

dev-ruby/rubyzip: sparc stable wrt bug #611384

Package-Manager: Portage-2.3.3, Repoman-2.3.1
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 dev-ruby/rubyzip/rubyzip-1.2.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/rubyzip/rubyzip-1.2.1.ebuild b/dev-ruby/rubyzip/rubyzip-1.2.1.ebuild
index 4f6d8ef6324..bdf509b9fd9 100644
--- a/dev-ruby/rubyzip/rubyzip-1.2.1.ebuild
+++ b/dev-ruby/rubyzip/rubyzip-1.2.1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/rubyzip/rubyzip/archive/v${PV}.tar.gz -> ${P}-git.tg
 
 LICENSE="Ruby"
 SLOT="1"
-KEYWORDS="alpha amd64 arm ~hppa ~ia64 ppc ppc64 ~sparc x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 arm ~hppa ~ia64 ppc ppc64 sparc x86 ~x86-fbsd"
 IUSE=""
 
 RDEPEND=""


             reply	other threads:[~2017-03-10 12:54 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 12:53 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-05  7:30 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rubyzip/ Hans de Graaff
2024-12-31 13:58 Hans de Graaff
2023-12-27 11:23 Hans de Graaff
2023-07-14  5:46 Arthur Zamarin
2023-06-29  6:18 Sam James
2023-04-04 22:24 Sam James
2023-04-02 16:33 Sam James
2023-04-02 16:32 Sam James
2023-04-02 16:30 Sam James
2023-04-02 16:30 Sam James
2023-04-02  8:14 Jakov Smolić
2023-04-02  8:14 Jakov Smolić
2023-04-01 23:53 Sam James
2023-03-28 23:38 Sam James
2023-03-10  9:00 Arthur Zamarin
2023-03-07  3:46 WANG Xuerui
2023-03-05  8:42 Hans de Graaff
2022-07-30  8:22 Hans de Graaff
2022-04-30  9:08 Hans de Graaff
2022-03-21  7:38 Hans de Graaff
2021-12-19 12:36 Yixun Lan
2021-07-10  6:23 Hans de Graaff
2021-05-17  5:40 Hans de Graaff
2021-03-23  6:30 Hans de Graaff
2020-06-26 10:04 Sergei Trofimovich
2020-06-26  9:29 Hans de Graaff
2020-03-19 19:52 Hans de Graaff
2020-03-19 19:52 Hans de Graaff
2020-03-15  7:29 Hans de Graaff
2020-02-03 15:24 Agostino Sarubbo
2020-02-03 12:38 Agostino Sarubbo
2020-02-03 12:35 Agostino Sarubbo
2020-02-03 12:31 Agostino Sarubbo
2020-02-03 12:30 Agostino Sarubbo
2020-02-02  7:22 Hans de Graaff
2020-02-02  7:22 Hans de Graaff
2020-01-26  7:08 Hans de Graaff
2019-12-29  6:51 Hans de Graaff
2019-09-26  4:05 Hans de Graaff
2019-09-26  4:05 Hans de Graaff
2019-09-07  6:10 Hans de Graaff
2019-05-24  7:06 Hans de Graaff
2019-02-01  8:41 Hans de Graaff
2019-01-31 20:21 Markus Meier
2019-01-30 13:20 Tobias Klausmann
2019-01-24 22:22 Thomas Deutschmann
2019-01-23 20:53 Sergei Trofimovich
2019-01-22  6:16 Hans de Graaff
2019-01-21 23:31 Sergei Trofimovich
2019-01-21 23:28 Sergei Trofimovich
2019-01-20 18:43 Hans de Graaff
2018-09-01  6:59 Hans de Graaff
2018-02-07  6:30 Hans de Graaff
2017-07-29 14:32 Alexis Ballier
2017-04-02  6:22 Hans de Graaff
2017-03-11  8:31 Jeroen Roovers
2017-03-10 10:59 Agostino Sarubbo
2017-03-10  9:09 Agostino Sarubbo
2017-03-07 17:08 Michael Weber
2017-03-06 15:50 Tobias Klausmann
2017-03-05 10:25 Hans de Graaff
2017-02-09  6:03 Hans de Graaff
2017-01-04  7:02 Hans de Graaff
2016-06-04  3:50 Hans de Graaff
2016-04-03  6:56 Hans de Graaff
2016-04-03  6:56 Hans de Graaff
2016-01-15  6:41 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=1489150388.560ce727e4f9b204daab17995bf3ff96cf157449.ago@gentoo \
    --to=ago@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