I helped fix a bug in early 2015, the author decided to re-roll a tarball with the same name rather than push a new version. I wasn't too concerned because I assumed another version (including the fix) would come out shortly afterwards. Unfortunately, it hasn't and I ran into the issue again today.
Since this is predominantly a mirror/manifest update, I don't believe it requires the upstream maintainer to update it and have assigned it directly to media-video (and CCed in the upstream maintainer) instead.
Please could this package's manifest (and associated mirrored tarball) be updated appropriately, or the patch applied separately? Since the ebuild is EAPI=5, it doesn't require the application of user_patches, so it's not an issue that's overly easy to work around...
Ping, there's been no activity on this for nearly two months. Could someone from media-video please check that the proxy-maintainer is still active (and if not, regenerate the manifests to match upstream's tarball)?