1FLATPAK UPDATE(1)               flatpak update               FLATPAK UPDATE(1)
2
3
4

NAME

6       flatpak-update - Update an application or runtime
7

SYNOPSIS

9       flatpak update [OPTION...] [REF...]
10
11       flatpak update [OPTION...] --appstream [REMOTE]
12

DESCRIPTION

14       Updates applications and runtimes.  REF is a reference to the
15       application or runtime to update. If no REF is given, everything is
16       updated, as well as appstream info for all remotes.
17
18       Each REF argument is a full or partial identifier in the flatpak ref
19       format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
20       except ID are optional and can be left out, including the slashes, so
21       most of the time you need only specify ID. Any part left out will be
22       matched against what is installed, and if there are multiple matches an
23       error message will list the alternatives.
24
25       By default this looks for both apps and runtimes with the given REF,
26       but you can limit this by using the --app or --runtime option, or by
27       supplying the initial element in the REF.
28
29       Normally, this command updates the application to the tip of its
30       branch. But it is possible to check out another commit, with the
31       --commit option.
32
33       If the configured remote for a ref being updated has a collection ID
34       configured on it, Flatpak will search the sideload-repos directories
35       configured either with the --sideload-repo option, or on a
36       per-installation or system-wide basis (see flatpak(1)).
37
38       Note that updating a runtime is different from installing a different
39       branch, and runtime updates are expected to keep strict compatibility.
40       If an application update does cause a problem, it is possible to go
41       back to the previous version, with the --commit option.
42
43       In addition to updates, this command will offer to uninstall any unused
44       end-of-life runtimes. Runtimes that were explicitly installed (not as a
45       dependency) or explicitly pinned (see flatpak-pin(1)) are left
46       installed even if unused and end-of-life.
47
48       Unless overridden with the --user, --system or --installation option,
49       this command updates any matching refs in the standard system-wide
50       installation and the per-user one.
51

OPTIONS

53       The following options are understood:
54
55       -h, --help
56           Show help options and exit.
57
58       -u, --user
59           Update a per-user installation.
60
61       --system
62           Update the default system-wide installation.
63
64       --installation=NAME
65           Updates a system-wide installation specified by NAME among those
66           defined in /etc/flatpak/installations.d/. Using
67           --installation=default is equivalent to using --system.
68
69       --arch=ARCH
70           The architecture to update for. See flatpak --supported-arches for
71           architectures supported by the host.
72
73       --subpath=PATH
74           Install only a subpath of the ref. This is mainly used to install a
75           subset of locales. This can be added multiple times to install
76           multiple subpaths. If this is not specified the subpaths specified
77           at install time are reused.
78
79       --commit=COMMIT
80           Update to this commit, instead of the tip of the branch. You can
81           find commits using flatpak remote-info --log REMOTE REF.
82
83       --no-deploy
84           Download the latest version, but don't deploy it.
85
86       --no-pull
87           Don't download the latest version, deploy whatever is locally
88           available.
89
90       --no-related
91           Don't download related extensions, such as the locale data.
92
93       --no-deps
94           Don't update or install runtime dependencies when installing.
95
96       --app
97           Only look for an app with the given name.
98
99       --appstream
100           Update appstream for REMOTE, or all remotes if no remote is
101           specified.
102
103       --runtime
104           Only look for a runtime with the given name.
105
106       --sideload-repo=PATH
107           Adds an extra local ostree repo as a source for installation. This
108           is equivalent to using the sideload-repos directories (see
109           flatpak(1)), but can be done on a per-command basis. Any path added
110           here is used in addition to ones in those directories.
111
112       -y, --assumeyes
113           Automatically answer yes to all questions (or pick the most
114           prioritized answer). This is useful for automation.
115
116       --noninteractive
117           Produce minimal output and avoid most questions. This is suitable
118           for use in non-interactive situations, e.g. in a build script.
119
120       --force-remove
121           Remove old files even if they're in use by a running application.
122
123       -v, --verbose
124           Print debug information during command processing.
125
126       --ostree-verbose
127           Print OSTree debug information during command processing.
128

EXAMPLES

130       $ flatpak --user update org.gnome.gedit
131

SEE ALSO

133       flatpak(1), flatpak-install(1), flatpak-list(1), ostree-find-remotes(1)
134
135
136
137flatpak                                                      FLATPAK UPDATE(1)