bvance Posted June 22, 2017 Report Share Posted June 22, 2017 Hi there, I'm trying to use gitsync to synchronize some local plastic repos distributed across my various workstations to one private github repository. My project has one submodule (some shared videogame systems I reuse across projects), which I have successfully pushed to github using gitsync.conf and an xlinked/gitsynced local repo. The problem I'm now encountering is that, when I do the following: 1) Make a fresh local repository and use gitsync to pull from my github repo (which works flawlessly), then... 2) Make some trivial change and attempt to push it back up to github... The push fails, giving me the following error message: "There was a problem unpacking: index-pack abnormal exit" Now, I have no idea why this might be happening. I've noticed, however, that there is a weird discrepancy between the place where I made the initial push and all the places I've attempted to pull it: these fresh repos include a .submodules file in the root of the workspace, while in the original repo no .submodules file exists. So I suppose I have two questions. Am I SUPPOSED to see the .submodules file in my local plastic repos after syncing with a git repo that contains a submodule (or is Plastic supposed to automagically hide that from me)? And of course, the bigger question: why isn't this shit working? I love Plastic and I hate git, but I am interested in open-sourcing some code of mine so this seemed like it'd be the best of both worlds. Really hoping I can get it running nicely. Link to comment Share on other sites More sharing options...
MattLT Posted May 23, 2020 Report Share Posted May 23, 2020 Same problem here, trying to GitSync Gitlab project repository with Plastic Cloud... Link to comment Share on other sites More sharing options...
calbzam Posted May 25, 2020 Report Share Posted May 25, 2020 Hi, - Could you enable the "cm" log and attach it? https://www.plasticscm.com/documentation/technical-articles/kb-enabling-logging-for-plastic-scm-part-i - Does the issue persist if you sync your Plastic repo agains a clean new git repo? - Does your Plastic repo incude big binary files? Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now