From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/ropper/
Date: Sun, 10 Apr 2022 17:01:04 +0000 (UTC) [thread overview]
Message-ID: <1649610029.067129a52c56a361f8dc83e4427712d331a6af5e.sam@gentoo> (raw)
commit: 067129a52c56a361f8dc83e4427712d331a6af5e
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 10 17:00:29 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 10 17:00:29 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=067129a5
dev-util/ropper: add pypi upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/ropper/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-util/ropper/metadata.xml b/dev-util/ropper/metadata.xml
index a1652b1a8756..5c40d8c11dc6 100644
--- a/dev-util/ropper/metadata.xml
+++ b/dev-util/ropper/metadata.xml
@@ -19,5 +19,6 @@
</use>
<upstream>
<remote-id type="github">sashs/Ropper</remote-id>
+ <remote-id type="pypi">ropper</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2022-04-10 17:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 17:01 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 16:48 [gentoo-commits] repo/gentoo:master commit in: dev-util/ropper/ Sam James
2025-04-28 14:01 Sam James
2025-03-28 15:22 Sam James
2025-03-28 15:22 Sam James
2024-10-03 9:47 Sam James
2024-07-01 16:47 Sam James
2024-07-01 16:47 Sam James
2024-06-01 3:07 Sam James
2024-06-01 3:07 Sam James
2024-01-14 4:53 Sam James
2023-04-14 19:43 Sam James
2023-04-14 4:04 Sam James
2023-02-25 5:47 Arthur Zamarin
2023-01-14 10:00 Arthur Zamarin
2023-01-10 4:13 Sam James
2023-01-05 5:21 Sam James
2023-01-05 0:19 Sam James
2023-01-05 0:19 Sam James
2022-08-23 5:30 Sam James
2022-08-23 5:30 Sam James
2022-04-17 16:44 Sam James
2022-04-05 3:08 Sam James
2022-01-28 8:22 Sam James
2022-01-28 5:18 Sam James
2022-01-28 5:18 Sam James
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=1649610029.067129a52c56a361f8dc83e4427712d331a6af5e.sam@gentoo \
--to=sam@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