From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/glyphsLib/
Date: Mon, 30 May 2022 23:04:27 +0000 (UTC) [thread overview]
Message-ID: <1653951863.6802df663b7b7b2b965b0746a1de20deea725742.Alessandro-Barbieri@gentoo> (raw)
commit: 6802df663b7b7b2b965b0746a1de20deea725742
Author: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Mon May 30 23:00:34 2022 +0000
Commit: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Mon May 30 23:04:23 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6802df66
dev-python/glyphsLib: update SRC_URI
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>
dev-python/glyphsLib/Manifest | 2 +-
dev-python/glyphsLib/glyphsLib-6.0.5.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-python/glyphsLib/Manifest b/dev-python/glyphsLib/Manifest
index 3ac7f10fb..7dbcf21e9 100644
--- a/dev-python/glyphsLib/Manifest
+++ b/dev-python/glyphsLib/Manifest
@@ -1 +1 @@
-DIST glyphsLib-6.0.5.tar.gz 31132348 BLAKE2B 7c4dbaac9db5142421e9b9785f363f6a8af3923f62b2c635d22072ce7a60a3c775371d7c1f75410509bb072e81cb1922e4d294fa2eb4b68c5fd67859c949f058 SHA512 71c371fac446f313c373923d3fcd675e3007ab9ffddf7bb0540a305c6412fcfccc7be90208398e8238d4774b40488b819517cbf170b789ad276168ac416b9c06
+DIST glyphsLib-6.0.5.gh.tar.gz 31132348 BLAKE2B 7c4dbaac9db5142421e9b9785f363f6a8af3923f62b2c635d22072ce7a60a3c775371d7c1f75410509bb072e81cb1922e4d294fa2eb4b68c5fd67859c949f058 SHA512 71c371fac446f313c373923d3fcd675e3007ab9ffddf7bb0540a305c6412fcfccc7be90208398e8238d4774b40488b819517cbf170b789ad276168ac416b9c06
diff --git a/dev-python/glyphsLib/glyphsLib-6.0.5.ebuild b/dev-python/glyphsLib/glyphsLib-6.0.5.ebuild
index 82ab32585..5cc7920a6 100644
--- a/dev-python/glyphsLib/glyphsLib-6.0.5.ebuild
+++ b/dev-python/glyphsLib/glyphsLib-6.0.5.ebuild
@@ -10,7 +10,7 @@ inherit distutils-r1
DESCRIPTION="A library to provide a bridge from Glyphs source files to UFOs"
HOMEPAGE="https://github.com/googlefonts/glyphsLib"
-SRC_URI="https://github.com/googlefonts/${PN}/archive/refs/tags/v${PV}.tar.gz -> ${P}.tar.gz"
+SRC_URI="https://github.com/googlefonts/${PN}/archive/refs/tags/v${PV}.tar.gz -> ${P}.gh.tar.gz"
LICENSE="Apache-2.0 MIT"
KEYWORDS="~amd64"
next reply other threads:[~2022-05-30 23:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 23:04 Alessandro Barbieri [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-09 15:26 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/glyphsLib/ Anna Vyalkova
2023-05-04 2:02 Anna Vyalkova
2022-06-01 5:03 Anna Vyalkova
2022-05-30 23:04 Alessandro Barbieri
2022-05-06 0:36 Alessandro Barbieri
2022-03-26 9:23 Alessandro Barbieri
2022-03-24 14:23 Alessandro Barbieri
2022-03-18 9:55 Alessandro Barbieri
2022-03-17 19:29 Ronny Gutbrod
2022-03-17 1:42 Alessandro Barbieri
2021-10-03 22:16 Alessandro Barbieri
2021-06-19 21:53 Alessandro Barbieri
2021-06-14 23:09 Alessandro Barbieri
2021-06-14 2:27 Alessandro Barbieri
2021-05-05 7:32 Alessandro Barbieri
2021-03-28 9:55 Andrew Ammerlaan
2021-02-22 1:54 Alessandro Barbieri
2020-12-12 15:35 Andrew Ammerlaan
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=1653951863.6802df663b7b7b2b965b0746a1de20deea725742.Alessandro-Barbieri@gentoo \
--to=lssndrbarbieri@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