Please add support for utf8-string 1.x

[peti]

We would like to update NixOS to the latest version of utf8-string, but unfortunately your package doesn't compile against the new version. Is there any chance of getting a quick update to remedy that issue?

[neilmayhew]

At the very least, the cabal file needs to specify a dependency on utf8-string < 1. It's not just NixOS that has problems. Any cabal package that depends indirectly on feed won't build without manual specification of the feed version.

[tolysz]

#10
Will add support for either(both?)

[bergmark]

I've added new revisions to all applicable versions on hackage with a utf8-string < 1 constraint.

[tolysz]

OT:
I guess some packages needs to have a community access... maybe IHG, or hackage trustees should have commit access to relevant git reopos (or should ask for it) once usage reaches certain level.

As creating the same package with the same name, but one which will be community managed would be a bit much.

But I guess, community driven libraries would be the best thing... no more 50 versions of the similar library.

[bergmark]

I don't expect that we'll force people to give us commit access to their repository, but we always have the option to maintain a fork under haskell-pkg-janitors.

I think maintainers will have to make this choice themselves, by allowing us or another person to be a backup maintainer with access to the repository and hackage (I try to make sure this is the case for all my packages).

[nomeata]

Having feed as part of Stackage would streamline the dependency management process a bit.

[nomeata]

It also blocks commercialhaskell/stackage#519

[bergmark]

I've taken over maintenance of this package and fixed this issue. The new repository location is http://github.com/bergmark/feed.