Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Failure to prepare transaction when trying to update (Read 434 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

[SOLVED] Failure to prepare transaction when trying to update

Code: [Select]
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 lib32 is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libelf (0.190-1) breaks dependency 'libelf=0.189' required by lib32-libelf
:: installing nvidia-utils (545.29.02-2) breaks dependency 'nvidia-utils=535.113.01' required by lib32-nvidia-utils

It's not a huge deal, I suppose we just have to wait for the mirrors to sync up? Just wondering if someone else noticed this starting today as well. Thanks.

Re: Failure to prepare transaction when trying to update

Reply #1 –
i came here to post about the ame thing also.


lib32-nvidia-utils also needs an update b4 i can update.


:: installing libelf (0.190-1) breaks dependency 'libelf=0.189' required by lib32-libelf
:: installing nvidia-utils (545.29.02-2) breaks dependency 'nvidia-utils=535.113.01' required by lib32-nvidia-utils

Cat Herders of Linux

Re: Failure to prepare transaction when trying to update

Reply #2 –
I'm using
pacman -Syu --ignore libelf
until they fix the issue with the 32-bit version. I only have the lib32 repo enabled because of steam :(

EDIT: They fixed it. lib32-libelf is now also on 0.190.

Re: Failure to prepare transaction when trying to update

Reply #3 –
all seems well def once mirrors updated completely... elf and nvidia are behaving nice.  like that 6.6 kernel update too yesterday..
Cat Herders of Linux

Re: Failure to prepare transaction when trying to update

Reply #4 –
Can confirm, fixed today morning. Didn't have to do any manual changes. Thanks maintainers!