FLATPAK-REMOTE-INFO(1)

💖 FLATPAK-REMOTE-INFO — like, the manual page, but make it cute

okay bestie so this is flatpak remote-info, part of the flatpak manual situation (volume 1, section 1, if you're keeping track 📓). it's the little command that spills the tea on an app or runtime sitting in a remote repo. let's get into it 🫶

---

✨ NAME ✨

flatpak-remote-info — show info about an application or runtime that lives in a remote 🦋

---

🌸 SYNOPSIS 🌸

flatpak remote-info [OPTION...] REMOTE REF

---

💅 DESCRIPTION 💅

So basically, this shows you information about the runtime or application REF from the remote repository named REMOTE. And if you're like "wait, what remotes do I even have??" — you can find every configured remote repository with flatpak remotes. easy peasy 🍓

By default the output comes formatted in a friendly format, like it's talking to a human. But the second you specify one of the --show-... options? Boom — output switches to a machine-readable format instead. two vibes, one command ✨

And unless you override it with --system, --user, or --installation, this command picks either the default system-wide installation or the per-user one — whichever one actually has the specified REMOTE. it literally goes looking for it 👑

---

🎀 OPTIONS 🎀

Here's everything this thing understands:

• -h, --help — shows the help options and then dips out. bye 👋
• -u, --user — use the per-user configuration.
• --system — use the default system-wide configuration.
• --installation=NAME — use a system-wide installation specified by NAME, picked from the ones defined in /etc/flatpak/installations.d/. and fun fact: using --installation=default is exactly the same as using --system. same energy, different name 💫
• --cached — prefers locally cached info when it can, even though that info might be out of date. so yeah, it's faster, but it risks handing you stale info 😭 also, heads up: some info isn't cached at all, so it just won't be available. no cap.
• --runtime — assume REF is a runtime if it wasn't explicitly specified.
• --app — assume REF is an app if it wasn't explicitly specified.
• --arch=ARCH — the default architecture to look for, in case it's not given explicitly in the REF. wanna know what architectures your host supports? check flatpak --supported-arches 🧚
• --commit=COMMIT — show info about that specific commit instead of the latest version. going digging in the archives fr fr
• --log — displays a log of previous versions. history lesson 📜
• -r, --show-ref — show the matched ref.
• -c, --show-commit — show the commit id.
• -p, --show-parent — show the parent commit id.
• -m, --show-metadata — show the metadata.
• -v, --verbose — print debug info while the command is processing.
• --ostree-verbose — print OSTree debug info while the command is processing. extra loud mode 🔥

---

🌈 EXAMPLES 🌈

here's the moment you've been waiting for, the demo:

$ flatpak --user remote-info flathub org.gnome.gedit

    Ref: app/org.gnome.gedit/x86_64/stable
    ID: org.gnome.gedit
    Arch: x86_64
    Branch: stable
    Date: 2017-07-31 16:05:22 +0000
    Subject: Build org.gnome.gedit at 3ec291fc1ce4d78220527fa79576f4cc1481ebe5
    Commit: 3de7e9dde3bb8382aad9dfbbff20eccd9bf2100bc1887a3619ec0372e8066bf7
    Parent: -
    Download size: 3,4 MB
    Installed size: 11,1 MB
    Runtime: org.gnome.Platform/x86_64/3.24

look at all that info. she ate 💅

---

👑 SEE ALSO 👑

flatpak(1), flatpak-remotes(1) flatpak-remote-ls(1)

---

okay that's the whole page, you're officially educated 🎓 go forth and inspect your remotes, bestie 🦋💖

this page is brought to you by the flatpak crew — that's the source right there, and the version/date stamp on this bad boy is FLATPAK REMOTE-INFO(1), periodt ✨