mirror of
https://github.com/flatpak/flatpak.git
synced 2026-03-27 11:22:00 -04:00
11158c2481
All the details of the bug are in: https://github.com/ostreedev/ostree/pull/2549 https://github.com/flatpak/flatpak/issues/3479 This patch works around it by marking the commit we're about to pull partial, so that if the .commit object exists in a staging directory from a previous failed pull, it will not be erroneously considered a complete commit, even by affected versions of libostree that don't have the above patch. If for some reason the commit in the staging dir is complete, libostree should harmlessly verify that and pull it in. Usually the commit we are pulling does not already exist in the local repo, but add a check anyway so we don't risk marking a complete commit as partial, and so this works on the code path from "flatpak install --reinstall ..." Fixes #3479
Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux.
See https://flatpak.org/ for more information.
Community discussion happens in #flatpak:matrix.org, on the mailing list, and on the Flathub Discourse.
Read documentation for Flatpak here.
Contributing
Flatpak welcomes contributions from anyone! Here are some ways you can help:
- Fix one of the issues and submit a PR
- Update flatpak's translations and submit a PR
- Improve flatpak's documentation, hosted at http://docs.flatpak.org and developed over in flatpak-docs
- Find a bug and submit a detailed report including your OS, flatpak version, and the steps to reproduce
- Add your favorite application to Flathub by writing a flatpak-builder manifest and submitting it
- Improve the Flatpak support in your favorite Linux distribution
Hacking
See CONTRIBUTING.md
Related Projects
Here are some notable projects in the Flatpak ecosystem:
- Flatseal: An app for managing permissions of Flatpak apps without using the CLI
- Flat-manager: A tool for managing Flatpak repositories