You can cut/paste the following in (instead of the attached script): -- mkdir darcs_test && cd darcs_test mkdir repo && cd repo darcs init touch one two darcs add one two darcs record -a --author "[email protected]" -m "one" one darcs record -a --author "[email protected]" -m "two" two cd .. darcs get repo repo_0 darcs get repo repo_1 cd repo_0 darcs query repo echo -n yd | darcs unpull cd .. cd repo_1 darcs push -a ../repo_0 --
It would seem that this is an issue with our binaries, as running this on a fedora machine actually works, so perhaps (hopefully) this is an isolated issue. TIA. -lev On Aug 25, 2010, at 2:47 PM, Lev Lvovsky wrote: > Hello, > > Some background, we're trying to upgrade from a darcs-1 repo to darcs-2. > That isn't the problem so much as an issue that it has helped us oncover with > darcs v.2 in general. > > I'm attaching a cleaned-up typescript to fully explain the order of > operations, however, it can briefly be explained w/o commands: > > 1. intialize a repo > 2. create two blank files in the repo > 3. add those two files to the repo one at a time (two distinct patches) > 4. do a 'darcs get' of that repo twice, resulting in two pristine copies of > the initial repo > 5. change dir into one of the copies and 'darcs unpull' the latest patch > from that repo. It should have only one left. > 6. change dir to the other "pristine" repo (which should have all two > patches still), and try pushing to the repo you were just in > 7. you should see a single pending patch > > This is where our problem occurs - in pushing that patch, we get an error > similar to this: > > darcs-2.4.4: fd:7: hPutBuf: resource vanished (Broken pipe) > > We simply cannot push to this repository. Pulling on the other hand, works > just fine. > > I've tried this with several versions of darcs, ranging from 2.0.2, 2.3.0, to > the latest available binary, 2.4.4. This is all performed on linux machines. > > In trying this on an OSX box with version 2.0.0, I cannot reproduce this > error. > > Any advice - including "file a bug report", which I intend to do once I make > sure this isn't user error - would be appreciated. > > thanks, > -lev > > > <typescript>_______________________________________________ > darcs-users mailing list > [email protected] > http://lists.osuosl.org/mailman/listinfo/darcs-users _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
