@minijackson Thanks for trying to fix this up.

Normally we don't completely overwrite packages this way, since someone will have to remember to undo it when it is updated upstream.

The first thing I'd suggest you do is to create an issue upstream asking for a new release. Normally package maintainers are pretty happy to make a new release for compatibility purposes.

If you make an issue on the upstream repo and the author doesn't reply, then we should try to fix this up in nixpkgs.

Normally we do it by just calling fetchpatch on a GitHub commit or PR that is implementing the compatibility fix upstream. There should be a few examples of people doing this in the configuration-common.nix file.

Oh, I just read the issue you linked to in the code.

I'd post a comment to that issue urging the author to make another release to Hackage.

However, if the author's decision is to not make any more releases to Hackage, than we have a separate way of supporting packages that aren't actually on hackage. You might want to take a quick look at the pkgs/development/haskell-modules/non-hackage-packages.nix file.

I guess another solution is to take over the package on Hackage and do the uploads in place of the actual author.

Are there any news about this endeavor? @minijackson, did you have any success convincing upstream to release a new version?

@peti I think you have as much information as I have, I haven't been contacting the maintainer of pandoc-sidenote, and I haven't seen a response in the aforementioned issue upstream

@minijackson Are you still interested in this?

On jez/pandoc-sidenote#14 (comment), the author of this package says that he'd be happy for someone to takeover this package on Hackage, so maybe you could contact the Hackage maintainers and ask to be added as a maintainer for this package? That would allow you to upload 0.20.0.0.

@cdepillabout Ah well, it'd be awesome, but I do not have nearly enough knowledge of Haskell, nor Pandoc / Pandoc-sidenote to do that, I'm merely just an end user ^^

The author released a new version to Hackage: https://hackage.haskell.org/package/pandoc-sidenote-0.22.1.0

In the next couple days, you may want to rebase this PR on haskell-updates and see if pandoc-sidenote now builds. If you have any trouble with this, please feel free to respond here.

(Also, saying thanks to the author on jez/pandoc-sidenote#14 would probably be a kind gesture!)

@minijackson All you need to do at this point is to revert the changes you made to configuration-common.nix, but leave the change to configuration-hackage2nix.yaml intact.

The version of pandoc-sidenote released on hackage is compatible with the version of pandoc in nixpkgs, so once it's not marked as broken anymore, it can at least be distributed to unstable.

Correct me if this is wrong, I'm relatively new to nix :)

This should be good now, sorry for the delay

Can confirm. Thank you!

Whoops, this should've gone to haskell-updates. I've cherry-picked this patch on top of that branch additionally.