| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We specify G_TYPE_INT64 but pass an unspecified integer that gets
promoted to 32-bit. This wreaks havoc in the GValue varargs collection
glib code.
Specify the right type in our tests, so that we don't hit this bug.
Closes: https://gitlab.gnome.org/GNOME/tracker/-/issues/397
|
|\ \
| |/
|/|
| |
| | |
ci: Update stable fedora image to F37 and add rawhide@aarch64 tests
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/586
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since we are departing from test beds that have libsoup2 only
into ones that have soup2 available but soup3 is also available and
enabled by default, the several paths skewed the coverage testing
paths.
Add a test target for soup2 specifically, so we get some of it back
and spot regressions in libsoup2 support.
|
| |
| |
| |
| | |
This may be necessary with the switch to gcovr >= 6.0.
|
| |
| |
| |
| |
| | |
Hopefully gets us again past gcovr JSON format version mismatches,
and allows merging those from the different CI test runs.
|
| |
| |
| |
| | |
Provide a hint to CI logs if gcovr fails to get a JSON summary.
|
| |
| |
| |
| |
| |
| | |
In addition to testing stable Fedora (even old, till the previous commit)
on aarch64, test this architecture on Rawhide as well, in order to spot
possible endianness regressions from our dependencies.
|
|/
|
|
| |
Fedora 35 is somewhat stale already.
|
| |
|
|\
| |
| |
| |
| | |
Documentation improvements
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/584
|
| |
| |
| |
| |
| |
| | |
Make the background of some images transparent, and add some
CSS to ensure nodes, edges and arrows get proper colors on both
light and dark themes.
|
| |
| |
| |
| |
| | |
Explain somewhat better what tracker is, does, and what possible
advantages there could be in using it.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The flatpak CLI parsing for additional policies changes at some point
so that it is not possible to specify multiple values in a single call.
Doing that results in the ';' being escaped, and the full string to be
interpreted as a single value.
In order to add multiple values, --add-policy can be called multiple
times, recommend that in our manpage for the task.
|
|/
|
|
| |
Explain this a bit better, add some diagrams, etc.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
website: Update IRC details
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/578
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Plug some leaks
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/582
|
| | |
| | |
| | |
| | |
| | | |
When juggling with both update/select errors, we might be leaking one if
the latter call succeeded.
|
| | |
| | |
| | |
| | |
| | | |
The async process takes a ref on the hashtable, so dispose our own
reference here.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
libtracker-common: Fix building Tracker as a subproject
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/583
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The module lookup is currently based to the top builddir, which
might differ is Tracker is being built as a subproject. Make
it dependent on the current build dir (i.e. the directory the
module will be built to), so it works also on those situations.
Fixes: a4f9885a15d ("libtracker-common: Convert unicode parser to a GModule")
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Migrate docs to gi-docgen (Take 2)
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/580
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The version is already expressed in gi-docgen output, plus it's now
appended in the completely wrong place... making the website output
look ugly.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to build docs with gi-docgen, and fix test-website
phase, as this is meant to run on MRs.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is bitrotting already, and we will not want to go back
to that. Presumably noone else would, so we can simply drop
this.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Same rationale than devhelp, we want to add ontology-related
search terms there. Generate the JSON files separately, in order
to merge them at the same last stage.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use embedded SVG for the few diagrams we have at the tutorial,
like everywhere else in docs now. This should also work with
dark modes and whatnot.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to move to embedded SVGs for images, we have to be able
to embed them first.
|
| | | |
| | | |
| | | |
| | | | |
In the annotations about nrl:notify properties.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Add some separation between columns, and a hover effect on rows,
to increase legibility.
|
| | | |
| | | |
| | | |
| | | | |
Otherwise, they show in multiple lines.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Highlight how do the various ontology classes relate to other classes.
Just like with the class diagrams, make things links so the documentation
can be navigated.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
More in line with gi-docgen, generate SVGs for our class hierarchies,
and embed them in the docs.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It is not much useful to e.g. list every defined resource in
the rdfs:Resource documentation. Avoid these kinda obvious
pre-defined instances.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Avoid too much nesting of sections, so the navigation sidebar is able
to show the classes and additional properties.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This document has some embedded code examples, these should be
embedded into the final markdown document.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Rescue this nasty little hack from commit c5414ed4da15, and make it
go through the generated documentation files at the moment.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update it to the gi-docgen syntax, fix links, flesh out
docs some more, and make documents generally make a better
use of the navigation sidebar.
The several subsections describing ontologies have been
merge into a single document.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Port references and links to the gi-docgen format, and while at
it flesh out some more documentation and adjust formatting to
look better with the gi-docgen templates.
|
| | | |
| | | |
| | | |
| | | | |
This is required for correct introspection of our error domain.
|
| | | |
| | | |
| | | |
| | | | |
Fix the images for our small property annotations.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The documentation of g_dbus_error_register_error_domain() says we
should not use one.
|