Hi Simon, Eric, Eric: good to know it wasn't my lack of darcs-foo Simon: that did the trick, it's all done now.
Thanks again, Axel On 25.05.2010, at 11:06, Simon Marlow wrote: > On 24/05/2010 21:00, Axel Simon wrote: >> Hi darcs gurus, hi Duncan, >> >> I'm stuck! I've just tried to separate the Gtk2Hs repo on >> code.haskell.org into it's constituent libraries. What we want is to >> extract some of the libraries that Gtk2Hs provides into their own >> repositories without loosing their history. The problem is that darcs >> will only checkout a directory that does not yet exist. So I've >> tried: >> >> sim...@nun:/srv/code/webkit$ darcs get --lazy /srv/code/gtk2hs >> Finished getting. >> sim...@nun:/srv/code/webkit$ mv gtk2hs/_darcs . >> sim...@nun:/srv/code/webkit$ mv gtk2hs/webkit . >> sim...@nun:/srv/code/webkit$ darcs mv webkit/* . >> sim...@nun:/srv/code/webkit$ rmdir webkit/ >> sim...@nun:/srv/code/webkit$ rm -rf gtk2hs/ >> sim...@nun:/srv/code/webkit$ darcs record >> >> This seems to work great: webkit only contains the files it should >> and >> recording the patch gives me exactly the movements of the webkit >> files >> one level up and the removal of all other files. However, when I >> check >> out on my local computer I get: >> >> ~/source as49$ darcs get sim...@code.haskell.org:/srv/code/webkit >> Copying patches, to get lazy repository hit ctrl-C... >> >> darcs failed: Couldn't fetch `0000001146- >> ffed5fe22fabf1987787fe71d2c6c2e3a06d53e176e52bad3112d8bba73f9440' >> in subdir patches from sources: >> >> thisrepo:/Users/as49/source/webkit >> repo:sim...@code.haskell.org:/srv/code/webkit >> repo:/srv/code/gtk2hs >> thisrepo:/srv/code/webkit/gtk2hs >> >> I *think* what this means is that darcs on code.haskell.org tries to >> pull more patches from the original repo but fails to do so (even >> though I used absolute path names). > > The problem is that when you did a "get" on code.haskell.org, the > other repo was /srv/code/gtk2hs, and now that you're on a different > machine that path is no longer accessible. > > Either use non-lazy repositories, or pull down the whole gtk2hs > repository locally so that all the patches end up in your local > cache (~/.darcs/cache). Non-lazy repos aren't as bad as they seem, > because darcs hard-links all the patch files together. > > Cheers, > Simon > > ------------------------------------------------------------------------------ _______________________________________________ Gtk2hs-devel mailing list Gtk2hs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk2hs-devel
