gbaz

The package takeover process is for _unmaintained_ packages, not packages where the maintainer works at a pace that is too slow for the taste of some downstream users. That said,...

(further, if there is code from the forks mentioned which people have not contributed upstream -- then why not? maintainer is just a set of responsibilities coupled with certain authority/ops...

As I described, you make some PRs and prod for a response. Or make more serious efforts to contact the package maintainer. I'm glad this situation worked out well. But...

@avanov note that @jonathanjouty and @arybczak both have hackage upload rights as per the above discussion. You can contact either of them about prodding for a release as well

I'm willing to bet the custom flags set in ghci.conf cause the code to compile differently.

For now I'll close with a reference to https://github.com/haskell/haddock/issues/1451 Once that haddock is released, not sure what can be done outside of trying to regenerate a ton of old docs.

Actually -- hmm. It simply requires making sure the following little bit is in the css of the bundled haddocks: https://github.com/haskell/haddock/pull/1486/files I think we can try to dynamically rewrite the...

There's some rough code here that shows how to do it: https://github.com/haskell/hackage-server/commit/bc903d36955b52656ea4db246e000710c3c00709

On the contrary, we have ongoing gsoc work right now and I was hoping that @AliasQli would find time to look at this.

It shouldn't be creating a lockfile, no. Those files are afaik created and managed by the acid-state library (https://github.com/acid-state/acid-state/search?q=open.lock) and perhaps the snapshot you're using is built against an older...