New ‘garuda-update’ this morning but when installing, it fails with this error;
error: failed to commit transaction (conflicting files)
garuda-update: /etc/garuda/garuda-update/config exists in filesystem
Errors occurred, no packages were upgraded.
sudo pacman -Syu --overwrite '*'
:: Paketdatenbanken werden synchronisiert …
garuda ist aktuell
core ist aktuell
extra ist aktuell
multilib ist aktuell
chaotic-aur ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Warnung: whoogle-git: Lokale Version (_r758.ge9c4ed6-1) ist neuer als chaotic-aur (0.8.3.r25.gcdf0b50-1)
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Paket (5) Alte Version Neue Version Netto-Veränderung
extra/blender 17:3.6.4-2 17:3.6.4-3 -1,20 MiB
garuda/garuda-update 4.2.3-1 4.2.4-1 0,00 MiB
extra/imagemagick 7.1.1.20-1 7.1.1.21-1 0,00 MiB
extra/openvdb 10.0.1-5 10.1.0-1 -3,92 MiB
extra/protobuf 24.3-1 24.4-1 0,00 MiB
Gesamtgröße der installierten Pakete: 722,69 MiB
Größendifferenz der Aktualisierung: -5,13 MiB
:: Installation fortsetzen? [J/n]
(5/5) Schlüssel im Schlüsselbund werden geprüft [--------------------------------------------] 100%
(5/5) Paket-Integrität wird überprüft [--------------------------------------------] 100%
(5/5) Paket-Dateien werden geladen [--------------------------------------------] 100%
(5/5) Auf Dateikonflikte wird geprüft [--------------------------------------------] 100%
(5/5) Verfügbarer Festplattenspeicher wird ermittelt [--------------------------------------------] 100%
:: Pre-transaction-Hooks werden gestartet …
(1/1) Performing snapper pre snapshots for the following configurations...
==> root: 975
:: Paketänderungen werden verarbeitet …
(1/5) Aktualisiert wird openvdb [--------------------------------------------] 100%
(2/5) Aktualisiert wird blender [--------------------------------------------] 100%
(3/5) Aktualisiert wird garuda-update [--------------------------------------------] 100%
(4/5) Aktualisiert wird imagemagick [--------------------------------------------] 100%
Neue optionale Abhängigkeiten für imagemagick
libjpeg-turbo: JPEG support [Installiert]
(5/5) Aktualisiert wird protobuf [--------------------------------------------] 100%
:: Post-transaction-Hooks werden gestartet …
(1/9) Arming ConditionNeedsUpdate...
(2/9) Foreign/AUR package notification
ananicy-rules 1.r129.8ac5d97-1
mtplayer 14__2023.05.22-1
python-xpybutil 0.0.6-5
(3/9) Orphaned package notification...
libvips 8.14.5-1
(4/9) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/pacman.d/mirrorlist.pacnew
Please check and merge
(5/9) Warn about old perl modules
(6/9) Updating icon theme caches...
(7/9) Updating the desktop file MIME type cache...
(8/9) Performing snapper post snapshots for the following configurations...
==> root: 976
(9/9) Syncing all file systems...
╭─sgs@pro in ~ as 🧙 took 5s
🕙 17:38:10
╰─λ upd
:: Paketdatenbanken werden synchronisiert …
garuda ist aktuell
core ist aktuell
extra ist aktuell
multilib ist aktuell
chaotic-aur ist aktuell
--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵
:: Paketdatenbanken werden synchronisiert …
garuda wird heruntergeladen …
core wird heruntergeladen …
extra wird heruntergeladen …
multilib wird heruntergeladen …
chaotic-aur wird heruntergeladen …
:: Starting full system upgrade...
warning: whoogle-git: local (_r758.ge9c4ed6-1) is newer than chaotic-aur (0.8.3.r25.gcdf0b50-1)
there is nothing to do
Failed to start updatedb.service: Unit var-tmp.mount is masked.
I also have this error, but i can remember me that i have disabled the mirrorsearch with the option SKIP_MIRRORLIST=1. I think that was the reason that this file exists here, and every person who add this option ( maybe there are more options that can be set here ?) will have this problem.
I think you are correct. I also removed the ‘#’ on two of the options, including disabling mirror search. I believe this is the culprit as to why the config file cannot be overwritten.
Okay, this is awkward but I’m pretty sure this whole thing is my fault.
I added a MR to deploy /etc/garuda/garuda-update/config a few weeks ago, as a fully commented-out file to make interacting with these options more accessible. As it was, no one would ever know these options even exist unless they read the wiki page, set up the missing directory, and added the file manually.
Apparently, the way I did it is creating a problem for anyone who already had this file set up. What I (and probably everyone else) would have preferred would have been if a .pacnew file was created, although apparently that doesn’t just magically happen on it’s own.
For next time, I’ll have to figure out how to set that up.
In the meanwhile, another option instead of overwriting the file would be to move the existing config to backup before taking the update.