The following test script causes the result:

"darcs failed:  Error applying hunk to file ./t.t
Error applying patch to the working directory."

The script to reproduce it with a darcs-unstable build is:

#!/bin/sh

IFS='';
export IFS;
EMAIL=tester;
export EMAIL;

set -v;

rm -rf tmp;
darcs init --hashed --repodir=tmp
touch tmp/t.t
cd tmp
darcs add t.t
echo 'content'>t.t
darcs record -am 'initial add' --ignore
echo 'content: remote change'>t.t
darcs record -am 'remote change' --ignore
darcs put tmp2
cd tmp2
darcs obliterate --last 1 --all;
echo 'content: local change'> t.t
darcs pull -a ../
darcs w -s
darcs revert

Hi Mark,

Could you add this as a test in the bugs/ directory? (Sorry, I'm feeling
overwhelmed today.)  And thanks for the report!

David,

I've added this test to bugs/ now. It still fails with the build from yesterday
(2/13). The patches from 2/14 are still being compiled into a new binary.

The following patch updated the status of issue662 to be resolved in the unstable branch:

* resolved issue662: fix bug in bugs/pull.sh test, which now passes. 

You can view the patch details online here: 
http://darcs.net/cgi-bin/darcs.cgi/unstable/?c=annotate&p=20080215152814-72aca-4b9117f142f0d1903b1c2c27ad1a4c54c0c76cc1.gz

The following patch updated the status of issue662 to be resolved in the unstable branch:

* resolved issue662: fix bug in bugs/pull.sh test, which now passes. 

You can view the patch details online here: 
http://darcs.net/cgi-bin/darcs.cgi/unstable/?c=annotate&p=20080215152814-72aca-4b9117f142f0d1903b1c2c27ad1a4c54c0c76cc1.gz