From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] tracker: update to 3.4.1.
Date: Fri, 02 Dec 2022 08:40:13 +0100 [thread overview]
Message-ID: <20221202074013.Z8kZv8u44z1jx2-tHgrnS3cV_dxaQD-349ViLwdrSZw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40875@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
There is an updated pull request by oreo639 against master on the void-packages repository
https://github.com/oreo639/void-packages tracker
https://github.com/void-linux/void-packages/pull/40875
tracker: update to 3.4.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/40875.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tracker-40875.patch --]
[-- Type: text/x-diff, Size: 3496 bytes --]
From ef97e65e2d5be925bd1aba034f5f030600f224bb Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Thu, 1 Dec 2022 23:17:36 -0800
Subject: [PATCH] tracker: update to 3.4.1.
---
...5ae5b296937ff58233a9a283f46ae2800af2.patch | 43 +++++++++++++++++++
srcpkgs/tracker/template | 6 +--
2 files changed, 46 insertions(+), 3 deletions(-)
create mode 100644 srcpkgs/tracker/patches/d54f5ae5b296937ff58233a9a283f46ae2800af2.patch
diff --git a/srcpkgs/tracker/patches/d54f5ae5b296937ff58233a9a283f46ae2800af2.patch b/srcpkgs/tracker/patches/d54f5ae5b296937ff58233a9a283f46ae2800af2.patch
new file mode 100644
index 000000000000..f672d3b15b68
--- /dev/null
+++ b/srcpkgs/tracker/patches/d54f5ae5b296937ff58233a9a283f46ae2800af2.patch
@@ -0,0 +1,43 @@
+From d54f5ae5b296937ff58233a9a283f46ae2800af2 Mon Sep 17 00:00:00 2001
+From: Carlos Garnacho <carlosg@gnome.org>
+Date: Sun, 20 Nov 2022 12:16:58 +0100
+Subject: [PATCH] core: Handle ROWIDs turned into strings in SparqlPrintIRI()
+
+Even though normally we expect ROWIDs to preserve numeric affinity
+when we proceed to print their IRI in the higher parts of the query,
+it is not guaranteed by the SQLite documentation:
+
+ "Whether or not a persistent internal datatype conversion occurs
+ is undefined and may change from one release of SQLite to the next."
+
+And this in fact changed for the core/property-paths/alternative-path-3
+unit test, where it does the '|' union of text and resource (i.e. ROWIDs)
+properties. Since SQLite 3.40.0, the SparqlPrintIRI() happening in the
+topmost select will get SQLITE_TEXT affinity for all ROWID values received
+through the union.
+
+In order to work with both older and newer version of SQLite, attempt to
+force integer affinity so ROWID IRIs are correctly resolved instead of
+being interpreted as IRI strings.
+
+Closes: https://gitlab.gnome.org/GNOME/tracker/-/issues/387
+---
+ src/libtracker-sparql/core/tracker-db-interface-sqlite.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libtracker-sparql/core/tracker-db-interface-sqlite.c b/src/libtracker-sparql/core/tracker-db-interface-sqlite.c
+index ca1ebb985..68f6bd310 100644
+--- a/src/libtracker-sparql/core/tracker-db-interface-sqlite.c
++++ b/src/libtracker-sparql/core/tracker-db-interface-sqlite.c
+@@ -1901,7 +1901,7 @@ function_sparql_print_iri (sqlite3_context *context,
+ return;
+ }
+
+- if (sqlite3_value_type (argv[0]) == SQLITE_INTEGER) {
++ if (sqlite3_value_numeric_type (argv[0]) == SQLITE_INTEGER) {
+ sqlite3_stmt *stmt;
+ gboolean store_auxdata = FALSE;
+ sqlite3 *db;
+--
+GitLab
+
diff --git a/srcpkgs/tracker/template b/srcpkgs/tracker/template
index 770ade715ca6..a9d64c84b16c 100644
--- a/srcpkgs/tracker/template
+++ b/srcpkgs/tracker/template
@@ -1,7 +1,7 @@
# Template file for 'tracker'
pkgname=tracker
-version=3.4.0
-revision=2
+version=3.4.1
+revision=1
build_style=meson
build_helper="gir"
configure_args="-Ddocs=false -Dman=true -Dstemmer=disabled
@@ -17,7 +17,7 @@ license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://wiki.gnome.org/Projects/Tracker"
changelog="https://gitlab.gnome.org/GNOME/tracker/-/raw/master/NEWS"
distfiles="${GNOME_SITE}/tracker/${version%.*}/tracker-${version}.tar.xz"
-checksum=b3b380c9571d7c7423b5f401e4a2f2d78de47143b035eb2c1281e2423c59218b
+checksum=ea9d41a9fb9c2b42ad80fc2c82327b5c713d594c969b09e1a49be63fb74f4fae
make_check_pre="dbus-run-session"
if [ "$CROSS_BUILD" ]; then
next prev parent reply other threads:[~2022-12-02 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 7:18 [PR PATCH] " oreo639
2022-12-02 7:40 ` oreo639 [this message]
2022-12-04 17:55 ` [PR PATCH] [Updated] " oreo639
2022-12-16 18:19 ` [PR PATCH] [Merged]: " paper42
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221202074013.Z8kZv8u44z1jx2-tHgrnS3cV_dxaQD-349ViLwdrSZw@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).