go-dialog issueshttps://0xacab.org/leap/go-dialog/-/issues2019-02-28T18:15:09Zhttps://0xacab.org/leap/go-dialog/-/issues/1merge changes back upstream2019-02-28T18:15:09Zanarcatmerge changes back upstreamA year ago, upstream expressed skepticism at porting their code to GTK3, in [this bug report](https://github.com/sqweek/dialog/issues/4). Or at least, they said clearly they wouldn't support *both* GTK2 and GTK3 and said they would prefe...A year ago, upstream expressed skepticism at porting their code to GTK3, in [this bug report](https://github.com/sqweek/dialog/issues/4). Or at least, they said clearly they wouldn't support *both* GTK2 and GTK3 and said they would prefer supporting GTK2 for now because "gtk2 remains more common on linux distros".
I think it's time to review that assertion: GTK2 is going away on many Linux distribution and GTK3 is certainly shipped everywhere. Therefore, the changes here should be proposed back upstream to resolve this fork.
This is blocking Debian packaging: we don't want to package an ephemeral fork and would prefer to stick with the official package, unless *this* because the official "dialog" go client that everyone uses.RiseupVPN 0.19.6meskiomeskio