I don’t know if this is a good tip or a terrible tip but I think it works well. I update every day. This morning, update error about dependencies. Tried lots of things, no go. However, Discover lists the available updates as well and I was able to update most of the Apps one-by-one until I was left with the three Apps which caused the dependency error. Ignoring these in pacman.conf allowed the update to progress as usual.
I’m suggestion this because it sometimes is not easy to single out the App update which breaks something else, doing it this way allows individual update until you single out the problem one.
Then go to the developers for more specific help.
Lastly, I’ve been testing other distros to see what I’m missing (Nothing it seems!) but some of the other distros, CachyOS for example, give a restart warning after a system update. Do we think this is something we could have in Garuda?
Even in Win11 you wouldn’t do this (they have insider updates but they still break stuff in their main OS), that have to break something, personally i update 1 time a week at most for all my devices .
They don’t officially support partial updates and only recommend garuda-update.
Not sure why you have dependency errors, since within Garuda pacman repositories, there are rarely dependency issues. Outside sources can cause dependency issues. I have had one AUR package introduce dependency issue, and I am not sure if I might have cause that issue.
Ignoring packages is fine… You can use downgrade as well, or just uninstall non essential packages.
Well, Garuda continues to work, if I allow it to update the three ignored apps, Howdy, my facial recognition software, fails to work and I use this multiple times a day so it is a great inconvenience. It is definitely Howdy’s issue but there seems no appetite for a fix.
The joys of using a rolling release.
I don’t disagree. I can shoot out my tires and put saand in my oil and the car will still drive. Probably pretty badly and no one would say that’s a good way to maintain a vehicle.
I’m just saying your tip is to create a partial update, which is neither recommended nor supported by any Arch or Arch based distro I’m aware of. Unless I’m wrong on that and they do here (that doesn’t sound like the folks I know though). . .
On updating daily, (or multiple times per day). While some would say this is excessive and not strictly required, there is one major benefit. Updating daily results in a far smaller number of packages that require updating. The less the number of packages updated at one time, the easier it is to determine exactly which individual package update has introduced a bug or regression. If you wait a longer time between updates, you will likely have hundreds of packages updated in your Pacman log. Finding the exact package that introduced a bug is far more difficult when you have hundreds of potential culprits, rather than a handful of packages to troubleshoot.
Partial updates are not supported on any Arch based system. The more critical the package, the more likely it is to cause problems if the updates are held back. It is always best to try avoid freezing any package update when a conflict occurs. My default is to always try to uninstall any package causing conflicts rather than holding a package at an outdated version. This is not always possible to do with very important packages with a lot of dependencies. In some cases an alternate package can be installed that performs the same function that doesn’t cause problems. The least recommended way to deal with package conflicts is by holding at an older package version.
Thanks tbg. The three packages which are held are -
IgnorePkg = ffmpeg libplacebo mpv
Attempts at uninstalling, reinstalling, or updating fail in a big way so, unless you have a magical way of fixing it, my system remains the same, working, even if I am flying by the seat of my pants.
So, in an effort to resolve this do you have any suggestions to clear these errors -
: ffmpeg is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] y
resolving dependencies...
warning: ignoring package libplacebo-7.349.0-1
looking for conflicting packages...
:: libplacebo-git-7.349.0.3572.g1fd3c7bd-1 and libplacebo-6.338.2-7 are in conflict. Remove libplacebo? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing libplacebo breaks dependency 'libplacebo.so=338-64' required by ffmpeg6.1
:: removing libplacebo breaks dependency 'libplacebo.so=338-64' required by mpv
I would also remove those other pkgs from the IgnorePkg & reboot before/after attempting to update.
Also, you are the sole person responsible for your predicament, not anyone else. The “fix” is don’t do it. If you didn’t know about partial updates and the problems they can cause with major components–like ffmpeg–you do now.
F. Scott Fitzgerald said something about learning this way…rocky shore…
but whatever works m8. The end result matters.
