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: net-im/bitlbee/
Date: Wed, 16 Mar 2016 11:51:21 +0000 (UTC)	[thread overview]
Message-ID: <1458129071.a6296afc86864dff3b9dd0354c57dea58ca6db3b.ago@gentoo> (raw)

commit:     a6296afc86864dff3b9dd0354c57dea58ca6db3b
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 16 11:49:10 2016 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Wed Mar 16 11:51:11 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a6296afc

net-im/bitlbee: ppc stable wrt bug #574942

Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 net-im/bitlbee/bitlbee-3.4.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net-im/bitlbee/bitlbee-3.4.1.ebuild b/net-im/bitlbee/bitlbee-3.4.1.ebuild
index 35b36e7..02ea33f 100644
--- a/net-im/bitlbee/bitlbee-3.4.1.ebuild
+++ b/net-im/bitlbee/bitlbee-3.4.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="http://get.bitlbee.org/src/${P}.tar.gz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="amd64 ~ppc ~ppc64 x86 ~x86-fbsd"
+KEYWORDS="amd64 ppc ~ppc64 x86 ~x86-fbsd"
 IUSE="debug gnutls ipv6 +xmpp libevent msn nss +oscar otr +plugins purple selinux
 	skype ssl test twitter +yahoo xinetd libressl"
 


             reply	other threads:[~2016-03-16 11:51 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 11:51 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-20  9:08 [gentoo-commits] repo/gentoo:master commit in: net-im/bitlbee/ Petr Vaněk
2024-02-20  9:08 Petr Vaněk
2022-09-30 15:24 Agostino Sarubbo
2022-09-30 15:23 Agostino Sarubbo
2022-09-30 15:22 Agostino Sarubbo
2022-08-30  8:48 Jakov Smolić
2022-08-23  5:11 Sam James
2022-08-23  5:11 Sam James
2022-08-23  5:11 Sam James
2022-08-18  7:06 Joonas Niilola
2022-07-28  7:10 Sam James
2022-07-09  9:55 Sam James
2022-06-21 16:12 Jakov Smolić
2022-02-07 20:20 Arthur Zamarin
2022-02-07 20:20 Arthur Zamarin
2022-02-07 20:20 Arthur Zamarin
2021-05-02 19:40 Mikle Kolyada
2021-04-15  8:41 Joonas Niilola
2021-03-26 15:55 Sam James
2020-09-07  8:20 Sergei Trofimovich
2020-08-22 11:26 Agostino Sarubbo
2020-08-22  5:50 Agostino Sarubbo
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:47 Joonas Niilola
2020-05-05  8:46 Joonas Niilola
2019-11-20 14:39 Joonas Niilola
2019-11-18  5:27 Tim Harder
2019-09-15 14:55 Michał Górny
2019-09-15 14:55 Michał Górny
2019-08-14 23:17 Tim Harder
2017-09-11  6:44 Tim Harder
2017-02-12 15:44 Agostino Sarubbo
2017-02-08  2:12 Michael Weber
2017-02-01 22:32 Tim Harder
2017-01-25  6:30 Tim Harder
2017-01-25  6:30 Tim Harder
2017-01-04 17:09 Agostino Sarubbo
2016-12-21 11:28 Tobias Klausmann
2016-08-07  6:52 Pacho Ramos
2016-07-03 23:01 Zac Medico
2016-03-27  1:26 Tim Harder
2016-03-27  1:26 Tim Harder
2016-03-15 15:27 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2016-01-18  3:33 Tim Harder
2016-01-18  3:17 Tim Harder
2016-01-17 22:20 Tim Harder

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=1458129071.a6296afc86864dff3b9dd0354c57dea58ca6db3b.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