Phaedrus Leeds
Phaedrus Leeds
I don't know, get malware from another source I suppose?
> If Flatpak gets into a state where it needs to be repaired (e.g. if an install was interrupted), AppCenter fails to install or update Flatpaks until `flatpak repair` is...
possibly relevant to this: https://blogs.gnome.org/alexl/2018/09/17/flatpak-on-windows/
If I'm reading https://ahayzen.com/direct/flathub.html#downloadsbyflatpakstacked correctly, there are quite a few users on 1.0.3 still.
Looks like Debian's stretch-backports repo is still on 1.0.3: https://packages.debian.org/stretch-backports/flatpak
Stretch-backports has 1.0.4 now :tada:
As suggested above I added a `DeployCollectionID` field to flatpak{ref,repo}: https://github.com/flatpak/flatpak/pull/2329 I think we want this in addition to https://github.com/flatpak/flatpak/pull/2324. Otherwise we can't set a collection ID in those files...
Arguably we should also fix https://github.com/flatpak/flatpak/issues/2328 before doing this, especially if it would cause authentication pop-ups during background automatic updates (which is the behavior I'm seeing on my computer)
> Arguably we should also fix [flatpak/flatpak#2328](https://github.com/flatpak/flatpak/issues/2328) before doing this, especially if it would cause authentication pop-ups during background automatic updates (which is the behavior I'm seeing on my computer)...
So we could go ahead and set `ostree.deploy-collection-id` in the metadata and `DeployCollectionID` in the `flatpak{ref,repo}` files, with the consequences: - The 10% of users on 1.0.3 will see a...