It’s been a while since I’ve last posted but I have returned with the story of my work on the Github desktop Flatpak. If you haven’t figured out by the title this is going to be a two-parter. The first part(what you’re reading now) is going to be up to submitting the Flatpak to flathub. The second part will be about fixing issues after getting on flathub.
Well, let’s start with what a “Flatpak” is. A Flatpak is a Linux distribution agnostic package format. It works on almost any Linux distribution with little to work beyond building or installing it. In May this year, I gave a friend of mine an open offer, name one app and I’ll Flatpak it. After a while, they came back requesting Github Desktop. I had just Flatpaked GitAhead another git frontend a few week priors.
Naively I thought it shouldn’t be hard to package it, after all, I’ve had experience turning another git manager into a Flatpak. I was wrong, very very wrong. When I started the first thing I did was check if someone else was working on a Flatpak, if you are planning on Flatpaking an app make sure no one else is doing it as well. If someone else is you should consider contributing to their effort.
In late 2020 Damián Nohales had attempted to do this but failed due to issues with electron interacting with the Flatpak sandbox. I knew about these issues from working on another Flatpak. The issue stems from electron’s sandbox being a suid(Set Uid) binary that can become root on start. Flatpak blocks this due to security issues. There are 2 ways to fix this, the first one is to launch the application with the flag
--nosandbox which impacts the security of the application and in some cases can break them.
The other smarter method is zypak a reimplementation of the chromium/electron sandbox that uses Flatpaks sandbox negating the need for the flag
--nosandbox. Using this knowledge I was able to modify Damián’s attempt at a Flatpak to attempt to get it to run. I was able to update to the latest release. Right away a new issue cropped up, I couldn’t log into Github desktop. Eventually, I gave up a took a break from this project.
It wasn’t until June where I started working on this again. I attempted to bump to the latest release and things broke hard. First I needed to update the node version, Damián had used node 10 which now was incompatible. I ended up going with node 14 instead. After a day of getting things working again, I had hit a new issue. At some point, a new dependency was added.
node-detect-arm64-translation this one dependency stumped me for weeks. Eventually, I asked Brendan Forster the maintainer of the Linux fork of Github desktop what it did and if I could “patch it out”. After getting the okay, I wrote a patch removing it completely. It was ugly but did its job allowing me to continue. The yarn generator was later updated to setup the repo as a tarball that yarn could use directly allowing me to drop all patches.
Finally, that left me with one issue. The login still didn’t work, I didn’t know why and had no idea how to debug it. Eventually, I asked the Flatpak matrix for ideas. It turns out the solution was adding
%U to the desktop file’s
%U tells your desktop environment that the executable takes args and where positionally to add them.
Finally with the major blocker out of the way. I began adding Flatpak specific functionality, support for spawning programs outside the sandbox, fixing issues with trashing files(the issue is not technically fixed but the issue is on the portal side not mine). After this, I managed to get it on Flathub, but that was not the end of my woes with Github desktop but that’s a post for another time.
– signing off