From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/rutorrent/
Date: Tue, 30 Jan 2024 05:37:55 +0000 (UTC) [thread overview]
Message-ID: <1706592790.46d1100ce26435a9a6836f397ee6ae52b37a643c.ceamac@gentoo> (raw)
commit: 46d1100ce26435a9a6836f397ee6ae52b37a643c
Author: Henning Schild <henning <AT> hennsch <DOT> de>
AuthorDate: Mon Jan 29 19:33:50 2024 +0000
Commit: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Tue Jan 30 05:33:10 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46d1100c
www-apps/rutorrent: remove google-code from metadata
The package has moved to github and the google-code mirror does not work
any longer.
Signed-off-by: Henning Schild <henning <AT> hennsch.de>
Closes: https://github.com/gentoo/gentoo/pull/35083
Signed-off-by: Viorel Munteanu <ceamac <AT> gentoo.org>
www-apps/rutorrent/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/www-apps/rutorrent/metadata.xml b/www-apps/rutorrent/metadata.xml
index faa46192acdb..64ba08e48229 100644
--- a/www-apps/rutorrent/metadata.xml
+++ b/www-apps/rutorrent/metadata.xml
@@ -11,7 +11,6 @@
</maintainer>
<stabilize-allarches/>
<upstream>
- <remote-id type="google-code">rutorrent</remote-id>
<remote-id type="github">Novik/ruTorrent</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2024-01-30 5:37 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 5:37 Viorel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-24 4:57 [gentoo-commits] repo/gentoo:master commit in: www-apps/rutorrent/ Viorel Munteanu
2025-06-24 4:57 Viorel Munteanu
2025-06-15 23:33 Sam James
2025-06-15 23:33 Sam James
2025-06-09 7:44 Viorel Munteanu
2025-06-09 7:44 Viorel Munteanu
2025-06-01 7:28 Viorel Munteanu
2025-05-27 8:28 Sam James
2025-05-27 8:28 Sam James
2025-05-21 21:15 Sam James
2025-05-21 21:15 Sam James
2025-05-15 17:48 Viorel Munteanu
2025-05-15 17:48 Viorel Munteanu
2025-04-25 17:56 Viorel Munteanu
2025-04-19 18:28 Viorel Munteanu
2025-04-19 18:28 Viorel Munteanu
2025-03-25 16:17 Viorel Munteanu
2025-03-25 16:17 Viorel Munteanu
2025-01-08 16:26 Viorel Munteanu
2025-01-08 16:26 Viorel Munteanu
2024-12-16 18:20 Viorel Munteanu
2024-12-16 18:20 Viorel Munteanu
2024-12-13 11:44 Viorel Munteanu
2024-12-13 11:44 Viorel Munteanu
2024-12-13 11:44 Viorel Munteanu
2024-12-02 16:42 Viorel Munteanu
2024-12-02 16:42 Viorel Munteanu
2024-12-02 16:42 Viorel Munteanu
2024-10-28 15:53 Viorel Munteanu
2024-10-28 15:53 Viorel Munteanu
2024-10-18 17:16 Viorel Munteanu
2024-10-18 17:16 Viorel Munteanu
2024-09-26 16:53 Viorel Munteanu
2024-08-27 11:47 Viorel Munteanu
2024-07-12 6:53 Viorel Munteanu
2024-07-12 6:53 Viorel Munteanu
2024-06-24 6:28 Viorel Munteanu
2024-06-24 6:28 Viorel Munteanu
2024-06-23 7:13 Viorel Munteanu
2024-06-23 7:13 Viorel Munteanu
2024-06-14 5:19 Viorel Munteanu
2024-01-21 8:00 Viorel Munteanu
2024-01-21 4:02 Sam James
2023-12-27 13:47 Viorel Munteanu
2023-12-23 9:26 Viorel Munteanu
2023-12-08 20:05 Arthur Zamarin
2023-10-18 16:15 Viorel Munteanu
2023-10-01 16:22 Viorel Munteanu
2023-06-16 6:43 Viorel Munteanu
2023-06-16 5:55 Viorel Munteanu
2023-05-09 4:56 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-03-02 18:06 Viorel Munteanu
2023-03-01 18:05 Viorel Munteanu
2022-08-31 22:56 John Helmert III
2021-01-10 22:27 Sam James
2018-01-11 5:33 Michael Palimaka
2018-01-10 8:44 Michael Palimaka
2018-01-10 8:44 Michael Palimaka
2018-01-10 8:44 Michael Palimaka
2015-09-01 20:11 Tobias Klausmann
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=1706592790.46d1100ce26435a9a6836f397ee6ae52b37a643c.ceamac@gentoo \
--to=ceamac@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