From: "Tobias Klausmann" <klausman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/rutorrent/
Date: Tue, 1 Sep 2015 20:11:36 +0000 (UTC) [thread overview]
Message-ID: <1441138086.e16bc8a22b9a00691bbba27f5da39361dce62be6.klausman@gentoo> (raw)
commit: e16bc8a22b9a00691bbba27f5da39361dce62be6
Author: Tobias Klausmann <klausman <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 1 20:08:06 2015 +0000
Commit: Tobias Klausmann <klausman <AT> gentoo <DOT> org>
CommitDate: Tue Sep 1 20:08:06 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e16bc8a2
www-apps/rutorrent: Fixing HOMEPAGE move due to code.google.com shutdown
Package-Manager: portage-2.2.20.1
www-apps/rutorrent/rutorrent-3.4-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www-apps/rutorrent/rutorrent-3.4-r1.ebuild b/www-apps/rutorrent/rutorrent-3.4-r1.ebuild
index 692537b..aea032b 100644
--- a/www-apps/rutorrent/rutorrent-3.4-r1.ebuild
+++ b/www-apps/rutorrent/rutorrent-3.4-r1.ebuild
@@ -7,7 +7,7 @@ EAPI="4"
inherit webapp eutils
DESCRIPTION="ruTorrent is a front-end for the popular Bittorrent client rTorrent"
-HOMEPAGE="https://code.google.com/p/rutorrent/"
+HOMEPAGE="https://github.com/Novik/ruTorrent"
SRC_URI="
https://rutorrent.googlecode.com/files/${P}.tar.gz
https://rutorrent.googlecode.com/files/plugins-${PV}.tar.gz"
next reply other threads:[~2015-09-01 20:11 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 20:11 Tobias Klausmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 8:44 [gentoo-commits] repo/gentoo:master commit in: www-apps/rutorrent/ Michael Palimaka
2018-01-10 8:44 Michael Palimaka
2018-01-10 8:44 Michael Palimaka
2018-01-11 5:33 Michael Palimaka
2021-01-10 22:27 Sam James
2022-08-31 22:56 John Helmert III
2023-03-01 18:05 Viorel Munteanu
2023-03-02 18:06 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-04-28 8:26 Viorel Munteanu
2023-05-09 4:56 Viorel Munteanu
2023-06-16 5:55 Viorel Munteanu
2023-06-16 6:43 Viorel Munteanu
2023-10-01 16:22 Viorel Munteanu
2023-10-18 16:15 Viorel Munteanu
2023-12-08 20:05 Arthur Zamarin
2023-12-23 9:26 Viorel Munteanu
2023-12-27 13:47 Viorel Munteanu
2024-01-21 4:02 Sam James
2024-01-21 8:00 Viorel Munteanu
2024-01-30 5:37 Viorel Munteanu
2024-06-14 5:19 Viorel Munteanu
2024-06-23 7:13 Viorel Munteanu
2024-06-23 7:13 Viorel Munteanu
2024-06-24 6:28 Viorel Munteanu
2024-06-24 6:28 Viorel Munteanu
2024-07-12 6:53 Viorel Munteanu
2024-07-12 6:53 Viorel Munteanu
2024-08-27 11:47 Viorel Munteanu
2024-09-26 16:53 Viorel Munteanu
2024-10-18 17:16 Viorel Munteanu
2024-10-18 17:16 Viorel Munteanu
2024-10-28 15:53 Viorel Munteanu
2024-10-28 15:53 Viorel Munteanu
2024-12-02 16:42 Viorel Munteanu
2024-12-02 16:42 Viorel Munteanu
2024-12-02 16:42 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-16 18:20 Viorel Munteanu
2024-12-16 18:20 Viorel Munteanu
2025-01-08 16:26 Viorel Munteanu
2025-01-08 16:26 Viorel Munteanu
2025-03-25 16:17 Viorel Munteanu
2025-03-25 16:17 Viorel Munteanu
2025-04-19 18:28 Viorel Munteanu
2025-04-19 18:28 Viorel Munteanu
2025-04-25 17:56 Viorel Munteanu
2025-05-15 17:48 Viorel Munteanu
2025-05-15 17:48 Viorel Munteanu
2025-05-21 21:15 Sam James
2025-05-21 21:15 Sam James
2025-05-27 8:28 Sam James
2025-05-27 8:28 Sam James
2025-06-01 7:28 Viorel Munteanu
2025-06-09 7:44 Viorel Munteanu
2025-06-09 7:44 Viorel Munteanu
2025-06-15 23:33 Sam James
2025-06-15 23:33 Sam James
2025-06-24 4:57 Viorel Munteanu
2025-06-24 4:57 Viorel Munteanu
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=1441138086.e16bc8a22b9a00691bbba27f5da39361dce62be6.klausman@gentoo \
--to=klausman@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