Apache is stuck using Subversion ... so I've been using the Git/Svn integration built into Git for a while now. The good news is that most of the Git workflow comes with it ... you can create private branches, do local commits to your local repository, and build up a series of changes to dcommit ("delta commit") into SVN.
But that doesn't always work. For reasons I don't understand (given that there have been no other commits to SVN since I started work in my private branch), I keep getting the following error:
Applying: Provide the missing asset request handler for the virtual "stack" folder. Committing to https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk ... M tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ClasspathAssetAliasManagerImpl.java M tapestry-core/src/main/java/org/apache/tapestry5/services/LibraryMapping.java M tapestry-core/src/test/java/org/apache/tapestry5/internal/services/ClasspathAssetAliasManagerImplTest.java A tapestry-core/src/test/java/org/apache/tapestry5/services/LibraryMappingTest.java Committed r935569 W: 86533530aac8673a9e107e323de5201b7187270f and refs/remotes/origin/trunk differ, using rebase: :040000 040000 9c78596ee3f916f012c51d8927b4aa31d497f17b 8eb2b9b4f28e825e223c736eaa664bb53018258e M tapestry-core Current branch trunk is up to date. # of revisions changed before: 07b37e03cbc17012247d2221e795023c564d8228 0830b5f383dc94ae16088185efefac2e1358cf30 0bf378bcafc3f5372b67edc50d7de5bed8713cd0 95c87c5d7a2435df6bfced0d858bfdcb6ff26f22 3cd4ea4d9b225fd5013e1ce72cb9bac6d5b3e5e2 7b95d935099ebbbeb81845c1b8170a89d6ca6421 af310cfa9a5552aab2574c1e345b3beb049fb040 20805630fc67b83b4ca946b942716aeba4c80bef b3ef5e069942a30e2dce45a35e4be16382c0108d 1be75a15b7f203c927bc2aa34f43dda59ca968e3 555d94ebab122a688b7a1c0af253bf73609f88f5 729757eb3c35e14e126cb6ef16f5032d95d1cc4a 79dcfa32b291454bf9c652d635374d60638b8fb8 304d12f9d7d040f4dc231d213df663fcdf3863b6 0d626a7b0648735ab83bc7a2fd241390eb92e4e2 after: 86533530aac8673a9e107e323de5201b7187270f 07b37e03cbc17012247d2221e795023c564d8228 0830b5f383dc94ae16088185efefac2e1358cf30 0bf378bcafc3f5372b67edc50d7de5bed8713cd0 95c87c5d7a2435df6bfced0d858bfdcb6ff26f22 3cd4ea4d9b225fd5013e1ce72cb9bac6d5b3e5e2 7b95d935099ebbbeb81845c1b8170a89d6ca6421 af310cfa9a5552aab2574c1e345b3beb049fb040 20805630fc67b83b4ca946b942716aeba4c80bef b3ef5e069942a30e2dce45a35e4be16382c0108d 1be75a15b7f203c927bc2aa34f43dda59ca968e3 555d94ebab122a688b7a1c0af253bf73609f88f5 729757eb3c35e14e126cb6ef16f5032d95d1cc4a 79dcfa32b291454bf9c652d635374d60638b8fb8 304d12f9d7d040f4dc231d213df663fcdf3863b6 0d626a7b0648735ab83bc7a2fd241390eb92e4e2 If you are attempting to commit merges, try running: git rebase --interactive --preserve-merges refs/remotes/origin/trunk Before dcommitting ~/work/t5-project $
I did the right things; git co trunk followed by git svn rebase, then git rebase revised-assets-12apr2010. It claimed to replay my branch changes on top of the trunk branch, but regardless, the dcommit failed.
Doing some hunting around with Google, I found a partial explanation, that at least gives me a way forward. I'd still like to know how I got into this predicament.
At this point I just keep blindly entering the command: git reset --hard 705ccfb1e27d303a9db62de755b2fcfcca9a02f6 ; git svn rebase; git svn dcommit and get one Git commit further each time (that's the Git hash code for my final change in my original branch). Joy.
1 comment:
Ugh. Even after I got all those changes checked in, I'm still getting the mysterious error on every new dcommit, no matter how trivial. In desperation, I'm doing an svn pull, but I may need to blow away my local repository and start again.
Post a Comment