LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Mercurial 4.6 or higher for 14.2 (https://www.linuxquestions.org/questions/slackware-14/mercurial-4-6-or-higher-for-14-2-a-4175659750/)

slackware-current 08-24-2019 05:21 PM
Mercurial 4.6 or higher for 14.2
 
Seem Bitbucket is dropping support for Mercurial this means 10 years of migrating code. For me that is about 51 active repo's
I would suggest slackware 14.2 upgrade to Mercurial 4.6 or higher.
or building it from current to make your migration easier.
Better to clone for migration with the newer version in order to get everything. Heads up.

GazL 08-26-2019 07:04 AM
I wonder how many repos won't get migrated/relocated and be lost forever because of this. :(

Moral of the story... when you put your data on other people's servers you give them control over your future! Think twice.

Richard Cranium 08-26-2019 03:39 PM
Quote:
Originally Posted by GazL (Post 6029611)
I wonder how many repos won't get migrated/relocated and be lost forever because of this. :(

Moral of the story... when you put your data on other people's servers you give them control over your future! Think twice.
Well, since Mercurial is a distributed version control system, any clone of those repos will be as good as another.

GazL 08-26-2019 04:08 PM
If there are any. You know what people are like when it comes to making backups.

Richard Cranium 08-26-2019 06:29 PM
Quote:
Originally Posted by GazL (Post 6029801)
If there are any. You know what people are like when it comes to making backups.
Well, if you are working on code under the control of a DVC system, you have a clone of the repository.

GazL 08-26-2019 08:04 PM
Quote:
Originally Posted by Richard Cranium (Post 6029846)
Well, if you are working on code under the control of a DVC system, you have a clone of the repository.
True, unless it's a repo that's not been worked on for a while and someone foolishly decided they didn't need to keep a copy of it because it's on bitbucket and they can just clone it again next time they need to work on it.

Richard Cranium 08-26-2019 10:41 PM
Quote:
Originally Posted by GazL (Post 6029883)
True, unless it's a repo that's not been worked on for a while and someone foolishly decided they didn't need to keep a copy of it because it's on bitbucket and they can just clone it again next time they need to work on it.
Well, fair enough.

I'll admit that I think I have freaking CVS checkouts on stuff that has been long dead (xconq comes to mind). I've even got larch/arch clones sitting around as well as some hg clones of stuff I did for a company that hasn't existed for 10 years or so.

I'll stipulate that it is more likely for there to be a number of out-of-date clones than no clones at all.

slackware-current 09-05-2019 01:22 PM
Thank you Richard it is a simple convert python script that rewrites HG to git need 4.6 or above. thank you for reply.
here is one for you.
Code:
Slackware package /tmp/git-2.23.0-x86_64-1.txz created.

bash-4.3# upgradepkg /tmp/git-2.23.0-x86_64-1.txz

Error:  there is no installed package named git-2.23.0-x86_64-1.
        (looking for /var/log/packages/git-2.23.0-x86_64-1)


bash-4.3# upgradepkg /tmp/git-2.23.0-x86_64-1.txz
You see this is the only stable tool we have right now with slackware. so any reason why pkgtool does not see this.
14.2 64.
I am just trying to control 15 years of code little help from team be nice.
my OP statement was a fact not a a chat thing ok.
Ok read the script it removes old ty.

Richard Cranium 09-05-2019 08:32 PM
Quote:
Originally Posted by slackware-current (Post 6033566)
Thank you Richard it is a simple convert python script that rewrites HG to git need 4.6 or above. thank you for reply.
here is one for you.
Code:
Slackware package /tmp/git-2.23.0-x86_64-1.txz created.

bash-4.3# upgradepkg /tmp/git-2.23.0-x86_64-1.txz

Error:  there is no installed package named git-2.23.0-x86_64-1.
        (looking for /var/log/packages/git-2.23.0-x86_64-1)


bash-4.3# upgradepkg /tmp/git-2.23.0-x86_64-1.txz
You see this is the only stable tool we have right now with slackware. so any reason why pkgtool does not see this.
14.2 64.
I am just trying to control 15 years of code little help from team be nice.
my OP statement was a fact not a a chat thing ok.
Ok read the script it removes old ty.

I'm not sure what you are asking me.

This will install your version of git if the old git package is not installed on your system.
Code:
upgradepkg --install-new /tmp/git-2.23.0-x86_64-1.txz

slackware-current 09-11-2019 09:36 PM
Sorry just making a point the python convert script requires Mercurial 4.6 and above that's all I was saying and the
stable slackware 14.2 version is below that and will not convert. I built installed 5.3 from current.

https://bitbucket.org/blog/sunsettin...t-in-bitbucket
hg fast-export requires Mercurial 4.6 or higher

https://github.com/frej/fast-export


All times are GMT -5. The time now is 03:21 AM.