search

haskell-infra / hackage-trustees

Issue tracker for Hackage maintainance and trustee operations
https://hackage.haskell.org/packages/trustees/
42 stars 7 forks source link

polyparse incompatible with GHC 8.6 #186

Closed clinty closed 6 years ago

clinty commented 6 years ago
  1. Emailed Malcolm.Wallace@me.com on October 12
  2. n/a
  3. Try to build polyparse with GHC 8.6
  4. polyparse is a dependency of graphviz, thus graphviz is unbuildable with GHC 8.6 (https://github.com/ivan-m/graphviz/issues/39)
davean commented 6 years ago

I emailed him a patch on 13 October myself.

On Sat, Oct 20, 2018 at 8:56 PM clinty notifications@github.com wrote:

  1. Emailed Malcolm.Wallace@me.com on October 12
  2. n/a
  3. Try to build polyparse with GHC 8.6
  4. polyparse is a dependency of graphviz, thus graphviz is unbuildable with GHC 8.6 (ivan-m/graphviz#39 https://github.com/ivan-m/graphviz/issues/39)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/haskell-infra/hackage-trustees/issues/186, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOVy8SH7HebMQ-C864s2EJhhrE8d_IAks5um8ZHgaJpZM4XyNfw .

DanBurton commented 6 years ago

I also emailed Malcolm on Oct 22. (Before I knew at least 2 others had already done so.)

kozross commented 6 years ago

This also breaks HLint, as well as hdevtools - you can't build either of them with GHC 8.6 now either.

ndmitchell commented 6 years ago

I also sent Malcolm a WhatsApp 28 Sep, to which he replied (hoping to get to it that weekend), and 18 Oct (no response). I think we now meet all the guidelines to do a NMU? If so, can someone get permission - for example @peti who offered in https://github.com/ndmitchell/hlint/issues/530#issuecomment-431130883.

peti commented 6 years ago

https://mail.haskell.org/pipermail/libraries/2018-October/029120.html

phadej commented 6 years ago

NMUs done:

sboosali commented 6 years ago

@phadej ah, I also updated polyparse and HaXml (for 8.6). I was waiting for the author to reply to my emails (from a few months ago), so maybe I should have contacted the trustees more proactively to avoid the duplicate work.

(btw, I'm willing to take over maintainship of HaXml, if that's necessary).

hvr commented 6 years ago

@sboosali See also Malcolm's reply at https://mail.haskell.org/pipermail/libraries/2018-October/029145.html from which I don't infer he intends to give up maintainership

erikd commented 6 years ago

I suspect asking for co-maintainership leads to potentially better results with a higher level or reliability :)

sboosali commented 6 years ago

As I mentioned in an issue on haxr, I don't really want to or have time to. But, since @ (who does a lot already) had to update the package, which they wouldn't if the maintainer had or if I had contacted the trustees earlier... I felt bad and didn't want busier people to do things I had done (and will do).

On Mon, Nov 5, 2018, 00:05 Erik de Castro Lopo <notifications@github.com wrote:

I suspect asking for co-maintainership leads to potentially better results with a higher level or reliability :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haskell-infra/hackage-trustees/issues/186#issuecomment-435785955, or mute the thread https://github.com/notifications/unsubscribe-auth/ACNoMeP9A9pJjhXTbxh4VdGu1IfWSxTwks5ur_FlgaJpZM4XyNfw .

sboosali commented 6 years ago

also, I haven't received any replies from Malcolm (afaik) to my emails, which include patches (which I assume darcs can import easily, no?) for both polyparse and HaXml.

so, if anyone has their ear, can you tell them that I'm happy to work with them as much or as little as they want, but would prefer to be neither maintainer nor co-maintainer? i just really need the HaXml package, being a dependency of an XML RPC library (and will for the next few years, at least, for an important project).

(btw, since the author seems has been involved with Haskell for a long time, I suspected I might need to send an email to the listserv, which many people read (instead of, say, reddit, github, etc). however, iirc, I wasn't able to sign up (?), and so I put it back on my TODO list. ah well.)

On Tue, Nov 6, 2018, 02:52 Spiros Boosalis <samboosalis@gmail.com wrote:

As I mentioned in an issue on haxr, I don't really want to or have time to. But, since @ (who does a lot already) had to update the package, which they wouldn't if the maintainer had or if I had contacted the trustees earlier... I felt bad and didn't want busier people to do things I had done (and will do).

On Mon, Nov 5, 2018, 00:05 Erik de Castro Lopo <notifications@github.com wrote:

I suspect asking for co-maintainership leads to potentially better results with a higher level or reliability :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haskell-infra/hackage-trustees/issues/186#issuecomment-435785955, or mute the thread https://github.com/notifications/unsubscribe-auth/ACNoMeP9A9pJjhXTbxh4VdGu1IfWSxTwks5ur_FlgaJpZM4XyNfw .