Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

pacman refuses to upgrade my Arch Linux system because of a conflict between open-vm-tools-modules and the linux kernel package:

$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
 community 1988.4 KiB   970K/s 00:02 [#############################################################################] 100%
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: open-vm-tools-modules: requires linux<3.10

Do you have any suggestions how to analyze the problem?

share|improve this question
add comment

3 Answers

up vote 1 down vote accepted

You should uninstall the openvm-tools-modules package because it's not provided by Arch Linux (anymore?), so it's not going to be updated to depend on a newer kernel. This has been "announced" on the arch-dev-public mailing list.

share|improve this answer
    
Thanks, I switched my accepted answer. Seems to be the right way. I also encountered no downsides in removing open-vm-tools-modules so far. –  Philipp Claßen Jul 28 '13 at 14:43
add comment

Braiam's answer covered most of the possible solutions. There is one additional solution. You can upgrade the system without upgrading the kernel.

pacman -Syu --ignore linux

If you have the package linux-headers installed, you should ignore it as well.

pacman -Syu --ignore linux,linux-headers
share|improve this answer
add comment

There are two possible solutions:

  1. Wait for Arch to update open-vm-tools-modules, so it can depends of recent kernels.
  2. Uninstall open-vm-tools-modules.
  3. Force your way through with the --force switch (Not Recommended!)

The reason why you can't upgrade is because the new kernel hasn't be tested or have new additions that breaks the packages, or the packages was made to work just with previous kernel flawlessly and must wait for new kernels to be tested and make changes if needed.

I don't think you really need the new kernel if the current works fine.

share|improve this answer
    
@evanteitelman the "two" was intentional, so as do not use the third :/ –  Braiam Jul 27 '13 at 16:03
    
My mistake. I thought it was a typo. –  Evan Teitelman Jul 27 '13 at 16:24
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.