i3blocks-git has a maintainer. Maybe post a comment there also. However, there are reports that it fails to compile in the comments, so if this is true, then flag the package. If nothing happens after a while (~two weeks), submit an orphan request.
]]>Then whether you fork the upstream repo or just apply the patch in the PKGBUILD seems like a toss up for which is "better" - though the latter would seem easier to me.
]]>My first approach was to report the issue upstream, though it seems that the development has been dead for a few years. Someone even created a PR with the necessary fix and it has been pending since May 2020: https://github.com/vivien/i3blocks/pull/425
The way I see it, there are a few ways forward:
Fork the repo and add in the patch. Then create a new AUR package for my fork
Create new aur package for i3blocks and apply the patch via PKGBUILD
Adopt the existing i3blocks-git AUR package and apply patch (maintainer seems to have abandoned)
Which way is the best?
]]>