For those who are scared by the pacnew merging process or terminal shy, take it from me, a lot of the comparing and merging process can be done with graphical tools instead of terminal.
I'm not ashamed to admit to using GUI exclusively for this. If you're using KDE Plasma, it's pretty easy.
choose a graphical file comparison application you are comfortable with. I use Meld no matter what DE I'm running because I'm so used to it, yes even in Plasma (pls don't turn this thread into a which program is better thread)
open both the original conf and the conf.pacnew file for comparison in Meld (or whatever program you prefer)
examine the pacnew file to see where it differs from original conf file. Use common sense to assess each difference to see you should move each pacnew difference over to the conf file or to ignore it. In the case of the current pacman.conf merge, the devs here have already posted and pinned a post to tell you which changes to move over (or to confirm already exist from the orig conf file).
So instead of blindly copying over the whole pacnew file to replace the orig conf file on your system (this will wipe out the chaotic-aur repo entry, Colours and ILoveCandy since of course vanilla pacman6 configuration won't have these lines!), you just assess, pick and choose certain lines from pacnew file and move them over to orig conf file in Meld
once you are happy with how the amended pacman.conf file looks in Meld, I "SELECT ALL" and copy the text in pacman.conf from Meld. Then I open /etc/pacman.conf in KATE, "SELECT ALL" the text in Kate and PASTE the text copied from Meld.
Then click on SAVE in KATE. You will be asked for your user password since you are seeking to amend a file in root system. Enter password and it's all done. Close Meld, and discard all the changes you made there. I keep my comparison and merging work separate and without elevated privileges, from the final saving of the changes.
All done without touching command line. It can be learned. Once you have got more comfortable with things, who knows, you may decide just to do the whole thing in terminal.
I've been running Garuda since some 4 months ago and already encountered some system problems such as when plymouth didn't allow system booting and now pacman. I have used several distros throughout the past 15 years and so far Garuda is the one I have booted more enthusiastically than any other before, followed Sabayon , Mint Cinnamon, Confusion (old distro), puppy, etc. Nevertheless, GAruda is al so the one I have to keep my fingers crossed each time I boot.
Ok, so you did share a good piece of advice there, I absolutely agree on your statement. So here comes the question:
Does Garuda have a Stable and Static Distro?
I wish I had more time to tinker but just don't...
Thanks in advance
If you have no faith things break as you are willing it to.
Also pacman did not break anything 3rd party apps broke, nothing to do with Arch or Garuda.
Simply if you get a puncture is the car manufacturer to blame or if the new sound system in your house fail do you blame the builder?
I decided to do some homework and did it all, including installing paru
This is my output when trying to upgradenow...
.%;888:8898898: simba@simba-gl553vd
x;XxXB%89b8:b8%b88: -------------------
.8Xxd 8X:. OS: Garuda Linux x86_64
.8Xx; 8x:. Kernel: 5.12.9-zen1-1-zen
.tt8x .d x88; Uptime: 0 mins
.@8x8; .db: xx@;
,tSXX° .bbbbbbbbbbbbbbbbbbbB8x@; Packages: 1695 (pacman)
.SXxx bBBBBBBBBBBBBBBBBBBBbSBX8; Shell: fish
,888S pd! Resolution: 3840x1080
8X88/ q Terminal: Alacritty
GBB.
x%88 d888@8@X@X@X88X@@XX@@X@8@X. CPU: Intel i5-7300HQ (4) @ 3.5GHz
dxXd dB8b8b8B8B08bB88b998888b88x. Memory: 2375MiB / 11854MiB (20%)
dxx8o .@@;.
dx88 .t@x.
d:SS@8ba89aa67a853Sxxad.
.d988999889889899dd.
⏎
╭─simba@simba in ~
╰─λ paru -Syu
[sudo] password for simba:
:: Synchronising package databases...
core is up to date
extra is up to date
chaotic-aur 1088,6 KiB 393 KiB/s 00:03 [################################] 100%
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace libcanberra-pulse with extra/libcanberra? [Y/n] y
resolving dependencies...
looking for conflicting packages...
Packages (35) alsa-lib-1.2.5-2 alsa-plugins-1:1.2.5-2 alsa-topology-conf-1.2.5-1 alsa-ucm-conf-1.2.5-1 at-spi2-core-2.40.2-1
blender-17:2.93.0-2 calibre-5.20.0-1 elfutils-0.185-1 evolution-data-server-3.40.2-1 fzf-0.27.2-1 gnome-boxes-40.2-1
gnome-maps-40.2-1 krita-4.4.3-4 latte-dock-git-0.9.91.r57.g45825996-1 lib32-libelf-0.185-1 lib32-ocl-icd-2.3.0-1
libcanberra-0.30+2+gc0620e4-4 libcanberra-pulse-0.30+2+gc0620e4-3 [removal] libelf-0.185-1 libogg-1.3.5-1 libqmi-1.28.6-1
librsvg-2:2.50.7-1 obs-studio-27.0.0-1 ocl-icd-2.3.0-1 opencolorio-2.0.1-2 opencolorio1-1.1.1-3 openimageio-2.2.15.1-1
osinfo-db-20210531-1 pulseaudio-alsa-1:1.2.5-2 qt5-declarative-5.15.2+kde+r28-1 timeshift-20.11.1+3+g08d0e59-4
vte-common-0.64.2-1 vte3-0.64.2-1 whoogle-git-0.5.3_r378.g0be639a-1 wine-6.10-1
Total Installed Size: 1256,04 MiB
Net Upgrade Size: 12,88 MiB
:: Proceed with installation? [Y/n] y
(34/34) checking keys in keyring [##################################################] 100%
(34/34) checking package integrity [##################################################] 100%
(34/34) loading package files [##################################################] 100%
(34/34) checking for file conflicts [##################################################] 100%
(35/35) checking available disk space [##################################################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
E: ts: Failed to get partition list.
E: System disk not found!
Unable to run timeshift-autosnap! Please close Timeshift and try again. Script will now exit...
error: command failed to execute correctly
error: failed to commit transaction (failed to run transaction hooks)
Errors occurred, no packages were upgraded.
╭─simba@simba in ~ took 21s
[🔴] ×
Timeshift issues?
This also occurred after the merging pacman.conf files..
Shall I just reinstall a new image for the sake of saving everyone's time?
Oh, and why are my drives often so active? you'd think I'm running m$...
Oh, and:
