3 ms·
You're right, I did mean the GNOME builder. I don't know what's wrong exactly, I think it's Flatpak related. From what I remember, it had something to do with
by jeroenhd 5y ago
You're right, I did mean the GNOME builder.
I don't know what's wrong exactly, I think it's Flatpak related. From what I remember, it had something to do with a certain version of the GNOME SDK not being installed (I think it was looking for a version of something that didn't exist?) so it failed a dependency check when I hit the install button from the Builder popup. I think this caused the tool to get into a faulty state where it thought the dependency was installed but simultaneously suggested installing the dependency, so it freaked out. I'm usually working on Ubuntu so combining the outdated Ubuntu stable-ish packages with Flatpak's bleeding edge stuff causes issues from time to time.
This could've been a temporary problem and I could've had a streak of bad luck, or maybe my deskop and laptop are somehow just set up plain wrong. I'm no expert in Flatpak internals. I also don't have Builder set up any more so reproducing the problem is kind of hard. Next time I'm giving it a try, I'll try to keep in mind to actually post a bug report.
- audidude 5y ago42 will be out in a couple weeks, and it has a lot of work to make flatpak stuff work better in the presence of "system" installations (rather than user installations where we normally install SDKs). Hope you'll try it out! (It's also available on Nightly).