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: dev-perl/DBI/
Date: Sun,  1 Jul 2018 14:01:13 +0000 (UTC)	[thread overview]
Message-ID: <1530453669.f7a5c1e3dbf289c44d7886ecea4bb3ad8ac7e0a9.zlogene@gentoo> (raw)

commit:     f7a5c1e3dbf289c44d7886ecea4bb3ad8ac7e0a9
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Jul  1 14:00:15 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Jul  1 14:01:09 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f7a5c1e3

dev-perl/DBI: mark s390 stable

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 dev-perl/DBI/DBI-1.637.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/DBI/DBI-1.637.0.ebuild b/dev-perl/DBI/DBI-1.637.0.ebuild
index 9210c18c07e..70e87656bce 100644
--- a/dev-perl/DBI/DBI-1.637.0.ebuild
+++ b/dev-perl/DBI/DBI-1.637.0.ebuild
@@ -11,7 +11,7 @@ inherit perl-module eutils
 DESCRIPTION="Database independent interface for Perl"
 
 SLOT="0"
-KEYWORDS="alpha amd64 arm arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 arm arm64 hppa ia64 ~m68k ~mips ppc ppc64 s390 ~sh sparc x86 ~ppc-aix ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-07-01 14:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 14:01 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-15 15:27 [gentoo-commits] repo/gentoo:master commit in: dev-perl/DBI/ Andreas K. Hüttel
2022-05-28 20:36 Andreas K. Hüttel
2022-05-28 19:08 Andreas K. Hüttel
2022-05-14  7:04 WANG Xuerui
2020-12-27 14:54 Fabian Groffen
2020-09-07  9:28 Kent Fredric
2020-09-06  7:49 Sergei Trofimovich
2020-08-30 18:32 Sam James
2020-08-29 18:22 Sam James
2020-08-16 14:47 Agostino Sarubbo
2020-08-15  0:20 Sam James
2020-08-14 23:08 Sam James
2020-08-12 11:43 Sam James
2020-08-12 10:01 Sam James
2020-08-12 10:01 Sam James
2020-07-09  4:48 Kent Fredric
2019-05-05 15:50 Mikle Kolyada
2019-01-11 10:03 Kent Fredric
2018-01-30  2:18 Kent Fredric
2018-01-08  0:45 Mikle Kolyada
2018-01-07 11:10 Sergei Trofimovich
2018-01-07  0:16 Sergei Trofimovich
2018-01-07  0:09 Sergei Trofimovich
2018-01-04  7:10 Sergei Trofimovich
2017-10-07 19:37 Kent Fredric
2017-02-24  4:16 Mike Frysinger
2017-01-23 18:27 Tobias Klausmann
2017-01-01 12:43 Agostino Sarubbo
2016-12-29  9:54 Michael Palimaka
2016-11-06  9:08 Kent Fredric
2016-01-24 12:11 Andreas Hüttel
2016-01-24  7:39 Jeroen Roovers
2016-01-17 18:57 Mikle Kolyada
2016-01-17 13:44 Mikle Kolyada
2016-01-12 20:17 Markus Meier
2016-01-10 10:34 Agostino Sarubbo
2016-01-06 13:34 Agostino Sarubbo
2016-01-03 14:02 Agostino Sarubbo
2016-01-03 13:57 Andreas Hüttel
2015-09-08 19:43 Andreas Hüttel

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=1530453669.f7a5c1e3dbf289c44d7886ecea4bb3ad8ac7e0a9.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