public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/daemons/
Date: Sat, 21 Jan 2023 12:21:26 +0000 (UTC)	[thread overview]
Message-ID: <1674303665.151a4f62b1c1e946bfb2f112549c7086878c4b95.arthurzam@gentoo> (raw)

commit:     151a4f62b1c1e946bfb2f112549c7086878c4b95
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 21 12:21:05 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 21 12:21:05 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=151a4f62

dev-ruby/daemons: Stabilize 1.4.1 ppc, #891583

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-ruby/daemons/daemons-1.4.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/daemons/daemons-1.4.1.ebuild b/dev-ruby/daemons/daemons-1.4.1.ebuild
index cd9217be1d55..790dd4ed241e 100644
--- a/dev-ruby/daemons/daemons-1.4.1.ebuild
+++ b/dev-ruby/daemons/daemons-1.4.1.ebuild
@@ -18,7 +18,7 @@ SRC_URI="https://github.com/thuehlinger/daemons/archive/v${PV}.tar.gz -> ${P}.ta
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~hppa ~ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x86-solaris"
+KEYWORDS="~alpha ~amd64 arm ~hppa ppc ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris ~x86-solaris"
 IUSE="examples"
 
 all_ruby_prepare() {


             reply	other threads:[~2023-01-21 12:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21 12:21 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-31 19:35 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/daemons/ Hans de Graaff
2023-03-12 12:09 Hans de Graaff
2023-01-29 15:40 Hans de Graaff
2023-01-21 16:53 Sam James
2023-01-21 16:53 Sam James
2023-01-21 12:21 Arthur Zamarin
2023-01-21 12:21 Arthur Zamarin
2022-05-06 10:04 Hans de Graaff
2021-08-27  6:46 Hans de Graaff
2021-05-05  5:05 Hans de Graaff
2020-06-20  5:41 Hans de Graaff
2020-06-19  6:40 Sergei Trofimovich
2020-06-15 15:03 Agostino Sarubbo
2020-06-14 20:19 Sergei Trofimovich
2020-06-14 20:08 Sergei Trofimovich
2020-02-23  6:04 Hans de Graaff
2019-11-16  9:36 Hans de Graaff
2019-02-02 17:17 Hans de Graaff
2018-12-15  6:31 Hans de Graaff
2018-12-11  7:07 Hans de Graaff
2018-04-29  5:58 Hans de Graaff
2018-04-26  4:57 Hans de Graaff
2018-04-26  4:21 Matt Turner
2018-04-15  5:38 Hans de Graaff
2018-03-25 17:18 Markus Meier
2018-03-21  2:43 Matt Turner
2018-02-25  6:47 Hans de Graaff
2018-02-18 17:56 Sergei Trofimovich
2018-01-24 16:11 Hans de Graaff
2018-01-24 16:11 Hans de Graaff
2017-12-25  6:50 Hans de Graaff
2017-10-23  5:20 Hans de Graaff
2017-06-20  5:00 Hans de Graaff
2016-12-11 18:15 Hans de Graaff
2016-11-13 11:28 Hans de Graaff
2016-08-03  6:19 Hans de Graaff
2015-11-08  7:13 Hans de Graaff
2015-11-07 23:15 Mikle Kolyada
2015-11-03 19:14 Markus Meier
2015-10-04 10:24 Jeroen Roovers
2015-09-30 13:43 Agostino Sarubbo
2015-09-30  3:51 Jeroen Roovers
2015-09-29 10:18 Agostino Sarubbo
2015-09-29  5:36 Hans de Graaff

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=1674303665.151a4f62b1c1e946bfb2f112549c7086878c4b95.arthurzam@gentoo \
    --to=arthurzam@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