public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick Farina" <zerochaos@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/windows_error/
Date: Mon,  4 Mar 2024 18:33:47 +0000 (UTC)	[thread overview]
Message-ID: <1709577215.5d347aa8f37e51326f2eefb12aa85053f30dd1e5.zerochaos@gentoo> (raw)

commit:     5d347aa8f37e51326f2eefb12aa85053f30dd1e5
Author:     Rick Farina <zerochaos <AT> gentoo <DOT> org>
AuthorDate: Mon Mar  4 18:32:22 2024 +0000
Commit:     Rick Farina <zerochaos <AT> gentoo <DOT> org>
CommitDate: Mon Mar  4 18:33:35 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5d347aa8

dev-ruby/windows_error: remove myself as maintainer

Per discussion with Graaff, dropping myself as maintainer for everything
I originally added as a metasploit deps or worked on because it was a
metasploit dep. Adding ruby project where missing. Minor QA
Signed-off-by: Rick Farina <zerochaos <AT> gentoo.org>

 dev-ruby/windows_error/metadata.xml               | 6 +++---
 dev-ruby/windows_error/windows_error-0.1.5.ebuild | 3 +--
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/dev-ruby/windows_error/metadata.xml b/dev-ruby/windows_error/metadata.xml
index bc23ade9c383..32074a5c0573 100644
--- a/dev-ruby/windows_error/metadata.xml
+++ b/dev-ruby/windows_error/metadata.xml
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-	<maintainer type="person">
-		<email>zerochaos@gentoo.org</email>
-		<name>Rick Farina</name>
+	<maintainer type="project">
+		<email>ruby@gentoo.org</email>
+		<name>Gentoo Ruby Project</name>
 	</maintainer>
 	<upstream>
 		<remote-id type="github">rapid7/windows_error</remote-id>

diff --git a/dev-ruby/windows_error/windows_error-0.1.5.ebuild b/dev-ruby/windows_error/windows_error-0.1.5.ebuild
index 6976ea1af99e..fbd5690fac28 100644
--- a/dev-ruby/windows_error/windows_error-0.1.5.ebuild
+++ b/dev-ruby/windows_error/windows_error-0.1.5.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -16,7 +16,6 @@ HOMEPAGE="https://github.com/rapid7/windows_error"
 LICENSE="BSD"
 SLOT="$(ver_cut 1-2)"
 KEYWORDS="~amd64 ~arm ~x86"
-IUSE=""
 
 all_ruby_prepare() {
 	rm -f .rspec || die


             reply	other threads:[~2024-03-04 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 18:33 Rick Farina [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-31  8:05 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/windows_error/ Hans de Graaff
2023-03-10 20:29 Hans de Graaff
2023-01-25  7:30 Hans de Graaff
2022-04-02  5:56 Hans de Graaff
2022-04-02  5:56 Hans de Graaff
2022-01-16  7:34 Hans de Graaff
2021-10-17  6:04 Hans de Graaff
2021-10-17  6:04 Hans de Graaff
2020-01-19  6:52 Hans de Graaff
2019-01-14 16:36 Hans de Graaff
2018-04-12  5:49 Hans de Graaff
2018-04-12  5:49 Hans de Graaff
2017-10-04  9:09 Michał Górny
2017-05-16  5:10 Hans de Graaff
2017-05-09  3:09 Richard Farina

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=1709577215.5d347aa8f37e51326f2eefb12aa85053f30dd1e5.zerochaos@gentoo \
    --to=zerochaos@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