public inbox for [email protected]
help / color / mirror / Atom feedgit repo "https://" working but "git://" is not
4+ messages / 3 participants
[nested] [flat]
* git repo "https://" working but "git://" is not
@ 2025-05-27 19:38 Jeff Davis <[email protected]>
2025-05-28 16:47 ` Re: git repo "https://" working but "git://" is not Masahiko Sawada <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Davis @ 2025-05-27 19:38 UTC (permalink / raw)
To: pgsql-www
It appears that something is going on with git.postgresql.org. Remotes
with "https://"; are working but not "git://".
Regards,
Jeff Davis
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: git repo "https://" working but "git://" is not
2025-05-27 19:38 git repo "https://" working but "git://" is not Jeff Davis <[email protected]>
@ 2025-05-28 16:47 ` Masahiko Sawada <[email protected]>
2025-05-28 17:51 ` Re: git repo "https://" working but "git://" is not Álvaro Herrera <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Masahiko Sawada @ 2025-05-28 16:47 UTC (permalink / raw)
To: Jeff Davis <[email protected]>; +Cc: pgsql-www
On Tue, May 27, 2025 at 12:38 PM Jeff Davis <[email protected]> wrote:
>
> It appears that something is going on with git.postgresql.org. Remotes
> with "https://"; are working but not "git://".
Same here. I've been using "git://" too but I switched to "https://";.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: git repo "https://" working but "git://" is not
2025-05-27 19:38 git repo "https://" working but "git://" is not Jeff Davis <[email protected]>
2025-05-28 16:47 ` Re: git repo "https://" working but "git://" is not Masahiko Sawada <[email protected]>
@ 2025-05-28 17:51 ` Álvaro Herrera <[email protected]>
2025-05-28 18:59 ` Re: git repo "https://" working but "git://" is not Jeff Davis <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Álvaro Herrera @ 2025-05-28 17:51 UTC (permalink / raw)
To: Masahiko Sawada <[email protected]>; +Cc: Jeff Davis <[email protected]>; pgsql-www
On 2025-May-28, Masahiko Sawada wrote:
> On Tue, May 27, 2025 at 12:38 PM Jeff Davis <[email protected]> wrote:
> >
> > It appears that something is going on with git.postgresql.org. Remotes
> > with "https://"; are working but not "git://".
>
> Same here. I've been using "git://" too but I switched to "https://";.
git:// was taken down recently because of a system upgrade. It's not
clear that we'll put it back in operation ... at least as I understand,
that protocol is pretty much obsolete, as it's unencrypted and
unauthenticated.
As Masahiko-san said, you can simply update the remotes to use https://,
with something like
git remote set-url origin https://...
and everything should work again.
Please don't consider this a formal announcement of removal, though :-)
That may still follow, pending further analysis.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"I can see support will not be a problem. 10 out of 10." (Simon Wittber)
(http://archives.postgresql.org/pgsql-general/2004-12/msg00159.php)
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: git repo "https://" working but "git://" is not
2025-05-27 19:38 git repo "https://" working but "git://" is not Jeff Davis <[email protected]>
2025-05-28 16:47 ` Re: git repo "https://" working but "git://" is not Masahiko Sawada <[email protected]>
2025-05-28 17:51 ` Re: git repo "https://" working but "git://" is not Álvaro Herrera <[email protected]>
@ 2025-05-28 18:59 ` Jeff Davis <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Jeff Davis @ 2025-05-28 18:59 UTC (permalink / raw)
To: Álvaro Herrera <[email protected]>; Masahiko Sawada <[email protected]>; +Cc: pgsql-www
On Wed, 2025-05-28 at 19:51 +0200, Álvaro Herrera wrote:
> Please don't consider this a formal announcement of removal, though
> :-)
> That may still follow, pending further analysis.
I'd suggest some kind of announcement. It's easy to fix, but I was
briefly confused about why it wasn't working. And I could imagine that
there are a few automated build / test scripts floating around that
need updating.
If we previously made a deprecation announcement, then perhaps its not
necessary.
Regards,
Jeff Davis
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-05-28 18:59 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-05-27 19:38 git repo "https://" working but "git://" is not Jeff Davis <[email protected]>
2025-05-28 16:47 ` Masahiko Sawada <[email protected]>
2025-05-28 17:51 ` Álvaro Herrera <[email protected]>
2025-05-28 18:59 ` Jeff Davis <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox