fast-export | A mercurial to git converter using git-fast-import | Code Editor library

by frej Python Version: v221024 License: No License

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | fast-export Summary

fast-export is a Python library typically used in Editor, Code Editor applications. fast-export has no bugs, it has no vulnerabilities and it has medium support. However fast-export build file is not available. You can download it from GitHub.

hg-fast-export.sh - mercurial to git converter using git-fast-import.

Support

Quality

Security

License

Reuse

Support

fast-export has a medium active ecosystem.

It has 778 star(s) with 246 fork(s). There are 31 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 176 have been closed. On average issues are closed in 97 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of fast-export is v221024

Quality

fast-export has 0 bugs and 0 code smells.

Security

fast-export has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fast-export code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fast-export does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

fast-export releases are available to install and integrate.

fast-export has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

fast-export saves you 469 person hours of effort in developing the same functionality from scratch.

It has 1112 lines of code, 104 functions and 13 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed fast-export and discovered the below as its top functions. This is intended to give you an instant insight into fast-export implemented functionality, and help decide if they suit your requirements.

Convert hg to git
Export a commit
Export file contents
Setup a repository
Check if count commits after commit
Load a mapping from a file
Filter the commit message based on the commit
Get all of the branches in the given repo
Get a list of tags from the git repository
Setup the repository

Get all kandi verified functions for this library.

fast-export Key Features

No Key Features are available at this moment for fast-export.

fast-export Examples and Code Snippets

No Code Snippets are available at this moment for fast-export.

Community Discussions

Trending Discussions on fast-export

CVS to GIT in Centos8

Git-svn failed with update-ref HEAD refs/remotes/origin/trunk: command returned error: 128

KDE SVN2GIT "WARN: Branch ... in repository ... doesn't exist at revision ... -- did you resume from the wrong revision?" Can't continue

untracked and deleted at the same time (git)

QUESTION

CVS to GIT in Centos8

Asked 2021-Dec-16 at 23:51

cvsimport is missing in Centos8. Unable to install. Now I tried to use fast-import. Most of the repos it is okay but it fails with some repo which has binary files. I think there is a bug in cvs-fast-export

...

ANSWER

Answered 2021-Dec-16 at 14:38

Posting solution based on comment exchange above in original question

I suggest trying cvs2git.

@RamananT says

I Tried and unfortunately cvs2git also failed with this error ERROR: The command 'cvs -Q -f -d :local:/home/user/path/to/cvs/repo/proj co -r1.1.1.2.1 -p -kb scripts/additions/320_str.20070501-001101.sql' failed with exit status=-9 and no output.

I then suggested

You could try that command yourself to see if the ,v file is somehow corrupted. The stored sql file it is a text file, but the .sq,v file is in RCS format and you would not be able to tell by inspection if it was corrupted or not. But you could fairly easily

run the cvs command that cvs2git says fails and see if it fails for you when run manually. Or
you could make a copy of the repo, remove that one file, and try cvs2git on that. That would also show you if that particular file is indeed a problem.

Thanks @mort, that made wonders. If it is an answer I would accept this solution. The issue is just on that file. I didn't investigate the issue but just deleted and carried on

Source https://stackoverflow.com/questions/70028962

QUESTION

Git-svn failed with update-ref HEAD refs/remotes/origin/trunk: command returned error: 128

Asked 2020-Dec-14 at 10:16

I'm trying to do a migration of a 14.4k commit and 12 years old project from SVN to git.

As this is the tool that comes first when doing a basic browser research I tried to do it with git-svn. As it is really big I tried to do the migration from just a recent history like so :

...

ANSWER

Answered 2020-Dec-11 at 16:55

Was I suppose to somehow resume the command that failed ?

Yes, try git svn fetch. This will resume it, exactly.

Basically, git svn clone = git svn init followed by git svn fetch. (Quite similarly to how git clone itself is a git init, followed by adding a remote named by default origin, followed by git fetch.)

In my experience with git-svn, certain amount of fiddling around with .git/config, and understanding the differences between refs and remotes, is often needed to get it working as you expect.

Usually, git-svn is the remote which stands for the remote SVN server you're accessing through the git-svn "adapter". Hypothetically, due to DVCS nature, you could have a Git repo with 3 remotes:

lab-server
cloud-archive
git-svn (or, perhaps better renamed as e.g. svn-legacy)

Seeing an origin remote in your error messages tells me you probably got confused at some point, and said git clone instead of git svn clone. My advice would be to figure out the basics and obtain a clear mental model of what you're doing. Documentation and .git/config may help with that.

Source https://stackoverflow.com/questions/65218724

QUESTION

KDE SVN2GIT "WARN: Branch ... in repository ... doesn't exist at revision ... -- did you resume from the wrong revision?" Can't continue

Asked 2020-Jul-14 at 21:48

I'm trying to migrate an 11GB SVN repo with over than 24k revisions inside to a single GIT repository.

I did a single file dump of the SVN using svnrdump command and load it into my local SVN server, placed on my MacBook machine.

I downloaded the svn2git from the https://github.com/svn-all-fast-export/svn2git repository.

Due to differences in the way how SVN and GIT handle tags, I used a merged-branches-tags.rules from the svn2git sample directory, which look like this (I've removed comments): create repository myproject end repository

...

ANSWER

Answered 2020-Jul-14 at 21:48

After a further investigation, it turns out that the mentioned "7.0M0p0000" tag was created in the rev 12601 as a copy of all the tags from rev 12600.

I've found it in the dump file, created using this command:

Source https://stackoverflow.com/questions/62895960

QUESTION

untracked and deleted at the same time (git)

Asked 2020-Jun-25 at 15:47

I have converted an old hg repository into git with hg-fast-export.sh. Then I've copied the .git directory into the server filesystem. I would expect git to recognize that all the files are the same as expected. Instead git complains that all the files are both deleted and untracked. For example:

...

ANSWER

Answered 2020-Jun-25 at 15:47

It's not clear to me why the file is showing up as "to be deleted" (note that it's not deleted yet, it is to be deleted instead) but the rest of the output is quite normal: it just means that somehow, you have told Git that the next commit you plan to make should omit the file base.html.

To fix this, use the advice shown by Git itself above:

Source https://stackoverflow.com/questions/62569181

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fast-export

You can download it from GitHub.
You can use fast-export like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: