From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/github-cli/
Date: Wed, 1 Jun 2022 01:51:26 +0000 (UTC) [thread overview]
Message-ID: <1654048250.ccce45a6a9753733dab4ecc3c4ccff4d6f3d8866.sam@gentoo> (raw)
commit: ccce45a6a9753733dab4ecc3c4ccff4d6f3d8866
Author: Randall T. Vasquez <ran.dall <AT> icloud <DOT> com>
AuthorDate: Sun May 29 15:04:31 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 1 01:50:50 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ccce45a6
dev-util/github-cli: version bump
This commit bumps dev-util/github-cli from v2.11.0 to 2.11.3.
Signed-off-by: Randall T. Vasquez <ran.dall <AT> icloud.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/github-cli/Manifest | 4 ++--
.../{github-cli-2.11.0.ebuild => github-cli-2.11.3.ebuild} | 6 +++++-
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/dev-util/github-cli/Manifest b/dev-util/github-cli/Manifest
index 82a40e137dc9..aafc44154b04 100644
--- a/dev-util/github-cli/Manifest
+++ b/dev-util/github-cli/Manifest
@@ -1,2 +1,2 @@
-DIST github-cli-2.11.0-deps.tar.xz 76402168 BLAKE2B 210c9861199caf92aff566334530fe953cd66134219b88d83fc973920f9264b2343d1f3b16338b190b64333eaa825fd498e7e5011f03c87c2f8786316332e4f4 SHA512 f147e76cf0705d3e8da2296c038911c2b11e422d14dfdfce34bf31d0813189fba501878dcc5c37323b5ece37fa4948730c351c5438cc8a11e99677d2b8678801
-DIST github-cli-2.11.0.tar.gz 716133 BLAKE2B 10c35dd8dd52e930c8dbae32d4ad5e02f2cb17872f9f1a4652ca6be7df2f8d38b18b98a1cf3577a249830691431f3408e0c3e00fda588e8c35412e32efcf2597 SHA512 4cccaf9baf1486ab031ffc4b0caf96b0b8eb0f25b52a303cc642ff35586139c13727b20cc9d4dc90335ba5b630f8778c49c6d7dcfdeb709df8c0de536e033ada
+DIST github-cli-2.11.3-deps.tar.xz 76137064 BLAKE2B 6b8a224f8e0b05c32c8be83b4f5a0b05febb44b230c06ce0d14dfb5a814faf0361d24f32a5feb1ec348e9b80dd35635249bdf1febf6cd6202ba5ea1e3e6a3168 SHA512 f72909be8798a7efed8cb2ee2c37f51216056901fd285b4e2c894ebfc2f08194b99d846f2f0080da4c1c3359b47e36f7eece11b4bec93485da5330ad38c073f1
+DIST github-cli-2.11.3.tar.gz 716386 BLAKE2B dcb07cda11e03ffe75a9ec2fcb0ed33c1f2c6bb7599ed1b47ee9e1e0df609fa21ae2dd043be417cfee75dcb3686290f510c0fdffc0b1df08f816ab2ac79d940b SHA512 952cd7c2a327c7169e201a4aa7c26a0e5c09a1ecef51b8d7c620fa9a849c2e8cc61447333f785851487a68d058b869e10bb290188594bd2fb00b0384297bdfd8
diff --git a/dev-util/github-cli/github-cli-2.11.0.ebuild b/dev-util/github-cli/github-cli-2.11.3.ebuild
similarity index 86%
rename from dev-util/github-cli/github-cli-2.11.0.ebuild
rename to dev-util/github-cli/github-cli-2.11.3.ebuild
index ec899ad1ea48..e08b4ff2cbbe 100644
--- a/dev-util/github-cli/github-cli-2.11.0.ebuild
+++ b/dev-util/github-cli/github-cli-2.11.3.ebuild
@@ -2,7 +2,7 @@
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit bash-completion-r1 go-module
+inherit bash-completion-r1 flag-o-matic go-module
DESCRIPTION="GitHub CLI"
HOMEPAGE="https://github.com/cli/cli"
@@ -35,6 +35,10 @@ src_unpack() {
src_compile() {
[[ ${PV} == *9999 ]] || export GH_VERSION="v${PV}"
+ # Filter '-flto*' flags to avoid build failures.
+ filter-flags "-flto*"
+ # Filter '-ggdb3' flag to avoid build failures. bugs.gentoo.org/847991
+ filter-flags "-ggdb3"
# Go LDFLAGS are not the same as GCC/Binutils LDFLAGS
unset LDFLAGS
# Once we set up cross compiling, this line will need to be adjusted
next reply other threads:[~2022-06-01 1:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 1:51 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-15 21:18 [gentoo-commits] repo/gentoo:master commit in: dev-util/github-cli/ Sam James
2024-08-15 21:18 Sam James
2024-06-27 16:48 William Hubbs
2024-01-12 22:32 William Hubbs
2023-09-01 18:08 William Hubbs
2023-08-07 19:31 William Hubbs
2023-06-24 2:59 Sam James
2023-06-22 20:39 William Hubbs
2023-06-22 20:38 William Hubbs
2023-04-13 15:02 William Hubbs
2023-01-16 20:11 William Hubbs
2022-12-01 21:16 William Hubbs
2022-12-01 21:13 William Hubbs
2022-10-19 20:42 William Hubbs
2022-10-19 20:42 William Hubbs
2022-08-25 7:07 WANG Xuerui
2022-08-25 7:07 WANG Xuerui
2022-08-05 19:00 William Hubbs
2022-08-04 18:41 Arthur Zamarin
2022-08-04 6:27 Arthur Zamarin
2022-06-22 14:55 William Hubbs
2022-06-22 14:55 William Hubbs
2022-06-01 1:51 Sam James
2022-06-01 1:51 Sam James
2022-06-01 1:51 Sam James
2022-05-24 15:12 William Hubbs
2022-05-24 15:12 William Hubbs
2022-05-24 15:04 William Hubbs
2022-04-20 1:44 William Hubbs
2022-03-10 2:37 Yixun Lan
2022-02-22 15:25 William Hubbs
2022-02-22 15:10 William Hubbs
2022-01-01 18:05 William Hubbs
2021-08-26 16:09 William Hubbs
2021-08-26 16:07 William Hubbs
2021-08-10 21:02 William Hubbs
2021-08-10 21:02 William Hubbs
2021-05-25 11:12 Joonas Niilola
2021-04-16 6:04 William Hubbs
2021-04-02 17:29 William Hubbs
2021-03-14 17:58 William Hubbs
2021-02-24 19:22 William Hubbs
2021-01-29 16:40 William Hubbs
2021-01-29 16:37 William Hubbs
2021-01-29 15:54 William Hubbs
2020-12-23 17:03 William Hubbs
2020-09-17 14:12 William Hubbs
2020-07-26 17:52 William Hubbs
2020-06-12 21:14 William Hubbs
2020-06-07 18:00 William Hubbs
2020-05-31 4:18 Robin H. Johnson
2020-05-31 4:18 Robin H. Johnson
2020-05-31 4:18 Robin H. Johnson
2020-05-26 20:19 William Hubbs
2020-05-18 15:48 Mike Gilbert
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=1654048250.ccce45a6a9753733dab4ecc3c4ccff4d6f3d8866.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