Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] tracker-miners: update to 3.4.3.
Date: Tue, 24 Jan 2023 03:25:51 +0100	[thread overview]
Message-ID: <20230124022551.x1wnTFy4AQjnHbACww9K8kHqqdFNjoSw6mHJdiVEEYg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41832@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1249 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/41832

tracker-miners: update to 3.4.3.
<!-- 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/41832.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tracker-41832.patch --]
[-- Type: text/x-diff, Size: 2716 bytes --]

From 2b6075c2f69d7fcd78e27af807ca308cb917bc31 Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Mon, 23 Jan 2023 16:30:15 -0800
Subject: [PATCH 1/2] sqlite: disable SQLITE_ENABLE_BATCH_ATOMIC_WRITE

Only supported on F2FS and triggers seccomp assertion in tracker-miners.
---
 srcpkgs/sqlite/template | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/sqlite/template b/srcpkgs/sqlite/template
index 7f311e9c51c7..ea827b4ec0a2 100644
--- a/srcpkgs/sqlite/template
+++ b/srcpkgs/sqlite/template
@@ -1,7 +1,7 @@
 # Template file for 'sqlite'
 pkgname=sqlite
 version=3.40.1
-revision=1
+revision=2
 _amalgamationver=$(printf "%d%02d%02d00\n" ${version//./ })
 build_style=gnu-configure
 configure_args="--enable-threadsafe --enable-dynamic-extensions --enable-fts5"
@@ -17,8 +17,7 @@ checksum=2c5dea207fa508d765af1ef620b637dcb06572afa6f01f0815bd5bbf864b33d9
 CFLAGS="-DSQLITE_ENABLE_DBSTAT_VTAB -DSQLITE_ENABLE_COLUMN_METADATA \
  -DSQLITE_ENABLE_UNLOCK_NOTIFY -DSQLITE_SECURE_DELETE \
  -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DSQLITE_ENABLE_FTS4 \
- -DSQLITE_ENABLE_FTS3_TOKENIZER=1 -DSQLITE_ENABLE_BATCH_ATOMIC_WRITE=1 \
- -DSQLITE_ENABLE_DESERIALIZE"
+ -DSQLITE_ENABLE_FTS3_TOKENIZER=1 -DSQLITE_ENABLE_DESERIALIZE"
 # explicitly enable fdatasync
 CFLAGS+=" -DHAVE_FDATASYNC"
 disable_parallel_build=yes

From e7c6a648f76dc852b439b55da838a5fd0903aae2 Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Mon, 23 Jan 2023 16:31:44 -0800
Subject: [PATCH 2/2] tracker-miners: update to 3.4.3.

---
 srcpkgs/tracker-miners/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/tracker-miners/template b/srcpkgs/tracker-miners/template
index 9e8cdc492c26..3e7966c2b4a9 100644
--- a/srcpkgs/tracker-miners/template
+++ b/srcpkgs/tracker-miners/template
@@ -1,6 +1,6 @@
 # Template file for 'tracker-miners'
 pkgname=tracker-miners
-version=3.4.2
+version=3.4.3
 revision=1
 build_style=meson
 build_helper=qemu
@@ -24,10 +24,10 @@ makedepends="tracker-devel ffmpeg-devel dbus-devel exempi-devel
 short_desc="Data miners for tracker"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
-homepage="https://developer.gnome.org/libtracker-miner/stable"
+homepage="https://tracker.gnome.org/"
 changelog="https://gitlab.gnome.org/GNOME/tracker-miners/-/raw/master/NEWS"
 distfiles="${GNOME_SITE}/tracker-miners/${version%.*}/tracker-miners-${version}.tar.xz"
-checksum=101e3608f1c28bfed8ae25522f7a720b559f889a76e280afbe50a4d8b064f92c
+checksum=8e4f3976472641b648d0f8f20debae1b1629ca5b560b8616e117d29d756fbeeb
 make_check=no # relies on unsupported ops in chroot
 
 tracker3-miners_package() {

  parent reply	other threads:[~2023-01-24  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  0:32 [PR PATCH] " oreo639
2023-01-24  0:57 ` oreo639
2023-01-24  0:57 ` oreo639
2023-01-24  2:03 ` [PR PATCH] [Updated] " oreo639
2023-01-24  2:25 ` oreo639 [this message]
2023-01-25  3:37 ` oreo639
2023-02-11  5:19 ` [PR PATCH] [Updated] " oreo639
2023-02-14 20:34 ` [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=20230124022551.x1wnTFy4AQjnHbACww9K8kHqqdFNjoSw6mHJdiVEEYg@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).