unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Sughosha <Sughosha@proton.me>, 63424@debbugs.gnu.org
Subject: [bug#63424] GNOME tracker does not work with tracker-miners
Date: Wed, 10 May 2023 21:50:25 +0200	[thread overview]
Message-ID: <e508e36b4e9a69fb6b5b8e225bb627e3fff9f3b9.camel@gmail.com> (raw)
In-Reply-To: <SVh3asopkM6s1s0AR4iT6odMIGMOp3DdKZrrQRbM-3MgTd2O_FS1ThP8QuQZQiTsbKwBtdDZBKZWf8UXRe8yVlbfc2j_33pZjR0rn1aYuMI=@proton.me>

Hi Sughosha,

Am Mittwoch, dem 10.05.2023 um 17:33 +0000 schrieb Sughosha:
> GNOME "tracker" is built with "libexecdir" in its own prefix in the
> store and "tracker-miners" in its own. The problem is that "tracker"
> does not have access to the executable files in the "libexecdir" of
> "tracker-miners", so commands like "tracker3 extract file.flac" does
> not work. Due to this problem GNOME Music cannot list FLAC files (I
> don't know how it listed my MP3 file). As per this issue
> <https://gitlab.gnome.org/GNOME/gnome-music/-/issues/522>, "tracker3
> extract" should work for GNOME Music to show FLAC files.
The problem here is that the tracker CLI searches these commands in a
hardcoded directory.  Instead of doing that, it should be using a
search path for libexec/tracker3.

Cheers




  reply	other threads:[~2023-05-10 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 17:33 [bug#63424] GNOME tracker does not work with tracker-miners Sughosha via Guix-patches via
2023-05-10 19:50 ` Liliana Marie Prikler [this message]
2023-06-16 20:22   ` Sughosha via Guix-patches via
2023-06-16 22:01     ` Liliana Marie Prikler
2023-06-23 17:16       ` Sughosha via Guix-patches via
2023-06-25 12:38         ` bug#63424: " Liliana Marie Prikler

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e508e36b4e9a69fb6b5b8e225bb627e3fff9f3b9.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=63424@debbugs.gnu.org \
    --cc=Sughosha@proton.me \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).