public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eli Schwartz" <eschwartz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: games-simulation/flightgear/
Date: Mon, 12 Aug 2024 01:16:22 +0000 (UTC)	[thread overview]
Message-ID: <1723425360.0bf450f5e4fae70aea1615b1ef6885e750c904c8.eschwartz@gentoo> (raw)

commit:     0bf450f5e4fae70aea1615b1ef6885e750c904c8
Author:     Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 12 00:59:12 2024 +0000
Commit:     Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
CommitDate: Mon Aug 12 01:16:00 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0bf450f5

games-simulation/flightgear: use https for git clones in live

Using git:// is a really bad idea and the eclass yells at you for it.
And the second uri does not actually exist (anymore).

Note: the live ebuild still doesn't actually build. The patch is stale
and then there are a bunch of weird "XXX does not name a type" and
"YYY was not declared in this scope" errors that I have no patience to
debug. Perhaps an upstream bug. I was able to determine that existing
LTO errors are still present and then gave up. Baby steps... :D

Signed-off-by: Eli Schwartz <eschwartz <AT> gentoo.org>

 games-simulation/flightgear/flightgear-9999.ebuild | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/games-simulation/flightgear/flightgear-9999.ebuild b/games-simulation/flightgear/flightgear-9999.ebuild
index b35e56b521a8..ec1215fc6d90 100644
--- a/games-simulation/flightgear/flightgear-9999.ebuild
+++ b/games-simulation/flightgear/flightgear-9999.ebuild
@@ -7,8 +7,7 @@ inherit cmake toolchain-funcs git-r3
 
 DESCRIPTION="Open Source Flight Simulator"
 HOMEPAGE="https://www.flightgear.org/"
-EGIT_REPO_URI="git://git.code.sf.net/p/${PN}/${PN}
-	git://mapserver.flightgear.org/${PN}"
+EGIT_REPO_URI="https://git.code.sf.net/p/${PN}/${PN}"
 EGIT_BRANCH="next"
 
 LICENSE="GPL-2"


             reply	other threads:[~2024-08-12  1:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12  1:16 Eli Schwartz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-12  1:16 [gentoo-commits] repo/gentoo:master commit in: games-simulation/flightgear/ Eli Schwartz
2024-06-04  1:50 Maciej Mrozowski
2023-07-27 19:42 Andreas Sturmlechner
2023-04-26  4:10 Sam James
2023-04-26  4:03 Sam James
2022-12-16  1:57 Sam James
2022-08-11  7:37 Ionen Wolkens
2022-05-16  8:12 David Seifert
2022-05-13 19:49 Sam James
2021-04-24 22:03 David Seifert
2020-10-31 11:11 David Seifert
2020-10-06 19:33 Maciej Mrozowski
2020-08-04 20:09 Maciej Mrozowski
2020-02-06  1:13 Maciej Mrozowski
2020-02-01  1:02 Maciej Mrozowski
2020-01-24 18:52 David Seifert
2018-12-24 22:15 Lars Wendler
2018-05-22 23:54 Maciej Mrozowski
2017-03-04 17:09 Lars Wendler
2017-03-04 10:50 Lars Wendler
2017-03-04 10:50 Lars Wendler
2017-01-11 17:46 Lars Wendler
2017-01-11 16:17 Agostino Sarubbo
2016-12-29 18:07 Lars Wendler
2016-12-25 14:22 Lars Wendler
2016-12-20 19:16 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=1723425360.0bf450f5e4fae70aea1615b1ef6885e750c904c8.eschwartz@gentoo \
    --to=eschwartz@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