New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/24984#issuecomment-696665008

Comment:
Sure it sounds better. But I see one random user on the internet claiming breakage (two, if you didn't also file the upstream report). How do I know you didn't misconfigure something? How do I know your patch doesn't have side effects? I've never used picard and hadn't even heard about it until reading your report.

Void defers to upstream. Whenever possible, we try not to maintain unofficial patches because it gets unwieldy. Either wait until upstream sanctions the patch by merging it (we will patch with upstream fixes that haven't yet been released, if they fix known issues), or hope another package committer uses picard and is willing to sign off on the unofficial patch.

You can maintain the patched package in your own repo until then.

> On Sep 22, 2020, at 4:29 AM, eater <notifications@github.com> wrote:
> 
> 
> we currently have a functionally broken package in our repo, having a minimally intrusive fix sounds better to than just keeping it around broken
> 
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or unsubscribe.