gnome-software:wip/hughsie/desktop2

Last commit made on 2019-10-11
Get this branch:
git clone -b wip/hughsie/desktop2 https://git.launchpad.net/gnome-software

Branch merges

Branch information

Name:
wip/hughsie/desktop2
Repository:
lp:gnome-software

Recent commits

65ab13c... by Richard Hughes on 2019-10-11

Do not show non-applications in the installed panel

3961c64... by Daniel Mustieles on 2019-10-10

Updated Spanish translation

80301a6... by Matej Urbančič on 2019-10-03

Updated Slovenian translation

ea9bdd7... by Richard Hughes on 2019-10-02

Match the exact ID when refining a wildcard

If we specify the unique ID (for instance from a GNOME Shell search result)
then match the *exact* GsApp rather than just returning the first one that
only matches the GsApp ID.

Fixes https://gitlab.gnome.org/GNOME/gnome-software/issues/769

1e15e1f... by Richard Hughes on 2019-10-02

trivial: Fix example spec file

65e97f3... by Robert Ancell on 2019-10-03

snap: Remove dead code

This should have been removed in 266fed5.

4af0908... by Marek Černocký <email address hidden> on 2019-10-03

Updated Czech translation

7a63b77... by scootergrisen on 2019-09-01

Change Top Rated to Rating.

cded66b... by Philip Withnall <email address hidden> on 2019-10-02

malcontent: Correctly distinguish empty content ratings from missing ones

As with the previous commit to make this change to the `appstream`
plugin, the OARS semantics require that if `<content_rating/>` is
present, any attributes whcih are missing from it (which could be ‘all
attributes’) are assumed to have a value of `none`. If
`<content_rating/>` is missing, they are assumed to have a value of
`unknown`.

Handle that correctly, and correctly convert all `unknown` values to
`intense` before comparing them against the user’s policy.

See the [OARS
specification](https://github.com/hughsie/oars/blob/master/specification/oars-1.1.md).

Signed-off-by: Philip Withnall <email address hidden>

77e2b12... by Philip Withnall <email address hidden> on 2019-10-02

build: Enable malcontent plugin by default

It should be ready to build by default. It was only disabled by default
when merged as that merge request was intended to target a
feature-frozen branch. We’re no longer in feature freeze.

For the moment, though, we have to disable it in the CI, as
libmalcontent isn’t available there yet.

Signed-off-by: Philip Withnall <email address hidden>