Re: HG-Bridge disabled (Mercurial connection refused)

On Wed, 20 Nov 2024, Tony Mechelynck wrote:

> On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <[email protected]> wrote:
> >
> > Hi,
> > just to let everybody know. Because of serious load issues, the HG
> > bridge is disabled for now.
> >
> > Just for my reference, how many users are still using it hg.256bit.org?
> 
> I don't know how many are, but as I suppose you already know, I am one
> of them. For some reason Mercurial feels congenial to me and git
> doesn't.
> 
> My current Mercurial configuration includes the following remote
> repository aliases, which I am listing alphabetically below with name,
> URL, and current response to "hg in". Some of them may be obsolete.
>     bitbucket = https://bitbucket.org/vim-mirror/vim
>         Not found.
>     default = http://hg.256bit.org/vim
>         Not found.
>     osdn = https://hg.osdn.net/view/vim/vim
>         Certificate has expired.
> In other words, the latter one is still responding, but rejecting the
> request for lack of an up-to-date certificate.
> I practically always pull from the "default" source unless, like now,
> it really goes down.

Oh, Apparently I am still pushing to osdn, I thought I had disabled this 
long time ago. For the time being, you can continue to use that one.

> > If there are very many users, we should probably move it to the vim.org
> > domain.
> 
> If you could do that without too much hassle, for someone at the
> receiving end like me it would just be a matter of adjusting the
> source aliases (i.e. those displayed by "hg paths") to make sure that
> the "default" source is the one we normally want to pull from. A piece
> of cake.

I think we can configure a vim.org subdomain hg.vim.org and move the 
bridge over there. Shouldn't be too much effort I suppose. CC: @Marc for 
your info (as he is taking care of the hosting)

@Sec: Is it possible to configure a new hg.vim.org subdomain and point 
it to the vim.org domain please?

Thanks all,
Christian
-- 
Thank you for observing all safety precautions.

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/vim_use/Zz2tIppTyWgFrnvM%40256bit.org.