• Kalev Lember's avatar
    flatpak: Match origin when searching appstream · 73f3f421
    Kalev Lember authored
    When parsing system installed appstream data for packages we usually
    have one appstream file that covers multiple repos (e.g.
    /usr/share/app-info/xmls/fedora.xml.gz and "fedora", "updates",
    "updates-testing" repos). In this case, when parsing the appstream we
    can't set app origin based on the appstream origin as there is no
    one-to-one mapping from appstream origin to the repo where the package
    actually comes from.
    
    For flatpaks, however, we always have per-remote appstream data and we
    need to keep track of the origin to match the correct app from the
    correct remote. If we don't do that then we end up refining flatpak apps
    with the first entry that appstream finds, which may be from a wrong
    remote.
    
    This is harmless when only one repo provides each flatpak app, but as
    soon as we have two (e.g. Flathub and Fedora) we need to make sure to
    match the correct appstream entry with the correct flatpak.
    
    This regressed in commit d3648252 that took out the origin adding in
    gs_appstream_create_app(). This commit now adds it back and makes it
    work again for the new libxmlb parsing code.
    
    Partially fixes: #547
    73f3f421
Name
Last commit
Last update
contrib Loading commit data...
data Loading commit data...
doc Loading commit data...
lib Loading commit data...
plugins Loading commit data...
po Loading commit data...
src Loading commit data...
subprojects Loading commit data...
tests Loading commit data...
.gitlab-ci.yml Loading commit data...
AUTHORS Loading commit data...
COMMITMENT Loading commit data...
COPYING Loading commit data...
MAINTAINERS Loading commit data...
NEWS Loading commit data...
README.md Loading commit data...
RELEASE Loading commit data...
gnome-software.doap Loading commit data...
meson.build Loading commit data...
meson_options.txt Loading commit data...
meson_post_install.sh Loading commit data...