| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
We don't have a separate discourse for Flatpak; it seems fine to link to
the Flathub one.
Fixes https://github.com/flatpak/flatpak/issues/3602
|
|
|
|
|
|
| |
If downloading a specific commit (or oci manifest) we may get a 401 back.
If so, request a token and try again. In this case we don't yet know the
token type, so pass MAXINT32 for "don't know".
|
| |
|
|
|
|
|
| |
This is what it is really, and I want to extend it with more http errors
that are not necessarily oci related.
|
| |
|
|
|
|
|
| |
We now allow this to be set with update --commit=123abc in the oci case
too.
|
|
|
|
|
|
| |
This downloads a manifest by digest and reconstructs the commit except
for the tree/metadata reference. This allows things like flatpak remote-info
and flatpak update --commit=xxx to work.
|
|
|
|
| |
This is duplicated in a few places
|
|
|
|
|
|
|
|
|
| |
Only have the single function flatpak_remote_state_load_ref_commit()
that loads the commit objects (and don't support loading other types
of objects as that is not used).
This is a minor cleanup, but it also will be useful later when
we want to be able to "load" commits from OCI repositories.
|
|
|
|
|
| |
This just does a GET, which is not quite right, but will work.
This is needed for the authenticator.
|
| |
|
|
|
|
|
|
|
|
|
| |
Without this I got for the fedora registry:
```
getting token for https://registry.fedoraproject.org/v2/f32/flatpak-runtime/manifests/sha256:bd83b4f6974094848efac22b933419c1dbe11b553def148a82f821faf595de8a
F: Anonymous authentication failed: Unexpected response status 404 from repo
```
|
| |
|
|
|
|
| |
This makes for instance docker hub work.
|
| |
|
|
|
| |
Update according to .po file from https://l10n.gnome.org/vertimus/flatpak/master/po/hr/
|
| |
|
|
|
|
| |
Fixes https://github.com/flatpak/flatpak/issues/3546
|
|
|
|
|
| |
Logically, the SDK should be listed with the app info right after the
runtime, not in the commit section.
|
|
|
|
|
|
| |
Currently if you run "flatpak update --commit=XYZ", we try to use that
commit for every installed thing, which doesn't make much sense. Make it
an error not to specify a ref with --commit.
|
|
|
|
|
|
|
|
|
|
|
| |
The newly added https://systemd.io/DESKTOP_ENVIRONMENTS/ lists an XDG
defined specification for how cgroups for applications should be named.
This will allow flatpak's to correctly follow any drop-in's set for
applications on the system as well as help next-gen system monitor's
treat flatpaks as applications.
flatpak-session-helper.service is unaffected.
|
|\
| |
| | |
flatpak-transaction: Change related_to_op to related_to_ops
|
|/
|
|
|
|
|
|
|
|
|
| |
Since a single runtime (for example) can be related-to several apps,
that needs to be representable in the data format.
This is an API break, but only of API which has not been released yet.
See https://github.com/flatpak/flatpak/pull/3568#issuecomment-618251958
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|\
| |
| | |
list: Fix a tiny whitespace error
|
|/ |
|
|
|
|
|
| |
Removing multiple refs where one is missing is now a warning, not a
failure, so change the test to just try to remove one ref.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When we add significant new source strings downstream, Endless adds
projects to our Transifex instance to get translations from paid
translators and community contributors.
Since we no longer add new source strings to Flatpak, we're removing it
from our infrastructure. I checked which strings we have translations
for downstream that are not present (if perhaps different) upstream, and
these German translations from a community member are it.
|
|
|
|
|
|
|
| |
While it can be worked out from the context, it’s clearer to state the
units that download and installed sizes are calculated in explicitly.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
|
|
|
| |
Make it explicit that skipped ops are excluded when returning the ops in
a transaction, or when working out whether it’s empty.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
|
|
|
|
|
| |
This exposes the `skip` member of `FlatpakTransactionOperation`, as it’s
needed for callers to usefully traverse the operation graph (which is
now accessible using
`flatpak_transaction_operation_get_related_to_op()`).
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
|
|
|
| |
This will make systemd create the system-helper user if it is missing.
|
|
|
|
| |
Signed-off-by: Philip Withnall <withnall@endlessm.com>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Re-implement flatpak_installation_list_installed_refs_for_update() using
a FlatpakTransaction, so we can guarantee it always gives the same set
of things to update as the update command. This API is used by GNOME
Software and many times in the past g-s has not shown the same list of
apps to be updated as the flatpak CLI. See:
- https://gitlab.gnome.org/GNOME/gnome-software/issues/539
- https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/430
This commit also expands the unit tests for this API, which were already
quite good. Now we test that missing subpaths of locale extensions show
up as updates, and updates that have been pulled but not deployed show
up as well. The latter is a break from how this function used to behave,
but it seems unlikely to break any application.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, if you add an app update to a transaction and its locale
extension does not have subpaths installed for every configured
language, the locale will be updated accordingly. But if you add only
the locale extension to the transaction to be updated, the transaction
is a no-op because we treat subpaths == NULL to mean the currently
installed set of subpaths, and
flatpak_dir_needs_update_for_commit_and_subpaths() decides there's
nothing to do.
This doesn't seem like the right behavior, so update
flatpak_transaction_add_ref() so that we take the configured set of
locales into account as we do in add_related().
This will help the unit test in the following commit to pass.
|
|
|
|
|
|
| |
This will be used in the following commit, so we can track what
installed thing needs an update when there's a transaction operation to
e.g. install its missing runtime or extension.
|
|
|
|
| |
These were committed recently by accident; use g_debug() instead.
|
|
|
|
|
| |
* Update russian translation
Some strings have been fixed
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Currently when you create a FlatpakQuietTransaction object using a
FlatpakDir, the dir will have no_interaction set to TRUE even after the
transaction runs. I don't think it makes sense to have a side effect
like that, and it causes the remote-delete command to fail in the case
where it has to uninstall things. So, restore the old no_interaction
value during destruction of the FlatpakQuietTransaction.
Fixes https://github.com/flatpak/flatpak/issues/3140
|
| |
|
|
|
|
|
|
| |
* Update russian translation
100% complete
|
|\
| |
| | |
Update sv.po
|
|/
|
| |
Trying to do a PR with updated Swedish translations
|
| |
|
| |
|
| |
|