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: virtual/perl-Thread-Queue/
Date: Sun,  6 Jan 2019 10:33:27 +0000 (UTC)	[thread overview]
Message-ID: <1546770690.f37b113a0a62dad8fb09aae68157aa593479db32.zlogene@gentoo> (raw)

commit:     f37b113a0a62dad8fb09aae68157aa593479db32
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Jan  6 10:31:30 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Jan  6 10:31:30 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f37b113a

virtual/perl-Thread-Queue: s390 stable wrt bug #673542

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

 virtual/perl-Thread-Queue/perl-Thread-Queue-3.120.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/perl-Thread-Queue/perl-Thread-Queue-3.120.0-r1.ebuild b/virtual/perl-Thread-Queue/perl-Thread-Queue-3.120.0-r1.ebuild
index b2ae200d07c..8088c052bfa 100644
--- a/virtual/perl-Thread-Queue/perl-Thread-Queue-3.120.0-r1.ebuild
+++ b/virtual/perl-Thread-Queue/perl-Thread-Queue-3.120.0-r1.ebuild
@@ -5,7 +5,7 @@ EAPI=6
 
 DESCRIPTION="Virtual for ${PN#perl-}"
 SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ppc ppc64 sh sparc x86 ~x64-cygwin"
+KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ppc ppc64 s390 sh sparc x86 ~x64-cygwin"
 
 RDEPEND="
 	|| ( =dev-lang/perl-5.28* =dev-lang/perl-5.26* ~perl-core/${PN#perl-}-${PV} )


             reply	other threads:[~2019-01-06 10:33 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 10:33 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-26 20:02 [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Thread-Queue/ Andreas K. Hüttel
2023-06-03 16:31 Andreas K. Hüttel
2023-04-22 13:01 Sam James
2022-05-25 21:16 Andreas K. Hüttel
2021-08-06 20:25 Andreas K. Hüttel
2021-05-26  8:13 Sam James
2021-05-24  5:47 Sam James
2021-05-24  5:07 Sam James
2021-05-24  4:42 Sam James
2021-05-24  3:27 Sam James
2021-05-24  2:04 Sam James
2021-05-20  3:21 Sam James
2021-02-03  2:53 Sam James
2021-02-03  2:53 Sam James
2020-08-07 16:01 Andreas K. Hüttel
2019-12-07 16:55 Aaron Bauman
2019-12-06 10:00 Mikle Kolyada
2019-12-06  9:56 Mikle Kolyada
2019-12-06  9:53 Mikle Kolyada
2019-12-06  9:51 Mikle Kolyada
2019-12-06  9:49 Mikle Kolyada
2019-12-06  9:46 Mikle Kolyada
2019-12-06  9:43 Mikle Kolyada
2019-12-06  9:41 Mikle Kolyada
2019-12-06  9:37 Mikle Kolyada
2019-12-06  9:34 Mikle Kolyada
2019-05-17 20:08 Andreas K. Hüttel
2019-02-16  8:46 Mikle Kolyada
2019-01-06 11:34 Mikle Kolyada
2019-01-06 10:23 Mikle Kolyada
2019-01-06 10:14 Mikle Kolyada
2019-01-06  8:32 Sergei Trofimovich
2019-01-05 20:46 Matt Turner
2019-01-05 12:30 Mikle Kolyada
2019-01-05  8:00 Mikle Kolyada
2019-01-04 13:47 Mikle Kolyada
2017-05-30 22:21 Sergei Trofimovich
2017-04-28 13:14 Agostino Sarubbo
2017-04-24 12:44 Tobias Klausmann
2017-04-16  8:07 Jeroen Roovers
2017-04-15 11:25 Agostino Sarubbo
2017-04-15 11:20 Agostino Sarubbo
2017-04-05 21:29 Michael Weber
2016-12-17  7:01 Markus Meier

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=1546770690.f37b113a0a62dad8fb09aae68157aa593479db32.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