bitbucket is going to drop Mercurial

[Tony Mechelynck]

Full details: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket

TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
will be deleted. From then on it will only support git repos.

How it concerns Vim: We have on bitbucket a Mercurial repo, which
mirrors the git repo maintained by Bram on github. So we don't need to
migrate to a git repo (we already have one) but if we do nothing our
existing Mercurial mirror will vanish into thin air on 2020-06-01.

Our current Mercurial repo is maintained by Christian Brabandt, and I
am one of its users; I hope I'm not alone (I understand Mercurial much
better than I do git). So Christian: IIUC you're holding the hot
potato. But maybe someone else has opinions about what to do next (I
don't).

Best regards,
Tony.

[Christian Brabandt]

Oh too bad. I am more of a git users nowadays but I am still sorry,
mercurial support is dropped. That sounds like there is only git left
for distributed versioning control. Does anybody know of other existing
code sharing sites we could use instead? I am willing to keep my script
running (since it's been running flawlessly and I haven't had many
issues with it) and it was an interesting challenge to keep two
repositories synced.

Best,
Christian
--
Dialog ist nur ein anderer Soundeffekt.
-- Alfred Hitchcock

[Tony Mechelynck]

The bitbucket page linked above points to the Mercurial wiki page
https://www.mercurial-scm.org/wiki/MercurialHosting which list a
number of free and paying services which are or were offering
Mercurial hosting support. Bitbucked is already listed there among
those who were. Among free ones who still are, some are restricted to
some software families not including Vim; others, including
SourceForge, are more general. If you're going to remain responsible
for the Vim Mercurial mirror, I think you should have the choice of
which particular service to use.

Best eregards,
Tony.

[Mike Williams]

On 20/08/2019 14:51, Christian Brabandt wrote:
> External Sender: Use caution with links/attachments.

>
> On Di, 20 Aug 2019, Tony Mechelynck wrote:
>
>> Full details: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>>
>> TLDR: Bit bucket won't allow creating *new* Mercurial repos starting
>> 2020-02-01 and on 2020-06-01 all existing Mercurial repos on bitbucket
>> will be deleted. From then on it will only support git repos.
>>
>> How it concerns Vim: We have on bitbucket a Mercurial repo, which
>> mirrors the git repo maintained by Bram on github. So we don't need to
>> migrate to a git repo (we already have one) but if we do nothing our
>> existing Mercurial mirror will vanish into thin air on 2020-06-01.
>>
>> Our current Mercurial repo is maintained by Christian Brabandt, and I
>> am one of its users; I hope I'm not alone (I understand Mercurial much
>> better than I do git). So Christian: IIUC you're holding the hot
>> potato. But maybe someone else has opinions about what to do next (I
>> don't).
>
> Oh too bad. I am more of a git users nowadays but I am still sorry,
> mercurial support is dropped. That sounds like there is only git left
> for distributed versioning control.

Mercurial itself is not disappearing, but most likely is becoming more
niche with just a few companies and projects holding out. But the sheep
seem to have voted and git has won it seems.

There is the hg-git plugin for those that still want to use Mercurial to
work on Vim, but I don't know how good it actually is.

> Does anybody know of other existing
> code sharing sites we could use instead? I am willing to keep my script
> running (since it's been running flawlessly and I haven't had many
> issues with it) and it was an interesting challenge to keep two
> repositories synced.

https://www.mercurial-scm.org/wiki/MercurialHosting#Free_services

Given the relatively low access it may be simpler to set up a small
hosted read-only server. The repo is only ~80MiB and most reads should
be for delta updates.

TTFN

Mike
--
Verbing weirds language.

[Nick Jensen]

The 2019-08-20 15:51, Christian Brabandt wrote:
> Does anybody know of other existing code sharing sites we could use instead?

What about sourcehut? Drew Devault has just made an announcement: "Sourcehut
welcomes Bitbucket refugees":

https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3CBWEK6BW6V110.3A3B02BDVECCN%40koishi%3E

The announcement includes a script to migrate a bitbucket mercurial repo to
sourcehut.

[Ron Aaron]

I'm also using mercurial to keep my vim up to date. But I could switch to git though I really hate to do that.

[Christian Brabandt]

On Di, 20 Aug 2019, Mike Williams wrote:

> Given the relatively low access it may be simpler to set up a small
> hosted read-only server. The repo is only ~80MiB and most reads should
> be for delta updates.

That's what I did. Please try out: http://hg.256bit.org

It should already mirror the bitbucket server.

Best,
Christian
--
Eine gute Ehe besteht aus einer besseren Hälfte und einer stärkeren Hälfte.
-- Victor de Kowa

[Christian Brabandt]

On Mi, 21 Aug 2019, Christian Brabandt wrote:

>
> On Di, 20 Aug 2019, Mike Williams wrote:
>
> > Given the relatively low access it may be simpler to set up a small
> > hosted read-only server. The repo is only ~80MiB and most reads should
> > be for delta updates.
>
> That's what I did. Please try out: http://hg.256bit.org
>
> It should already mirror the bitbucket server.

Alternatively, we could also enable the mercurial repository at OSDN

We are already using that for the website hosting.

Best,
Christian
--
Viel zu spät begreifen viele
die versäumten Lebensziele:
Freuden, Schönheit und Natur,
Gesundheit, Reisen und Kultur.
Darum, Mensch, sei zeitig weise!
Höchste Zeit ist's! Reise, reise!
-- Wilhelm Busch

[Bram Moolenaar]

> On Mi, 21 Aug 2019, Christian Brabandt wrote:
>
> > On Di, 20 Aug 2019, Mike Williams wrote:
> >
> > > Given the relatively low access it may be simpler to set up a small
> > > hosted read-only server. The repo is only ~80MiB and most reads should
> > > be for delta updates.
> >
> > That's what I did. Please try out: http://hg.256bit.org
> >
> > It should already mirror the bitbucket server.
>
> Alternatively, we could also enable the mercurial repository at OSDN
>
> We are already using that for the website hosting.

It would be nice if that works. So far OSDN has been reliable and
responsive to any problems. Not sure what happens win 256bit.org when
you are on holiday :-).

--
From "know your smileys":
% Bike accident. A bit far-fetched, I suppose; although...
o _ _ _
_o /\_ _ \\o (_)\__/o (_)
_< \_ _>(_) (_)/<_ \_| \ _|/' \/
(_)>(_) (_) (_) (_) (_)' _\o_

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

[Christian Brabandt]

On Mi, 21 Aug 2019, Bram Moolenaar wrote:

> > On Mi, 21 Aug 2019, Christian Brabandt wrote:
> > Alternatively, we could also enable the mercurial repository at OSDN
>

> It would be nice if that works. So far OSDN has been reliable and
> responsive to any problems.

Okay, I also setup osdn mercurial.
https://osdn.net/projects/vim/scm/hg/vim/

I would call it experimental. Just in case you want to update your
scripts to also push directly to the OSDN repository. Then we probably
need to set it up a bit differently. Let me know if you want to do that.

> Not sure what happens win 256bit.org when you are on holiday :-).

The server doesn't actually care if I am on holiday ;)

Well in case the server has some problems, several other things would
break:
- the github notification forwarding
- the mercurial mirror wouldn't updated (bitbucket and now also
hg.256bit.org and osdn)
- the vim-win32-installer repository wouldn't be updated
- coverity reports wouldn't be generated (that was a bit flaky in the
last time, I hope to have resolved that)


Best,
Christian
--
Man soll keine Dummheit zweimal begehen, die Auswahl ist schließlich
groß genug.
-- Jean-Paul Sartre

[Mike Williams]

On 21/08/2019 11:42, Christian Brabandt wrote:
> External Sender: Use caution with links/attachments.
>

> On Di, 20 Aug 2019, Mike Williams wrote:
>
>> Given the relatively low access it may be simpler to set up a small
>> hosted read-only server. The repo is only ~80MiB and most reads should
>> be for delta updates.
>
> That's what I did. Please try out: http://hg.256bit.org

Works for me. Or would you prefer people to use the OSDN repo?

> It should already mirror the bitbucket server.
>
> Best,
> Christian
>

Mike
--
Been there, done that, and someone stole the T-shirt! Hated it.

[Christian Brabandt]

On Do, 22 Aug 2019, Mike Williams wrote:

> > That's what I did. Please try out: http://hg.256bit.org
>
> Works for me. Or would you prefer people to use the OSDN repo?

All those repos are now synchronized, so from the git repo first the
256bit server repo is updated and from there it will be pushed to the
OSDN and bitbucket servers. If Bram does not want to directly push to
OSDN then it will just stay like this (and I will disable pushing to
bitbucket around summer next year).

My server is currently located in Germany and I believe the OSDN data
centers are distributed around the world (with the headquarter located
in japan). So performance wise, I expect a smoother network experience
for people accessing OSDN from asia.

I personally do not like the OSDN server, the interface is a bit
confusing and I prefer the clean view of the hgserver so my personal
preference is quite clear (not that it matters much when working on the
command line) :)

As long as not millions of people try to pull from my server (at the
same time), everything is fine for me. However if I notice issues
(scalability, traffic, performance etc), I might have to disable the
local mercurial server. I will communicate this of course.

Let's test this out for a bit, but I currently do not expect any issues.

Best,
Christian

[Bram Moolenaar]

What are the "hg clone" commands to use? For bitbucket it's:

hg clone https://bitbucket.org/vim-mirror/vim

--
hundred-and-one symptoms of being an internet addict:
95. Only communication in your household is through email.

[Christian Brabandt]

On Do, 22 Aug 2019, Bram Moolenaar wrote:

> What are the "hg clone" commands to use? For bitbucket it's:
>
> hg clone https://bitbucket.org/vim-mirror/vim

hg clone http://hg.256bit.org/vim or
hg clone https://hg.osdn.net/view/vim/vim

For OSDN, the correct URL is also mentioned on the top of the page. If
you go to the Vim project (https://osdn.net/projects/vim/), then click
on Show Code -> Mercurial Vim it will show the server to check out from
next to the Fork button.

Best,
Christian
--
Der Mensch ist ein Seil, geknüpft zwischen Tier und Übermensch - ein
Seil über dem Abgrunde.
-- Friedrich Wilhelm Nietzsche

[Tony Mechelynck]

On Fri, Aug 23, 2019 at 8:40 AM Christian Brabandt <cbl...@256bit.org> wrote:
>
>
> On Do, 22 Aug 2019, Bram Moolenaar wrote:
>
> > What are the "hg clone" commands to use? For bitbucket it's:
> >
> > hg clone https://bitbucket.org/vim-mirror/vim
>
> hg clone http://hg.256bit.org/vim or
> hg clone https://hg.osdn.net/view/vim/vim

IOW, once you have a clone you can set them all in the .hg/hgrc config
file in that clone, for instance as follows:

...
[paths]
default = https://bitbucket.org/vim-mirror/vim
256bit = http://hg.256bit.org/vim
osdn = https://hg.osdn.net/view/vim/vim
...

Then "hg pull 256bit" or "hg fetch 256bit" will pull from the 256bit
Vim repo while "hg pull" or "hg fetch" would still pull from the
bitbucket repo.

IOW, "default" is the one you pull from when you don't specify a
remote source, so once you feel confident that, let's say, the 256bit
repo is stable enough for you, replace "default" by "bitbucket" and
"256bit" by "default" in the above example.

Best regards,
Tony.

[Bram Moolenaar]

Christian wrote:

> On Do, 22 Aug 2019, Bram Moolenaar wrote:
>
> > What are the "hg clone" commands to use? For bitbucket it's:
> >
> > hg clone https://bitbucket.org/vim-mirror/vim
>
> hg clone http://hg.256bit.org/vim or
> hg clone https://hg.osdn.net/view/vim/vim
>
> For OSDN, the correct URL is also mentioned on the top of the page. If
> you go to the Vim project (https://osdn.net/projects/vim/), then click
> on Show Code -> Mercurial Vim it will show the server to check out from
> next to the Fork button.

Thanks, I updated https://www.vim.org/mercurial.php
We'll update it again when we get feedback about which one works best.

--
hundred-and-one symptoms of being an internet addict:

98. The Alta Vista administrators ask you what sites are missing
in their index files.

[Tony Mechelynck]

On Fri, Aug 23, 2019 at 8:35 PM Bram Moolenaar <Br...@moolenaar.net> wrote:
> Thanks, I updated https://www.vim.org/mercurial.php
> We'll update it again when we get feedback about which one works best.

I'm not sure there's a single one which works *best*, i.e. definitely
better than both others at the moment. AFAIK, all we know is that
bitbucket is going to delete all Mercurial repositories in a little
less than a year, so that server should not be relied upon in the long
term. I've modified my .hg/hgrc as said earlier, and while there was
nothing to pull, all three servers told me "no changes found" on the
same clone. Then I set my default to the 256bit server, kept using it,
and just now I pulled patch 8.1.1913 from it. Not the least problem.

TL;DR: AFAIK all three work equally well for the time being, but we
know that bitbucket support isn't going to stay.

Best regards,
Tony.

[Christian Brabandt]

For anybody that is still using the bitbucket server to pull the Vim
source, it is now time to switch to either
https://hg.osdn.net/view/vim/vim or http://hg.256bit.org/vim

Bitbucket has turned on read-only mode, so do not expect any new changes
from the bitbucket mirror. Syncing to Bitbucket still worked as of
8.2.1114 (which was pushed yesterday), but bitbucket has announced to
turn on read-only mode as of July 1st. So do not expect to get updates
from the bitbucket server.

In addition, I just have disabled the sync script to push to bitbucket.

Best,
Christian
--
Die großen Begebenheiten der Welt werden nicht gemacht, sondern sie
finden sich.
-- Georg Christoph Lichtenberg

[Bram Moolenaar]

Thanks for taking care of this, Christian.

Let me know if some links on the website need to be updated.

--
Friends? I have lots of friends! In fact, I have all episodes ever made.

[Tony Mechelynck]

I just checked my VimWiki tip,
https://vim.fandom.com/wiki/Getting_the_Vim_source_with_Mercurial and
it already mentioned http://hg.256bit.org/vim as the site "where to
clone from" so that's OK. Let me know if there's something else that
needs updating.

Best regards,
Tony.