From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/mime-construct/
Date: Fri, 20 Jul 2018 23:18:16 +0000 (UTC) [thread overview]
Message-ID: <1532128671.155466acb092e7788e12fa9df8e5c4e3c2dd2369.slyfox@gentoo> (raw)
commit: 155466acb092e7788e12fa9df8e5c4e3c2dd2369
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 20 23:00:12 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Jul 20 23:17:51 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=155466ac
dev-perl/mime-construct: stable 1.1100.0-r1 for ppc, bug #661196
Bug: https://bugs.gentoo.org/661196
Package-Manager: Portage-2.3.43, Repoman-2.3.10
RepoMan-Options: --include-arches="ppc"
dev-perl/mime-construct/mime-construct-1.1100.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/mime-construct/mime-construct-1.1100.0-r1.ebuild b/dev-perl/mime-construct/mime-construct-1.1100.0-r1.ebuild
index 1747742a99e..92dbf3df1f0 100644
--- a/dev-perl/mime-construct/mime-construct-1.1100.0-r1.ebuild
+++ b/dev-perl/mime-construct/mime-construct-1.1100.0-r1.ebuild
@@ -11,7 +11,7 @@ DESCRIPTION="construct and optionally mail MIME messages"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="amd64 ia64 ~ppc ~sparc x86"
+KEYWORDS="amd64 ia64 ppc ~sparc x86"
IUSE=""
RDEPEND="
next reply other threads:[~2018-07-20 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 23:18 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-19 19:40 [gentoo-commits] repo/gentoo:master commit in: dev-perl/mime-construct/ Andreas K. Hüttel
2020-04-15 9:53 Kent Fredric
2018-07-20 8:08 Sergei Trofimovich
2018-07-15 18:55 Thomas Deutschmann
2018-07-15 15:51 Mikle Kolyada
2017-01-01 11:21 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=1532128671.155466acb092e7788e12fa9df8e5c4e3c2dd2369.slyfox@gentoo \
--to=slyfox@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