The -o and -O options must be removed from the 2.5 release, because they
are too buggy to be fixed in the short term.

As mornfall said it:

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.

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).

The following patch updated issue issue1924 with status=resolved;resolvedin=2.5.0 CURRENT

* resolve issue1924: remove output options of obliterate 
Ignore-this: b85544067119c5c80db2ef449aea8456

The following patch updated issue issue1924 with status=resolved;resolvedin=2.8.0 HEAD

* resolve issue1924: remove output options of obliterate 
Ignore-this: b85544067119c5c80db2ef449aea8456

Hah, our infrastructure's pretty stupid isn't it?  (We pushed this to
HEAD after we pushed it to branch-2.5, so that's what we get).

Note that I've rolled this back in HEAD.  
Tsk. Unfortunately, I wasn't paying enough attention to keep the patch
log under 72 chars.

This is resolved, dear tracker. At least for all I can tell. Dear Issue 
Manager will hopefully clean up after me if I messed up, thanks!