refi64

> Our git handling is extremely messy and includes terrible hacks, i.e. dynamic package.json patching at build time. I mean, we're also building the entire internal cache representation from scratch,...

> IMO it does. Massive jq-driven build-time patches are significantly more complex (and probably prone to break) than plain and simple flatpak-builder sources that don't need any post-processing. Fair, tbh...

Afaik on Fedora, Arch, and Ubuntu, bwrap doesn't run as setuid root and instead relies solely on user namespaces. On Sat, Oct 12, 2019, 5:43 PM madaidan wrote: > bubblewrap...

Super late to this, but @Kaurin are sure sure Atom closed fully? Some editors like to stay running in the background, and when you "start" it you just bring the...

Off the top of my head, I recall this happening once and I had to run `reset` to fix it, my best guess was that something else left the terminal...

This reminds me of #4127, can you try `sudo flatpak repair --system` and/or `flatpak repair --user` and see if it fixes it?

Ok, so I'm going to propose something a bit different to solve this. The standing issues with simply adding local checkouts and factoring in uncommitted changes are: - It requires...

hmm the CI failures seem unrelated? ``` [#] docker start 2bc1b0ae0db1e203e180da06a86cd383b8b76472feeead435e2cc35f216f8023 2bc1b0ae0db1e203e180da06a86cd3[83](https://github.com/tonarino/innernet/actions/runs/5361835266/jobs/9728189885?pr=273#step:4:84)b8b76472feeead435e2cc35f216f8023 DEBUG wireguard_control::backends::kernel > get_by_name: got 1 response message(s) from netlink request DEBUG wireguard_control::backends::kernel > get_by_name: parsed wireguard device...

> Do you think it's worth the hassle to do this context copying compared to, say, only allowing overwriting /etc/hosts in-place if SELinux is detected? IMO yes: SELinux-enabled is the...

whoops looks like this fell off my radar, all comments should be fixed now.