Arch Linux

corrupt

Member

Registered: 2007-06-25

Posts: 74

db4.1 needs gcc-libs which is not in the package set

sudo pacman -Syu
:: Synchronizing package databases...
 current is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
warning: openal: forcing upgrade to version 0.0.8-4
resolving dependencies...
error: cannot resolve dependencies for "db4.1" ("gcc-libs" is not in the package set)
error: failed to prepare transaction (could not satisfy dependencies)
:: db4.1 requires gcc-libs

What to do?
I cannot simply remove it.

Last edited by corrupt (2007-09-21 18:26:49)

tardo

Member

Registered: 2006-07-15

Posts: 526

Re: db4.1 needs gcc-libs which is not in the package set

sudo sed -i -e 's|current|core|g' /etc/pacman.conf
sudo pacman -Syu

corrupt

Member

Registered: 2007-06-25

Posts: 74

Re: db4.1 needs gcc-libs which is not in the package set

after sudo sed -i -e 's|current|core|g' /etc/pacman.conf

sudo pacman -Syu
:: Synchronizing package databases...
error: failed to synchronize core:
 extra                    325.7K  415.6K/s 00:00:01 [#####################] 100%
 community                300.4K  435.7K/s 00:00:01 [#####################] 100%
:: Starting full system upgrade...
warning: openal: forcing upgrade to version 0.0.8-4
resolving dependencies...
error: cannot resolve dependencies for "aspell" ("gcc-libs" is not in the package set)
error: failed to prepare transaction (could not satisfy dependencies)
:: aspell requires gcc-libs

Last edited by corrupt (2007-09-22 13:47:06)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: db4.1 needs gcc-libs which is not in the package set

What version of pacman is installed?

corrupt

Member

Registered: 2007-06-25

Posts: 74

Re: db4.1 needs gcc-libs which is not in the package set

Pacman v3.0.5 - libalpm v1.0.0

corrupt

Member

Registered: 2007-06-25

Posts: 74

Re: db4.1 needs gcc-libs which is not in the package set

Ok, figured it out. My pacman.conf was set to core but there wasn't core file in my dir /etc/pacman.d. So I set to current and did pacman upgrade to 3.0.6. Now everything is fine.