public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bit-struct/
Date: Fri,  2 Feb 2018 11:25:22 +0000 (UTC)	[thread overview]
Message-ID: <1517570717.86757afbcd0799343f23e059554d39c12e4c3ce7.graaff@gentoo> (raw)

commit:     86757afbcd0799343f23e059554d39c12e4c3ce7
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Fri Feb  2 11:24:47 2018 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Fri Feb  2 11:25:17 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86757afb

dev-ruby/bit-struct: fix rubygems in metadata

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 dev-ruby/bit-struct/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/bit-struct/metadata.xml b/dev-ruby/bit-struct/metadata.xml
index e89ff7601bd..4090b848801 100644
--- a/dev-ruby/bit-struct/metadata.xml
+++ b/dev-ruby/bit-struct/metadata.xml
@@ -7,6 +7,6 @@
   </maintainer>
   <upstream>
     <remote-id type="github">vjoel/bit-struct</remote-id>
-    <remote-id type="rubygems">sshkey</remote-id>
+    <remote-id type="rubygems">bit-struct</remote-id>
   </upstream>
 </pkgmetadata>


             reply	other threads:[~2018-02-02 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 11:25 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-08  5:44 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/bit-struct/ Hans de Graaff
2021-04-25  6:19 Hans de Graaff
2020-08-23  5:42 Hans de Graaff
2019-02-03 10:49 Hans de Graaff
2018-02-02 11:25 Hans de Graaff
2018-02-02 11:25 Hans de Graaff
2017-06-06  4:57 Hans de Graaff
2016-07-29 20:39 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=1517570717.86757afbcd0799343f23e059554d39c12e4c3ce7.graaff@gentoo \
    --to=graaff@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