public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-cpp/pangomm/
Date: Tue, 26 Feb 2019 21:19:43 +0000 (UTC)	[thread overview]
Message-ID: <1551215971.e60d96726a4880b2224d3c0c3b7c69cdf623af1b.slyfox@gentoo> (raw)

commit:     e60d96726a4880b2224d3c0c3b7c69cdf623af1b
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Tue Feb 26 20:34:14 2019 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Feb 26 21:19:31 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e60d9672

dev-cpp/pangomm: stable 2.42.0 for hppa, bug #675486

Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
RepoMan-Options: --include-arches="hppa"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 dev-cpp/pangomm/pangomm-2.42.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-cpp/pangomm/pangomm-2.42.0.ebuild b/dev-cpp/pangomm/pangomm-2.42.0.ebuild
index cfb113bdb5b..1c3dc722eea 100644
--- a/dev-cpp/pangomm/pangomm-2.42.0.ebuild
+++ b/dev-cpp/pangomm/pangomm-2.42.0.ebuild
@@ -9,7 +9,7 @@ HOMEPAGE="https://www.gtkmm.org"
 
 LICENSE="LGPL-2.1+"
 SLOT="1.4"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ppc ppc64 ~sh sparc x86 ~x86-fbsd ~amd64-linux ~x86-linux ~sparc-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm ~arm64 hppa ia64 ppc ppc64 ~sh sparc x86 ~x86-fbsd ~amd64-linux ~x86-linux ~sparc-solaris ~x86-solaris"
 IUSE="doc"
 
 COMMON_DEPEND="


             reply	other threads:[~2019-02-26 21:19 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 21:19 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-03  6:30 [gentoo-commits] repo/gentoo:master commit in: dev-cpp/pangomm/ Sam James
2022-11-12  6:01 WANG Xuerui
2022-11-05 18:58 Arthur Zamarin
2022-11-05 18:58 Arthur Zamarin
2022-11-05  9:58 Arthur Zamarin
2022-11-05  9:58 Arthur Zamarin
2022-11-05  9:44 Arthur Zamarin
2022-11-05  9:44 Arthur Zamarin
2022-10-29 23:21 Matt Turner
2022-09-24  3:43 Matt Turner
2022-09-24  3:43 Matt Turner
2022-09-24  3:43 Matt Turner
2022-04-18 20:48 Jakov Smolić
2022-03-15 20:54 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-03-09  1:31 Sam James
2022-03-09  1:09 Sam James
2022-03-09  1:09 Sam James
2022-03-08 12:32 Sam James
2022-01-22  0:37 Andreas K. Hüttel
2022-01-10 23:05 Sam James
2022-01-10 23:05 Sam James
2022-01-02 10:54 Jakov Smolić
2021-12-22  4:15 Sam James
2021-12-18  3:47 Matt Turner
2021-08-12  3:10 Yixun Lan
2021-06-02 18:08 Matt Turner
2021-06-02  6:54 Matt Turner
2021-05-31  2:19 Matt Turner
2021-05-31  2:19 Matt Turner
2021-05-22  2:27 Matt Turner
2021-04-18 17:28 Sergei Trofimovich
2021-04-13 15:00 Sam James
2021-04-12 16:02 Sam James
2021-03-23 15:05 Matt Turner
2021-03-15 18:06 Sergei Trofimovich
2021-02-16  2:12 Matt Turner
2021-02-16  2:12 Matt Turner
2020-07-29 11:23 Mart Raudsepp
2020-07-29  4:49 Sam James
2020-05-30 19:20 Sergei Trofimovich
2020-03-21 18:57 Mart Raudsepp
2019-03-30 17:39 Mart Raudsepp
2019-02-28 15:35 Mikle Kolyada
2019-02-17 21:05 Mikle Kolyada
2019-02-17 17:14 Sergei Trofimovich
2019-02-17 17:08 Sergei Trofimovich
2019-02-17 16:57 Sergei Trofimovich
2019-02-16  6:08 Mikle Kolyada
2019-02-15 15:46 Thomas Deutschmann
2019-02-14 22:09 Sergei Trofimovich
2019-01-22 12:39 Mart Raudsepp
2017-07-09 10:41 Alexis Ballier
2016-12-06 20:10 Markus Meier
2016-09-08  7:26 Gilles Dartiguelongue
2016-05-03 19:51 Markus Meier
2015-11-16 21:56 Pacho Ramos
2015-11-16 21:56 Pacho Ramos

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=1551215971.e60d96726a4880b2224d3c0c3b7c69cdf623af1b.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