flatpak-external-data-checker VS org.qutebrowser.qutebrowser

> Maybe. The CI rules should be made public in that case, though, surely? Maybe they are?

Agreed, but thankfully they are. The PRs link to <https://github.com/flathub/flatpak-external-data-checker>. That said, it'd be clearer if the flathubbot 'user' profile also linked to that URL.

> The enormous amount of value the distros bring [...] is audit of packages (and packaging).

Yes, auditing against supply chain attacks is good! But there's also a risk in running outdated software. I don't have easy answers. But if automation leaves more time for the hard part, great.

Flathub provides an excellent tool to keep your dependencies up to date, so it's just a matter of adding it to the manifests. Besides, who says 'dependencies not being updated enough' is a valid metric to determine the quality of a package? LOL.

According to Github issue/PR #126 new builds are failing because of a bug in flatpak-external-data-checker or some incompatibility between the two projects at least.

I'm surprised the documentation says that since Flathub itself runs its CLI scripts via Flatpak: https://github.com/flathub/flatpak-external-data-checker

Another thing you could add would be to tag your releases on GitHub, add a tag field next to the commit one, and add an x-checker-data section to the manifest so the Flathub bot will automatically open PRs to update the Flatpak release when you update your repository.

See f-e-d-c, and if you're not planing to submit to Flathub, then look at the GitHub workflow example there. Be aware that auto-merging is not acceptable for anything other than extra-data sources.

Unfortunately the maintainership of the Zoom Flatpak on Flathub has been a bit slow, but you can still install it since the Flathub bot do automatic builds whenever there's an update, thanks to the provided flatpak-external-data-checker service.

There is https://github.com/flathub/flatpak-external-data-checker which automatizes the update pull requests including dependencies. Flatpak has other downsides, but security or not getting the latest and greatest is not one of them.

> One thing I don't know about (which maybe somebody can inform me/us about): the wiki states that PRs are reviewed by Flathub reviewers, but I see no sign of human review on e.g. https://github.com/flathub/com.bitwarden.desktop/pull/167 (or others in that repo). What's the actual process?

In this case, I think the lack of human involvement is mostly a good thing. Flathub was criticised for having outdated packages[1]. Using automation to automatically update packages is mostly a good thing.

Obviously, we want to see thorough review of new packages, but that's a separate issue.

[1] I thought I read this in an LWN article, but I can't find it. But see e.g. https://github.com/flathub/org.qutebrowser.qutebrowser/issue...

If you're already testing the userscripts, any chance you can report here. I'm not using qutebrowser currently, so testing the userscripts is a bit lower on my to-do list.

Sorry if this is a duplicate post. I've been looking for a solution to this problem for a while now and I'm posting here because I haven't been able to find anything. I'm using the command :spawn mpv {hint-url} --ytdl-format="bestvideo[vcodec!=?vp9]+bestaudio/best" under a bind to move youtube videos into an mpv instance in order to bypass ads. However, I'm using the flatpak version of qutebrowser (as the version on apt is very far out of date -- I'm using Ubuntu), and when I try to use the bind to open a youtube video, I get the following error message: flatpak-spawn-wrapper: Please enable host access. For more details visit https://github.com/flathub/org.qutebrowser.qutebrowser/wiki I've tried using the command sudo flatpak override org.qutebrowser.qutebrowser --filesystem=host and rebooting, but after doing this, my browser throws the same error.

Probably relevant, if that's not you as well: alsa support? · Issue #126 · flathub/org.qutebrowser.qutebrowser

I don't understand what you're asking - you should find the permissions and such in the Flatpak YAML, no?

You might want to open an issue in the qutebrowser Flatpak repository asking for some documentation on how to get mpv to work - the maintainer there is usually quite responsive.

I think so, though I don't think I've ever tested it.