update to tinysparql leads to conflicting files and depency issues #258
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
the package
tinysparql
replacestracker3
. But the replaces does not work when using ALHP, because:but the ALHP version is 3.7.3-2.1
this leads to a depency problem because gtk3 and gtk4 depend on tracker3 therefore removing tracker3 is not possible.
https://gitlab.archlinux.org/archlinux/packaging/packages/tinysparql/-/blob/main/PKGBUILD?ref_type=heads
Is this solved by adding
--assume-installed tinysparql
and/or--assume-installed tracker3
?You can also try adding a specific version to
--assume-installed
.with running
sudo pacman -Syu --assume-installed tinysparql
the update applies but it breaks gtk during the update:afterwards, GTK applications are broken, I have repaired the system manually by running
sudo pacman -R tracker3 --assume-installed tracker3
andsudo pacman -S gtk3
which pulled intinysparql
as a dependency and re-ran the Probing GTK3 input method modules... stepEdit: running
sudo pacman -R tracker3 --assume-installed tracker3
and after that applying the update should work without breaking the system but I can't test that scenario.for the record, those are the files that conflict:
Confirmed Working Solution
Would it be possible to first remove
tracker3
withand then update normally with e.g.
That looks cleaner,
but I also have no way to test that atm.Just got to test it. You do actually only need the first step, after that you can update as normal. The update then pulls in
tinysparql
automatically.wouldn't that leave the system with an unresolved dependency?
tinysparql now provides tracker3, so it is the correct replacement, it just doesn't apply that way because the replaces check is too narrow.
To come back to the underlying problem, I'm not sure we can do much here that would not involve PKGBUILD editing.
If this stays an isolated case, then I think pinning this issue should suffice.
Between the steps yes, but not after. As soon as one installs
tinysparql
(which happens in step 2), tracker3 is provided by that package, as you say.Only caveat would be that its marked as explicitly installed in this case, but that could be fixed by(does not happen with the solution above)pacman -D --asdeps tinysparql
I guess.edit: just noticed that I mixed up the options on step 2, fixed now.
I think that is ok. I don't expect that Arch developers will change their package for third party repositories
GNOME just renamed the tracker3 to tinysparql, see https://blogs.gnome.org/carlosg/2024/07/14/goodbye-tracker-hello-tinysparql-and-localsearch/
I solved this problem via downloading the official old tracker3 package from Arch Linux Archive website: https://archive.archlinux.org/packages/t/tracker3/tracker3-3.7.3-2-x86_64.pkg.tar.zst
And downgrade the tracker3 3.7.3-2.1 to tracker3 3.7.3-2 by pacman -U tracker3-3.7.3-2-x86_64.pkg.tar.zst,
and then update as normal.
this should be solved by now, closing