From: "Takuya Wakazono" <pastalian46@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sec-keys/signify-keys-telescope/
Date: Sun, 30 Jun 2024 13:50:03 +0000 (UTC) [thread overview]
Message-ID: <1719755309.6bbd428ebf891d189a6db43dea376e7cbc476ef0.pastalian46@gentoo> (raw)
commit: 6bbd428ebf891d189a6db43dea376e7cbc476ef0
Author: Takuya Wakazono <pastalian46 <AT> gmail <DOT> com>
AuthorDate: Sun Jun 30 13:48:29 2024 +0000
Commit: Takuya Wakazono <pastalian46 <AT> gmail <DOT> com>
CommitDate: Sun Jun 30 13:48:29 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6bbd428e
sec-keys/signify-keys-telescope: update HOMEPAGE
Signed-off-by: Takuya Wakazono <pastalian46 <AT> gmail.com>
sec-keys/signify-keys-telescope/metadata.xml | 2 +-
sec-keys/signify-keys-telescope/signify-keys-telescope-0.10.ebuild | 2 +-
sec-keys/signify-keys-telescope/signify-keys-telescope-0.9.ebuild | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sec-keys/signify-keys-telescope/metadata.xml b/sec-keys/signify-keys-telescope/metadata.xml
index 695e0f1ae..13a010dc9 100644
--- a/sec-keys/signify-keys-telescope/metadata.xml
+++ b/sec-keys/signify-keys-telescope/metadata.xml
@@ -3,6 +3,6 @@
<pkgmetadata>
<!-- maintainer-needed -->
<upstream>
- <remote-id type="github">omar-polo/telescope</remote-id>
+ <remote-id type="github">telescope-browser/telescope</remote-id>
</upstream>
</pkgmetadata>
diff --git a/sec-keys/signify-keys-telescope/signify-keys-telescope-0.10.ebuild b/sec-keys/signify-keys-telescope/signify-keys-telescope-0.10.ebuild
index 4432de27a..d884faded 100644
--- a/sec-keys/signify-keys-telescope/signify-keys-telescope-0.10.ebuild
+++ b/sec-keys/signify-keys-telescope/signify-keys-telescope-0.10.ebuild
@@ -5,7 +5,7 @@ EAPI=8
MY_P="${PN#signify-keys-}-${PV}"
DESCRIPTION="Signify keys used to sign telescope releases"
-HOMEPAGE="https://telescope.omarpolo.com/"
+HOMEPAGE="https://www.telescope-browser.org/"
SRC_URI="https://ftp.omarpolo.com/${MY_P}.pub"
S="${WORKDIR}"
diff --git a/sec-keys/signify-keys-telescope/signify-keys-telescope-0.9.ebuild b/sec-keys/signify-keys-telescope/signify-keys-telescope-0.9.ebuild
index 4432de27a..d884faded 100644
--- a/sec-keys/signify-keys-telescope/signify-keys-telescope-0.9.ebuild
+++ b/sec-keys/signify-keys-telescope/signify-keys-telescope-0.9.ebuild
@@ -5,7 +5,7 @@ EAPI=8
MY_P="${PN#signify-keys-}-${PV}"
DESCRIPTION="Signify keys used to sign telescope releases"
-HOMEPAGE="https://telescope.omarpolo.com/"
+HOMEPAGE="https://www.telescope-browser.org/"
SRC_URI="https://ftp.omarpolo.com/${MY_P}.pub"
S="${WORKDIR}"
next reply other threads:[~2024-06-30 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 13:50 Takuya Wakazono [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-30 13:50 [gentoo-commits] repo/proj/guru:dev commit in: sec-keys/signify-keys-telescope/ Takuya Wakazono
2024-04-09 1:24 Anna Vyalkova
2024-04-09 1:24 Anna Vyalkova
2024-04-09 1:24 Anna Vyalkova
2023-05-12 9:32 Matt Jolly
2022-05-30 17:47 Anna Vyalkova
2022-01-16 17:58 Anna Vyalkova
2022-01-03 9:43 Anna Vyalkova
2022-01-02 18:55 Andrew Ammerlaan
2021-12-19 14:13 Anna Vyalkova
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=1719755309.6bbd428ebf891d189a6db43dea376e7cbc476ef0.pastalian46@gentoo \
--to=pastalian46@gmail.com \
--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