[darcs-users] darcs patch blocked on new utf8-string, haskeline releases

Judah Jacobson judah.jacobson at gmail.com
Tue Nov 17 14:34:03 UTC 2009


On Tue, Nov 17, 2009 at 2:06 AM, Reinier Lamers <tux_rocker at reinier.de> wrote:
> Hi Eric, Judah,
>
> The current version of utf8-string (0.3.5) appears to contain a bug
> that is triggered by the unit tests for UTF-8 storage in darcs. I
> submitted a fix for that bug to utf8-string, and it has been included
> on its trunk now.
>
> We plan to do a new darcs release in late January, and it would be
> great if we could include UTF-8 storage in it. However, then we need
> to depend on a version of haskeline that is not yet released as we
> speak, that depends on the to-be-released utf8-string 0.3.6.
>
> In order to be able to merge in the UTF-8 storage soon, I'd like to
> ask you to release these new versions of utf8-string and haskeline
> some time these days, and let me know when you have done so. If this
> crosses some other plans of yours, please let me know.

Do you actually need a new release of Haskeline?  The latest release
of Haskeline (0.6.2.1) has the following constraint in its .cabal
file:

utf8-string==0.3.* && >=0.3.1.1,

So unless I'm missing something, I'd expect the existing release of
Haskeline to work fine with the future version of utf8-string that
you've described.

-Judah


More information about the darcs-users mailing list