Olek Wojnar

This is currently not building correctly because of old code in Google Bazel Common. Once a [pending PR](https://github.com/google/bazel-common/pull/113) is accepted, a build against Google Bazel Common HEAD should succeed.

As an alternative, you could also manually define workspace rules instead of loading the clearly very outdated ones from the google_bazel_common project.

@Berkmann18 From what I understand, the CLI has a node dependency. It would be nice to just do this in GitLab without the additional dependency.

@Berkmann18 I try to have as little extraneous software as possible on my development machine. Therefore being able to use this functionality directly in GitLab would be very helpful.

I submitted my own Support Ticket with Mainframe (6736) and referenced @hsmalley's as well. I went through my Proton error log and I match OP on the first 20 but...

> @hsmalley how did you acquire these debug logs? You can also use this launch option in Steam to get a nice Proton error log conveniently deposited in your home...

I'm not sure how much of this is a Proton issue and how much of this is a developer-unwilling-to-make-any-effort-for-Proton-support issue. I'm opening another ticket to ask for a timeline for...

Additional data point: the Pax Dei update on September 5th finally allowed me to start the game! But only with GE Proton 9-12. Proton Experimental still crashes on boot. Perhaps...

Ok, today's Proton Experimental update works now! Well, at least it doesn't crash on boot anymore.

@TomAFrench It looks like you just need to do a MR to [F-Droid](https://gitlab.com/fdroid/fdroiddata) as described in their [submittal guide](https://f-droid.org/docs/Submitting_to_F-Droid_Quick_Start_Guide/). They seem to make it pretty developer-friendly. 🙂