Recent Update error with tinysparql and tracker3

General
1

Bildschirmfoto vom 2024-09-19 11-37-06
Bildschirmfoto vom 2024-09-19 11-37-06905Ă—638 8.95 KB

3 Likes
2

I have same problem.

3

Same problem :frowning_face:

4

Definitely not alone ;0

5

No problem.
You should update using the Linux package manager.

6

Gnome was updated to 47.

You can remove tracker3 as it is no longer used (tinysparql and localsearch replace it). First try sudo pacman -Syuu, if this doesn’t work proceed with the commands below.

sudo pacman -Rdd tracker3
sudo pacman -Syu
6 Likes
7

If you type update or pacman -Syu, you will be asked if you want to replace the tracker.

8

Wasn’t the case for me (or anyone above apparently). It just error’d out with a file conflict.

1 Like
9

Normally it should replace it, but seems it won’t work with the optimised packages as tracker3 is not in cachy repos

2 Likes
10

It worked for me. I can’t say why it doesn’t work for others.

11

Yes, worked. :+1:

12

Can I ask what method you tried again?
It might be the solution after all.

13

sudo pacman -Rdd tracker3

Then you can update with sudo pacman -Syu

14

Thanks for the information. But, as I wrote above, I just had to confirm that I want to replace the tracker. This is probably because I always use the system updater for system updates. I just don’t like GUIs.

EDIT: If you use Pamac, Discover or similar for updates, you obviously can’t answer yes/no questions. This will probably be the reason you have to replace the tracker3 afterwards.

15

Please do not suggest -Rdd as a workaround to the public. If it works for you sure, thats great, but the nature of the command is very destructive and if the user is not careful, things will definitely break.

Suffice to say that, this should be fixed after all the GNOME packages are built in the cachy repos. Sorry for the inconvenience.

1 Like
16

Thx @inffy , it did the trick on my side.

17

What command would you have had adviced @naim

sudo pacman -Rns {package} !

If it did or borked my install I would ve reinstalled, I do nothing important on that , but it might not be the same for everyone.

18

The only thing that can be done that is NOT destructive in this situation in the user’s side is to manually install tracker3 that fulfills the conditions of the replaces=() line from tinysparql. The only way to do this is to build it manually:

git clone https://gitlab.archlinux.org/archlinux/packaging/packages/tracker3/
cd tracker3
sudo pacman -S glib2 glib2-devel
makepkg -si

Afterwards, a system update would run without any errors.

Edit: It looks like there will not be a fix in repos side, anytime soon at least. There is however a solution from the main CachyOS developers, which matched the previous solution with -Rdd.

3 Likes
19

Thx, appreciated @naim

Wonder why it did that, it might have to do with the recent pacamn 7 update, I don t know, never had that one before.

Well, that didn t go well on my side;

tracker/src/libtracker-sparql/core/meson.build:1:27: ERROR: Dependency 'glib-2.0' tool variable 'glib_mkenums' contains erroneous value: '/usr/bin/glib-mkenums'

This is a distributor issue -- please report it to your glib-2.0 provider.

A full log can be found at /home/altima/tracker3/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
20

Oh no! When I run git clone Arch Linux / Packaging / Packages / tracker3 · GitLab
cd tracker3
makepkg -si
the terminal says pacman can’t handle the dependency