| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This prevents someone from placing special characters in order to
manipulate the appearance of the permissions list.
CVE-2023-28101, GHSA-h43h-fwqx-mpp8
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
|
|
|
|
|
|
|
|
|
| |
To make indentation work with less effort. The modeline was copied from
libostree with minor modification and the .editorconfig from GLib.
The advantage of having both a modeline and an editorconfig is we can
work out of the box on more editor setups, and the modeline allows us to
specify the style with a lot more fine grained control.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent Meson versions have warnings if you add the subprojects
directory as an include path, because the way Meson wants to consume
subprojects is by the subproject's build system producing a Meson
dependency object that encapsulates its include directory. Flatpak
doesn't have a Meson build system yet, but I'm working on that.
libglnx seems to be set up to have the libglnx directory be its include
path instead: for example, ostree (by the author of libglnx) already
uses "libglnx.h" or <libglnx.h> everywhere. Do the same here.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Then convert all callers
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid shadowing variables that are already declared in a previous scope,
and make such occurrences compile-time errors. These are not functional
changes.
In a few places do related code cleanup.
A similar ostree PR is here:
https://github.com/ostreedev/ostree/pull/2195
|
|
|
|
|
|
|
|
|
| |
flatpak_find_deploy_for_ref() will look for a deploy across all
installations, but we want to use the user-specified one, e.g. user if
--user was passed.
Pointed out here:
https://github.com/flatpak/flatpak/pull/3853#discussion_r487711857
|
| |
|
| |
|
|
|
|
| |
Don't imply a download or install uses a negative number of bytes.
|
|
|
|
|
|
|
|
| |
I had to make a few manual edits but other than those the changes look
reasonable.
Closes: #2715
Approved by: matthiasclasen
|
|
|
|
|
|
|
|
| |
This makes the NAME - DESCRIPTION line at the top
wrap nicely at word boundaries.
Closes: #2620
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
These can be long, so ellipsize them.
Closes: #2499
Approved by: matthiasclasen
|
|
|
|
|
|
|
| |
Use existing defines for metadata fields.
Closes: #2502
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
printf(), and by extension, g_print() interprets
field width in terms of bytes, not characters.
Therefore, using %*s for padding strings with
non-ASCII characters does not work. Instead, use
the new utility function for aligned lines.
While we are doing this, also fix up the alignment of
the extension sections in the output.
Closes: #2502
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
| |
The info command has its own --system/--user/--installation
options, but it was not setting a name for the argument
of --installation. This was showing up in the completion
missing a '=' after --installation.
Closes: #2534
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
Don't consider 'Version:' for indentation when we
don't have version information to show.
Closes: #2521
Approved by: mwleeds
|
|
|
|
|
|
|
| |
This seems the right thing to do.
Closes: #2521
Approved by: mwleeds
|
|
|
|
|
|
|
|
|
|
|
| |
When the -s option is used, it is likely that
the result is getting screenscraped and reparsed.
Make that easier by producing a plain number in
this case.
Closes: #2536
Approved by: mwleeds
|
|
|
|
|
| |
Closes: #2536
Approved by: mwleeds
|
|
|
|
|
| |
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a version to the deply data format, assuming that if
there is no version then it is 0. Also extends all loaders so that
it can specify a required version, with the goal that most users
are fine with old versions, but if you need more recent we have
a (costly) conversion process to upgrade (will be added later).
The library and the flatpak list/info commands require the most
current version for full info, all other users can use any version.
Also, as part of this we now pass the ref to flatpak_load_deploy_data()
as this will be needed later for the backwards compat support.
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
| |
Show a description and show the appstream version,
and tidy up the formatting.
This gets us closer to the design in
https://github.com/flatpak/flatpak/wiki/CLI-experimental-design
Closes: #2409
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
Make format_timestamp() a shared utility,
instead of having 3 almost identical copies.
Closes: #2409
Approved by: alexlarsson
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for fuzzy matching ref names (AKA "typo helper") to
the uninstall command to mirror what the install command has. In short,
this means you can do "flatpak uninstall gedit" instead of "flatpak
uninstall org.gnome.gedit". Flatpak will prompt you to choose between
similarly named installed refs, and will only make the choice for you if
--assumeyes was used and there's only one match.
Note that this commit does have the side effect that if there are
multiple matching refs with the same ID (e.g. with different branches or
in different installations) you are prompted to choose between them.
Previously you were shown an error message.
Closes: #2330
Approved by: matthiasclasen
|
|
|
|
|
|
|
| |
We have to free the return value of flatpak_deploy_get_dir.
Closes: #1964
Approved by: mwleeds
|
|
|
|
|
|
|
| |
We have to free the FlatpakDir
Closes: #1964
Approved by: mwleeds
|
|
|
|
|
|
|
| |
flatpak_dir_read_latest return value has to be freed
Closes: #1964
Approved by: mwleeds
|
|
|
|
|
| |
Closes: #1870
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #1800
Approved by: alexlarsson
|
| |
|
|
|
|
|
|
|
| |
Also show sdk in regular output
Closes: #1753
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
This shows the location the ref is deployed to
Closes: #1753
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This makes info, list, remotes, and search work if there is no
system flatpak repo. Before it failed with EPERM.
Closes: #1742
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
This is the start of the merging of lib/* into common/*
Closes: #1706
Approved by: alexlarsson
|
|
|
|
|
| |
Closes: #1566
Approved by: alexlarsson
|
|
|
|
|
| |
This also looks for removed but live deploys so that an app
can be re-started as long as it is live.
|
|
|
|
|
|
|
|
|
|
|
|
| |
All flatpaks built using version 0.9.4 or newer should have the
xa.metadata field in the commit metadata, so warn if it doesn't exist.
This commit changes the info command to print a warning rather than
nothing and changes the info-remote command to print a warning rather
than error out.
Closes: #1351
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
If flatpak is compiled with P2P support and the commit in question has a
collection ID in its metadata, show it.
Closes: #1351
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This allows you to see if a particular app has access
to a specific path.
Closes: #1387
Approved by: alexlarsson
|
|
|
|
|
|
|
| |
This shows the active permissions for the app, including any overrides.
Closes: #1387
Approved by: alexlarsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some builtin flatpak commands work on a single installation, and others
work on multiple installations (such as the remotes command that lists
both system and user remotes). Currently flatpak_option_context_parse()
only supports returning one installation to its caller, and any commands
that want to support multiple installations have to implement that
themselves which leads to a lot of code duplication.
This commit changes flatpak_option_context_parse() to take three new
flags:
* FLATPAK_BUILTIN_FLAG_ONE_DIR maintains the old behavior by
returning one installation (i.e. user if --user was passed, system if
--system, etc.).
* FLATPAK_BUILTIN_FLAG_STANDARD_DIRS will get all the installations
specified by the options, or the user and system ones if none were.
* FLATPAK_BUILTIN_FLAG_ALL_DIRS includes non-default system
installations along with the user and system ones if none were
specified.
These flags also affect what options are parsed and whether the
directories are ensured to exist, so it makes sense in some
circumstances for callers to pass a NULL out_dirs even when not using
FLATPAK_BUILTIN_FLAG_NO_DIR.
This commit also changes all the callers of
flatpak_option_context_parse() so they maintain their behavior. The only
functional change introduced by this is that using --installation
multiple times for commands that only support one now leads to an
error emitted by flatpak rather than by g_option_context_parse().
A follow-up commit will use this refactoring to make many commands
behave more intelligently in determining which installation to use.
Closes: #1205
Approved by: alexlarsson
|
|
|
|
|
|
|
|
| |
This adds the Date, Subject and Parent fields that are shown
by remote-info so these match for the fields where it makes sense.
Closes: #1192
Approved by: alexlarsson
|
| |
|
|
|
|
|
| |
This is useful mainly to parse the keyfile, and is not very
nice for pretty output.
|