Sergei von Alis

Ah, looks like now I get it. So, the problem is that Docker creates bridges (in host namespace) with random names?

I've looked into packaging ProtonVPN Linux app in Flatpak. It mostly works, thanks to relying on NetworkManager, which is largely usable from within Flatpak sandbox. However, there are some obstacles....

This is an error, but what causes it is still not clear. We've seen this happening with GitHub API, then with Gnome's `cache.json`, now this with PyPI - it's not...

The only way I see to work around this issue is to store source version in the manifest, and actually compare it with the new version.

In the log there are errors like this: >`ERROR src.manifest: Failed to check archive akregator/akregator-22.04.2.tar.xz with AnityaChecker: Wrong content type 'text/plain' received from 'https://download.kde.org/stable/release-service/22.04.3/src/akregator-22.04.3.tar.xz'` It indicates a broken or outdated...

It can be disabled by setting `"disable-external-data-checker": true` in `flathub.json`. From the way you put it, I suppose the maintainers are AFK currently?

GitChecker is for git tags, it doesn't know anything about releases. If you want to track Github/Gitlab releases, use JSONChecker instead.

While this feature is surely something we'd like to have, it's not trivial to implement in a reliable way. @sophie-h In the Telegram flatpak repo, the default branch is `beta`...

JSONC is a different standard. It seems mostly compatible with normal-json-with-C-style-comments, but relying on this unintended compatibility seems like a bad idea, adding risk to write a json file that...

Actually, your proposal (to add jsonc support to json-glib) is better than mine. We probably couldn't use json-glib to _write_ files, since its semantics are way too different from python...