I'm marking this as urgent because darcs reports this as a bug itself, and it's
rather easy to trigger with the current darcs-unstable. 

#!/bin/sh

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

set -ev;

rm -rf tmp;
darcs init --darcs-2 --repodir=tmp
touch tmp/t.t
cd tmp
darcs add t.t
echo 'content'>t.t
darcs record -am 'initial add'
echo 'remote change'>t.t
darcs record -am 'remote change'
darcs put tmp2

####

Result is: 

darcs failed:  Malformed patch bundle: 'hunk ./t.t 1' is not 'Context:'

+content

Context:

Patch bundle hash:
5818289a101f72e75fbbb0caf2475b58ef48bf86

Apply failed!

shell returned 2

I'll add the only the --darcs-2 format fails this test. Both the old format and
the --hashed format pass.

On Fri, Feb 08, 2008 at 03:59:27AM -0000, Mark Stosberg wrote:
> I'll add the only the --darcs-2 format fails this test. Both the old format and
> the --hashed format pass.

It looks like put isn't passing the correct flags to darcs initialize to
set up the right sort of repository.

David

I'm just now pushing a patch to fix this bug.

Is this related to new, not-fixed issue1217?

Resolving as issue1255 was also resolved.