Try bloody - git is further updated there. Thanks for the reproduction though. Time permitting I can try it on 020.
Dan Sent from my iPhone (typos, autocorrect, and all) > On May 5, 2017, at 12:20 AM, Rick Sayre <[email protected]> wrote: > > $ uname -a > SunOS mybox 5.11 omnios-r151020-4151d05 i86pc i386 i86pc > > $ git push > Counting objects: 7, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (7/7), done. > Writing objects: 100% (7/7), 627 bytes | 0 bytes/s, done. > Total 7 (delta 6), reused 0 (delta 0) > remote: error: object feec1f602cb04c13c661b24f1bbe06d53c17ba70: fullPathname: > contains full pathnames > remote: fatal: Error in object > error: unpack failed: index-pack abnormal exit > To https://github.com/whorfin/duktape.git > ! [remote rejected] master -> master (failed) > error: failed to push some refs to 'https://github.com/whorfin/duktape.git' > > $ git fsck > warning in tree feec1f602cb04c13c661b24f1bbe06d53c17ba70: fullPathname: > contains full pathnames > Checking object directories: 100% (256/256), done. > Checking objects: 100% (47718/47718), done. > > # nothing weird here > $ git rev-list --objects --all | grep feec1f602cb04c13c661b24f1bbe06d53c17ba70 > > May or may not be relevant - OpenSolaris issue reported at > http://stackoverflow.com/questions/30700947/git-fsck-error-contains-full-pathnames > > So the punchline is that running git on linux or lxss on windows works > fine. > > To reproduce: > fork duktape [if you're going to push] > https://github.com/svaarala/duktape > clone your fork or the above like so > $ git clone https://github.com/svaarala/duktape.git > $ cd duktape > #make an edit, in my case it was > $ vim config/platforms/platform_solaris.h.in > $ git commit -a > > # Now the bad news: > $ git fsck > # and you will see what I saw > $ git push # if you made your own fork > # also failtown > > Installed git is 2.10 on r151020. Same failure with 2.11 git from > Joyent/pkgin > > git 2.7.4 on Ubuntu 16.0.4 works fine > once the change/push was done on ubuntu, pulling down the forked and > changed repo shows an ok git fsck on OmniOS. i suspect a further change > will bork it again > > > Cheers > --Rick > _______________________________________________ > OmniOS-discuss mailing list > [email protected] > http://lists.omniti.com/mailman/listinfo/omnios-discuss _______________________________________________ OmniOS-discuss mailing list [email protected] http://lists.omniti.com/mailman/listinfo/omnios-discuss
