1. Migrating to Github
- Posted by ghaberek (admin) Apr 08, 2018
- 1977 views
- Last edited May 25, 2018
Update: I've migrated our Mercurial repos to GitHub!
I'm using fast-export to convert the Mercurial repos to Git and it seems to be working well so far.
Who owns this, _tom maybe? https://github.com/OpenEuphoria/ It looks like a user.
Can we convert it to an organization and the grant individual users (i.e. me) access instead?
https://help.github.com/articles/converting-a-user-into-an-organization/
-Greg
2. Re: Migrating to Github
- Posted by _tom (admin) Apr 09, 2018
- 1949 views
Github OpenEuphoria is mine. (I just have to find out where I put my password...)
_tom
3. Re: Migrating to Github
- Posted by _tom (admin) Apr 09, 2018
- 1875 views
I have sent the github particulars to you directly.
You are free to use this account in any way for OE.
_tom
4. Re: Migrating to Github
- Posted by ghaberek (admin) Apr 09, 2018
- 1932 views
I have sent the github particulars to you directly.
You are free to use this account in any way for OE.
_tom
I received your email(s). Not sure why you sent two though...
You can keep the account if you'd like. In fact, I'd recommend it since you've used your email address and you'll probably want to contribute to the project.
The page I linked to details how to do that here. Basically you just need to rename the account and that should free up the organization name for us to use.
Keep your personal user account and create a new organization manually
If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
- To retain your current user account name for your personal use, change the name of your personal user account to something new and wonderful.
- Create a new organization with the original name of your personal user account.
- Transfer your repositories to your new organization account.
You really only have to do step 1. I'll take care of the rest.
-Greg
5. Re: Migrating to Github
- Posted by ghaberek (admin) Apr 09, 2018
- 1912 views
I've got the organization set up now, thanks Tom!
I'm still working out a surprising number of build issues on the default branch. Once I get that worked out, I'll complete the migration to GitHub and do the 4.1 release there.
-Greg
6. Re: Migrating to Github
- Posted by ghaberek (admin) Apr 09, 2018
- 1872 views
I sent out a bunch of invitations earlier to join the organization. Anyone who has an existing GitHub account before I pull in the repo will help make the transition a little bit easier since I can match commit authors during the import process.
-Greg
7. Re: Migrating to Github
- Posted by SDPringle Apr 09, 2018
- 1860 views
I've got the organization set up now, thanks Tom!
I'm still working out a surprising number of build issues on the default branch. Once I get that worked out, I'll complete the migration to GitHub and do the 4.1 release there.
-Greg
I was trying to build the latest eui code from 32-bit Linux to 64-bit Linux and I got something that just seg faults on me. Maybe I need to build the latest 32-bit toolkit and build with that.
SD Pringle
8. Re: Migrating to Github
- Posted by ghaberek (admin) Apr 09, 2018
- 1832 views
I was trying to build the latest eui code from 32-bit Linux to 64-bit Linux and I got something that just seg faults on me. Maybe I need to build the latest 32-bit toolkit and build with that.
Hmm. I haven't tried that yet. Just building 64-bit with 64-bit on Windows for now.
Did this ever get fixed? http://openeuphoria.org/forum/123670.wc
That is, should the interpreter report system-vs-managed memory correctly?
I did a cursor search of the commit history and found nothing to that affect.
-Greg
9. Re: Migrating to Github
- Posted by ghaberek (admin) Apr 09, 2018
- 1824 views
Once I get that worked out, I'll complete the migration to GitHub and do the 4.1 release there.
Scratch that. We should release 4.1 first then migrate to GitHub. I don't want to let one side-track the other.
The deeper I dig back into the world of Euphoria development, the more I remember how tangled it all is. Good grief.
-Greg
10. Re: Migrating to Github
- Posted by ghaberek (admin) May 24, 2018
- 1676 views
- Last edited May 25, 2018
Scratch that. We should release 4.1 first then migrate to GitHub. I don't want to let one side-track the other.
No, scratch that. I've ported all of the repos from our local Mercurial repos to GitHub. Check it out!
https://github.com/OpenEuphoria
Edit: I've setup a redirect on the existing SCM page to kick those links over to the corresponding GitHub page.
e.g. http://scm.openeuphoria.org/hg/euphoria redirects to https://github.com/OpenEuphoria/euphoria
-Greg
11. Re: Migrating to Github
- Posted by SDPringle May 26, 2018
- 1628 views
I suppose you should disable the Mercurial service, as we shouldn't use it and it just makes sense to remove what we don't use from a security perspective generally speaking. Apart from that someone might forget that he needs to use Git now and commit to the wrong place.
By someone, I probably mean "me" in this case. :)
12. Re: Migrating to Github
- Posted by ghaberek (admin) May 26, 2018
- 1589 views
I suppose you should disable the Mercurial service, as we shouldn't use it and it just makes sense to remove what we don't use from a security perspective generally speaking. Apart from that someone might forget that he needs to use Git now and commit to the wrong place.
I did!
Edit: I've setup a redirect on the existing SCM page to kick those links over to the corresponding GitHub page.
e.g. http://scm.openeuphoria.org/hg/euphoria redirects to https://github.com/OpenEuphoria/euphoria
See?
hg clone http://scm.openeuphoria.org/hg/euphoria euphoria-hg abort: HTTP Error 406: Not Acceptable
Mercurial no longer works.
git clone http://scm.openeuphoria.org/hg/euphoria euphoria-git Cloning into 'euphoria-git'... remote: Counting objects: 41737, done. remote: Compressing objects: 100% (17151/17151), done. remote: Total 41737 (delta 25374), reused 40416 (delta 24056), pack-reused 0 Receiving objects: 100% (41737/41737), 135.33 MiB | 2.76 MiB/s, done. Resolving deltas: 100% (25374/25374), done. Checking connectivity... done. Checking out files: 100% (843/843), done.
But Git does work. This is just a redirect to GitHub.
-Greg
13. Re: Migrating to Github
- Posted by ghaberek (admin) May 26, 2018
- 1578 views
What's neat about doing this migration is that I was able to clean up spurious author names.
So instead of "Shawn Pringle" and "Shawn D. Pringle" all of your entries are now just "Shawn Pringle".
We were pretty much all guilty of having random slightly-off author names at one point or anther.
See a screenshot here: https://docs.google.com/uc?id=1jot-32a1HOClWnYoX4gq8NbjM8R9rlip
-Greg
14. Re: Migrating to Github
- Posted by ghaberek (admin) May 26, 2018
- 1659 views
Here's a good guide for learning Git for those of us coming from Mercurial: Git for longtime Mercurial users
-Greg