You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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.
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).
Activity
neilmayhew commentedon Jan 31, 2015
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 commentedon Feb 1, 2015
#10
Will add support for either(both?)
bergmark commentedon Feb 9, 2015
I've added new revisions to all applicable versions on hackage with a
utf8-string < 1constraint.tolysz commentedon Feb 9, 2015
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 commentedon Feb 9, 2015
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 commentedon Apr 3, 2015
Having
feedas part of Stackage would streamline the dependency management process a bit.nomeata commentedon Apr 3, 2015
It also blocks commercialhaskell/stackage#519
bergmark commentedon May 6, 2015
I've taken over maintenance of this package and fixed this issue. The new repository location is http://github.com/bergmark/feed.