Bitbucket ends mercurial support
Bitbucket ends mercurial support
https://bitbucket.org/blog/sunsetting-m ... -bitbucket
Most of the old LuxRender repositories use mercurial: https://bitbucket.org/account/user/luxr ... jects/PROJ
We could consider porting them to git, either on bitbucket or on our new github project.
Most of the old LuxRender repositories use mercurial: https://bitbucket.org/account/user/luxr ... jects/PROJ
We could consider porting them to git, either on bitbucket or on our new github project.
Re: Bitbucket ends mercurial support
That would be a good thing, I think.
From some initial test I did locally, conversion is not totally painless...
Re: Bitbucket ends mercurial support
I did the migration to GitHub at one point but the idea was than rejected. I have kept https://github.com/orgs/LuxRender/dashboard exactly for this task. The problem was in large binary files stored in original mercurial repositories.
But the only repositories that may be a good idea to save are the one with sources. The one with binaries for Windows/Linux/MacOS are so outdated we can probably trash them.
Acasta69, if you want to try to do the migration to https://github.com/orgs/LuxRender, I can give you admin rights.
P.S. the mercurial repositories are here: https://bitbucket.org/%7B019a5fcb-cfaf- ... 000916%7D/
Re: Bitbucket ends mercurial support
OK, I'll look into that.Dade wrote: ↑Fri Jan 24, 2020 11:02 am Acasta69, if you want to try to do the migration to https://github.com/orgs/LuxRender, I can give you admin rights.
Re: Bitbucket ends mercurial support
After some tests, it seems that the hg-fast-export tool works fine.
The plain conversion command produces some errors:
The latter refers to deleted branches in the mercurial repos, which git cannot interpret correctly.
Using --force gets rid of the errors and the resulting git repository is apparently ok (I've tried lux and luxrays at the moment).
In next days I'll upload these so that anyone can check if they want, and proceed with other conversions.
The plain conversion command produces some errors:
Code: Select all
$ ../../fast-export-master/hg-fast-export.sh -r ../../luxrender/luxtest
Error: The option core.ignoreCase is set to true in the git
repository. This will produce empty changesets for renames that just
change the case of the file name.
Use --force to skip this check or change the option with
git config core.ignoreCase false
Code: Select all
Error: repository has at least one unnamed head: hg r3113
Using --force gets rid of the errors and the resulting git repository is apparently ok (I've tried lux and luxrays at the moment).
In next days I'll upload these so that anyone can check if they want, and proceed with other conversions.
Re: Bitbucket ends mercurial support
Great work, thanks a lot Alessandro!
Re: Bitbucket ends mercurial support
At the moment I have uploaded the following repos:
If anyone wants to check and finds something wrong, let me know and I'll try to fix it.
Also note that I uploaded the contents of the previous Mercurial repos as they are. For example I did not convert .hgignore files to .gitignore. I guess this can be enough for a reference copy, but tell if you think otherwise.
The simplest would be to port everything, if we have no storage problems.
For the linux_deps and windows_deps we have three choices:
- Lux
- LuxRays
- Windows
- Linux
If anyone wants to check and finds something wrong, let me know and I'll try to fix it.
Also note that I uploaded the contents of the previous Mercurial repos as they are. For example I did not convert .hgignore files to .gitignore. I guess this can be enough for a reference copy, but tell if you think otherwise.
The MacOS version had only one repo for compilation environment and binaries, it weighs approx 1 GB total in the mercurial version.
The simplest would be to port everything, if we have no storage problems.
For the linux_deps and windows_deps we have three choices:
- discard them as Dade suggested;
- keep them on BitBucket, if possible: they are already in git format, so they should not be deleted;
- or try to upload only a binary file, to keep a reference of the last-working deps but save some storage.
Re: Bitbucket ends mercurial support
Update about ported repos:
Dade, if you agree, could you please delete them? I don't have the rights to do that. They are:
I have made a local copy, so if you change your mind I can always upload them.
- LuxBlend25 / LuxBlend
- LuxMark
- Other exporters (Su2Lux, LuxMaya, etc.)
- TestSuite
Dade, if you agree, could you please delete them? I don't have the rights to do that. They are:
- LuxMax
- LuxMax-old-version-archived
- LuxFire
- LuxViewer
- AzureRender
- Windows_Installer
I have made a local copy, so if you change your mind I can always upload them.
Re: Bitbucket ends mercurial support
I don't really remember the difference between the various repositories but I would just rename them (i.e. it costs nothing).acasta69 wrote: ↑Mon Feb 10, 2020 2:47 pm About LuxMax exporter: there are already 2 old repos because of previous activity. Saving the last status would mean creating the third one. What do you think of deleting the existing so to have only the last version?
Dade, if you agree, could you please delete them? I don't have the rights to do that. They are:
- LuxMax
- LuxMax-old-version-archived
Re: Bitbucket ends mercurial support
Thank you for your efforts Alessandro!