Error 503 on Mercurial server

27 views
Skip to first unread message

Tony Mechelynck

unread,
Nov 6, 2025, 10:19:45 AMNov 6
to vim_dev
The latest changeset I have been able to download is the second
runtime change (dated 2025-11-05 23:14:23 +0100) after patch 9.1.1896.
This "latest runtime change" has Mercurial changeset ID 1961fe307a90
and git changeset ID 7dfdc7f6cb802d5283e2e0eedb87932b9cd2cb3 ; it
modifies .github/MAINTAINERS, runtime/ftplugin/sml.vim and
runtime/indent/sml.vim.

Since then, every time I run "hg incoming" I get "HTTP Error 503:
Service unavailable" and exit status 255.

Best regards,
Tony.

Christian Brabandt

unread,
Nov 6, 2025, 10:49:41 AMNov 6
to vim...@googlegroups.com
Great, just yesterday I tweaked it to make it work again.

I am going to turn this off Tony. It's causing too many stability issues
on the Vim homepage for no additional benefit.

Best,
Christian
--
One thought driven home is better than three left on base.

Tony Mechelynck

unread,
Nov 6, 2025, 12:37:47 PMNov 6
to Christian Brabandt, vim...@googlegroups.com
Hm. I had thought to enable the Mercurial "git" extension but its help
is not very helpful. The following is all it says (for hg version
7.1.1):

git extension - grant Mercurial the ability to operate on Git repositories.
(EXPERIMENTAL)

This is currently super experimental. It probably will consume your firstborn
a la Rumpelstiltskin, etc.

(use 'hg help extensions' for information on enabling extensions)

Best regards,
Tony.

Marvin Renich

unread,
Nov 6, 2025, 1:44:03 PMNov 6
to vim...@googlegroups.com
* Tony Mechelynck <antoine.m...@gmail.com> [251106 12:37]:
> Hm. I had thought to enable the Mercurial "git" extension but its help
> is not very helpful. The following is all it says (for hg version
> 7.1.1):
>
> git extension - grant Mercurial the ability to operate on Git repositories.
> (EXPERIMENTAL)
>
> This is currently super experimental. It probably will consume your firstborn
> a la Rumpelstiltskin, etc.
>
> (use 'hg help extensions' for information on enabling extensions)

Tony, I use hggit. To enable it, add to your ~/.hgrc (or .hg/hgrc in a
specific repo):

[extensions]
hggit =

Then you can get help with «hg help hggit». Basically, you just clone
the git repo:

hg clone git+https://github.com/vim/vim.git

and then use it as a local Mercurial repo, including push and pull.

...Marvin

Tony Mechelynck

unread,
Nov 7, 2025, 5:00:27 AMNov 7
to vim...@googlegroups.com
My Mercurial distribution (hg 7.1.1 from openSUSE Tumbleweed) includes
the git extension but not the hggit extension. Anyway, I've made the
jump and cloned the master git repository. Not that I like it. I
haven't (yet) implemented my few local additions (one line in
src/feature.h IIRC), and like previously, instead of modifying the
distributed files, I use

ln -svf ../Makefile
ln -svf ../config.mk.dist

once and for all in each of my shadow directories to keep these files
updated. Also like before, my configurations are defined in the
environment, a slightly different one in each shell, one per shadow
directory, so when a new patch comes in, I can compile all my
differently-configured versions of Vim in parallel.

Took me some time to find out that "git status" would tell me if I
need to pull, like "hg incoming" does it for Mercurial.

Best regards,
Tony.
Reply all
Reply to author
Forward
0 new messages