Hi again,

unfortunately trying to reproduce issue1921, I ran in couple more
(fairly serious) bugs about darcs unpull -o where it produces busted
bundles. We may consider disabling it for the release.

Basically, passing any noninteractive matchers to unpull -o will make it
produce a partial and definitely wrong context, which then makes darcs
apply explode in a fancy firework. I have observed commutation failures
and bogus conflictors at least.

Yours,
   Petr.

PS: This is of course fixable, but I am not sure we want to delay the
release a week or more for this (i.e. I won't have time to fix this
sooner, so unless someone else steps up, I suggest just yanking the
-o/-O options from unpull on the release branch).

If I understand correctly, this is the same as a fetch -o bug (which I 
can't find on the tracker).

[I'm mostly testing a roundup here in my reply]

Can someone provide a test-case for this, I think I have it fixed, but 
I'd like to be sure (I cannot build a small failing test-case).

The following patch sent by Florent Becker <florent.becker@ens-lyon.org> updated issue issue1922 with
status=resolved;resolvedin=2.8.0 HEAD

* resolve issue1922: output correct context in darcs unpull -O 
Ignore-this: 741866c4a645edc0b43ba889fb4e965c