On Wed, Nov 20, 2024 at 11:10 AM Christian Brabandt <cblists@256bit.org> wrote:
>
>
> On Wed, 20 Nov 2024, Christian Brabandt wrote:
>
> >
> > On Wed, 20 Nov 2024, Tony Mechelynck wrote:
> >
> > > On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <cblists@256bit.org> 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.
>
> Hm, I can still pull using --insecure
>
> But pushing is totally broken:
> ```
> pushing to ssh://chrisbra@osdn//hgroot/vim/vim
> remote: logger: socket /dev/log: Connection refused
> searching for changes
> remote: abort: No usable temporary directory found in ['/tmp',
> '/var/tmp', '/usr/tmp', '/home/users/c/ch/chrisbra']
> abort: unexpected response: empty string
> ```
> and neither can I push using https urls, so this repository is at
> ```
> changeset: 36245:368dd9765c4d
> tag: tip
> user: Christian Brabandt <cb@256bit.org>
> date: Sat Oct 05 17:15:03 2024 +0200
> summary: runtime(compiler): add cppcheck linter compiler plugin
> ```
>
> We will setup a secondary vim.org mercurial mirror, but this will take
> some time.
Take all the time you need ; in the meantime I have two temporary
solutions as I mentioned in another thread (1. keep using Vim 9.1.873
compiled from my own config options when hg.256bit.org/vim was still
online ; 2. fall back on the Vim from my Linux distro, which will
always be a little behind the times but not much and will never be
exactly what I would have configured myself, but it is usable ;
currently it is at 9.1.836, Huge, with GTK3 GUI).
Best regards,
Tony.
--
--
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 vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJkCKXsRfVC9aqiwOox3WB3GPCiyOufAfa2EfK66_YiwJNXZ%2BQ%40mail.gmail.com.
Wednesday, November 20, 2024
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment