Trying to install the KDE-git edition via chaotic-aur/kde-git-meta

[GarCom]

Hi to all ,

I'm on Garuda KDE Dr460nized Gaming Edition and want to try to install the KDE-git edition via chaotic-aur/kde-git-meta

I get an error:

Garuda's PrivateBin

Cannot ?

Thanks in advance. See you.

[BluishHumility]

@GarCom

error: failed to prepare transaction (could not satisfy dependencies)
:: removing kwin breaks dependency 'kwin>=5.27.0' required by kwin-effects-sliding-notifications

The package that is causing the conflict is basically a standalone package.

pacman -Sii kwin-effects-sliding-notifications
Repository      : chaotic-aur
Name            : kwin-effects-sliding-notifications
Version         : 1.5.0-1
Description     : Sliding animation for notification windows
Architecture    : x86_64
URL             : https://github.com/zzag/kwin-effects-sliding-notifications
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : kwin>=5.27.0
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Download Size   : 16.23 KiB
Installed Size  : 37.91 KiB
Packager        : Nico Jensch <[email protected]>
Build Date      : Thu 16 Feb 2023 08:09:25 AM EST
MD5 Sum         : d3fa8ceb9652c43d790e5366d999db9d
SHA-256 Sum     : 39b7b40fbd23e879c05072f60f1e39d47eaf47fdf222e92d51bdd73993a08913
Signatures      : 0706B90D37D9B881

Just uninstall it, then try again. If you want to keep the sliding animation package, figure out how to install it after the dust settles from this large package maintenance task you are doing.

A couple considerations:

• Switching to a base of mostly git packages means you are going to be using software in basically its least-tested state. There are more bugs, and a higher likelihood things will come down broken and you will have to figure out what to do. If this simple dependency conflict has stumped you, then it is possible this package base might not be what you want.
• You should not run yay as root. Best practice will be to not even log in as root in the first place, unless you have to for some reason. You should try to run your programs from as least-privileged a user as possible. It is easy to break stuff as root, even with commands that are run correctly.