I moved about a month ago and haven’t touched my pc a whole lot from before packing it away and finally getting around to unpacking it.

I’m running CachyOS and finally got around to unburying it, and after trying to run a system update I’m met with this:

sudo pacman -Syu
:: Synchronizing package databases...
 cachyos-v4 is up to date
 cachyos-core-v4 is up to date
 cachyos-extra-v4 is up to date
 cachyos is up to date
 core is up to date
 extra is up to date
 multilib is up to date
 DEB_Arch_Extra         10.1 KiB  12.5 KiB/s 00:01 [---------------------] 100%
:: Starting full system upgrade...
warning: gtk2: local (2.24.33-5.1) is newer than cachyos (2.24.33-5)
:: Replace lib32-vulkan-mesa-device-select with cachyos/lib32-vulkan-mesa-implicit-layers? [Y/n] y
warning: libpng12: local (1.2.59-2.1) is newer than cachyos (1.2.59-2)
:: Replace vi with extra/ex-vi-compat? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: vulkan-mesa-implicit-layers-1:25.3.5-2 and vulkan-mesa-device-select-1:25.2.7-2 are in conflict

I’m not super technologically inclined, not completely illiterate but no expert for sure. Usually I’d update my system regularly but with the move and otherwise being extremely busy lately I’m only getting around to it now. I tried looking it up first but I’m not sure if I just used the wrong search queries or what, but I couldn’t get a good answer anywhere, so I thought I’d try here.

Thanks in advance for any help. I really do appreciate it.

  • Ooops@feddit.org
    3·
    5 hours ago

    That’s a totally separate error… It can happen that the keyring itself is so out of date that it blocks the update, and with it the upgrade to a newer keyring. For this reason it’s often safer after a long time to do pacman -Syu cachyos-keyring (pretending I guesse right and that’s the name of the package) first to avoid the whole update getting blocked by signature with an out-of-date-key. Yet that should not apply here.

    But Ignoring the warnings you get for now… This looks like vulkan-mesa-implicit-layers did not replace vulkan-mesa-device-select but now the 32bit library version lib32-vulkan-mesa-device is supposed to be replaced by cachyos/lib32-vulkan-mesa-implicit-layers, which would in turn need vulkan-mesa-implicit-layers as a dependency.

    What happens when you answer ‘no’ to that first question? Alternatively, is there anything keeping you from installing vulkan-mesa-implicit-layers (thus replacing vulkan-mesa-device-select)?

    • BurntWits@sh.itjust.worksOP
      1·
      5 hours ago

      Answering “n” gives me the same error still. Same with if I say no for both questions. In fact, any combination will always result in the same error.

      Probably a dumb question but how would I go about installing vulcan-mesa-implicit-layers?

      • Ooops@feddit.org
        1·
        6 minutes ago

        pacman -S vulcan-mesa-implicit-layers

        Which will then probably tell you that it conflicts with vulkan-mesa-device-select and asks if you want to replace it. Which might either work or just get you another conflict because vulkan-mesa-device-select is required by some other package.

        Btw… pacman -Qi <package name> usually tells you anything you need to know about a package. In this context mainly why it was installed (as a requirement for which package) and which other packages are required as a dependency.

        So maybe you should take one step back first. Check why 'vulkan-mesa-device-select` was installed in the first place. If it’s not dependency of something else you can either remove it (or replace it) alongside its lib32 version.

      • FauxLiving@lemmy.world
        1·
        29 minutes ago

        remove is -R

        so

        sudo pacman -R vulcan-mesa-implicit-layers

        You can force it to ignore dependencies (be careful doing this as it is bypassing an important safety check in the package manager), for example if you’re trying to remove a package that you’re going to replace with another one then you can ignore the dependency warning when you try to remove it.

        Use -Rdd to remove and ignore dependency checking.