[SOLVED] Pacman upgrade failed because of gcc-libs

I have the multilib version of gcc installed in my 64 bit system. Ten minutes ago I tried to upgrade with pacman -Syu and I got:
:: I seguenti pacchetti dovrebbero essere aggiornati prima :
pacman
:: Vuoi annullare l'operazione corrente
:: e aggiornare adesso questi pacchetti? [S/n]
risoluzione delle dipendenze in corso...
ricerca dei conflitti in corso...
:: gcc-libs e gcc-libs-multilib vanno in conflitto. Vuoi rimuovere gcc-libs-multilib? [s/N] n
errore: sono stati rilevati dei conflitti irrisolvibili
errore: impossibile eseguire l'operazione richiesta (dipendenze in conflitto)
:: gcc-libs e gcc-libs-multilib vanno in conflitto
It is in italian, but basically it complains about a conflict between the installed gcc-libs-multilib and the needed gcc-libs. gcc-libs-multilib provides gcc-libs, so why this kind of error? I thought my mirror could be out of sync but I get the same error also using mirrors.kernel.org.
Am I doing something wrong?
Last edited by snack (2012-02-18 17:30:59)

I did mean 'search the forums':
* https://bbs.archlinux.org/viewtopic.php?pid=1045658
* https://bbs.archlinux.org/viewtopic.php?pid=1049681
* https://bbs.archlinux.org/viewtopic.php?pid=1057624
* https://bbs.archlinux.org/viewtopic.php?pid=1054861
* https://bbs.archlinux.org/viewtopic.php?pid=1057459
* https://bbs.archlinux.org/viewtopic.php?id=134397

Similar Messages

Upgrade fails because of gcc-gcj

Full system upgrade fails because the following dependency cannot be satisfied.
:: gcc-gcj: requires gcc=4.6.1
Any solution?
ty

(sigh)
I am still stuck;
if I try to update (via pacman) either libtool/gcc-fortran I get that they cannot be updated because gcc-fortran/libtool and gcc-gcj need gcc 4.6.1
if I try to update (via yaourt) gcc-gcj it says that libtool AND gcc-fortran require gcc 4.6.1 (even though gcc-gcj is up to date)
My mirror says that gcc-fortran is at the version 4.6.2-1 and libtool at 2.4.2
My mirror is up to date
Basically I am stuck in a loop.
A solution would be to uninstall gcc-gcj and reinstall it, but pdftk depends on it, and last time I installed it it took something like two hours to complete, I would like to avoid that
Any suggestion?
(edit: thanks for the help!)
Last edited by miguelroboso (2011-11-01 20:56:51)

[Solved] pacman upgrade fail

When I try to upgrade pacman I get the following:
gordiegii@Ion-Arch ~]$ sudo pacman -S pacman
Password:
resolving dependencies...
looking for inter-conflicts...
Targets (1): pacman-4.0.3-1
Total Installed Size: 3.54 MiB
Proceed with installation? [Y/n]
(1/1) checking package integrity [###################################################] 100%
(1/1) loading package files [###################################################] 100%
(1/1) checking for file conflicts [###################################################] 100%
error: failed to commit transaction (conflicting files)
pacman: /usr/bin/cleanupdelta exists in filesystem
pacman: /usr/bin/makepkg exists in filesystem
pacman: /usr/bin/pacman exists in filesystem
pacman: /usr/bin/pacman-db-upgrade exists in filesystem
pacman: /usr/bin/pacman-key exists in filesystem
pacman: /usr/bin/pacman-optimize exists in filesystem
pacman: /usr/bin/pacsort exists in filesystem
pacman: /usr/bin/pactree exists in filesystem
pacman: /usr/bin/pkgdelta exists in filesystem
pacman: /usr/bin/rankmirrors exists in filesystem
pacman: /usr/bin/repo-add exists in filesystem
pacman: /usr/bin/repo-elephant exists in filesystem
pacman: /usr/bin/repo-remove exists in filesystem
pacman: /usr/bin/testdb exists in filesystem
pacman: /usr/bin/testpkg exists in filesystem
pacman: /usr/bin/vercmp exists in filesystem
pacman: /usr/include/alpm.h exists in filesystem
pacman: /usr/include/alpm_list.h exists in filesystem
pacman: /usr/lib/libalpm.a exists in filesystem
pacman: /usr/lib/libalpm.so exists in filesystem
pacman: /usr/lib/libalpm.so.7 exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ca/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/cs/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/da/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/de/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/el/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/es/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/fi/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/fr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/hu/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/it/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/kk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/lt/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/nb/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pl/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pt/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ro/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/ru/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/sv/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/tr/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/uk/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/libalpm.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman-scripts.mo exists in filesystem
pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman.mo exists in filesystem
pacman: /usr/share/man/man3/libalpm.3.gz exists in filesystem
pacman: /usr/share/man/man5/PKGBUILD.5.gz exists in filesystem
pacman: /usr/share/man/man5/makepkg.conf.5.gz exists in filesystem
pacman: /usr/share/man/man5/pacman.conf.5.gz exists in filesystem
pacman: /usr/share/man/man8/makepkg.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacman-key.8.gz exists in filesystem
pacman: /usr/share/man/man8/pacman.8.gz exists in filesystem
pacman: /usr/share/man/man8/pkgdelta.8.gz exists in filesystem
pacman: /usr/share/man/man8/repo-add.8.gz exists in filesystem
pacman: /usr/share/man/man8/repo-remove.8.gz exists in filesystem
pacman: /usr/share/man/man8/vercmp.8.gz exists in filesystem
pacman: /usr/share/pacman/ChangeLog.proto exists in filesystem
pacman: /usr/share/pacman/PKGBUILD-split.proto exists in filesystem
pacman: /usr/share/pacman/PKGBUILD.proto exists in filesystem
pacman: /usr/share/pacman/proto.install exists in filesystem
pacman: /usr/share/zsh/site-functions/_pacman exists in filesystem
Errors occurred, no packages were upgraded.
[gordiegii@Ion-Arch ~]$
Has anybody seen this or have any idea how to fix it?
Should I just delete all these files?
I was getting a gcc / gcc-libs error before but reinstalling gcc as per other forum help fixed that.
Last edited by GordieGii (2012-04-29 15:29:26)

@Gcool: I did a quick search and could not find anything that matched my symptoms. The only things I found that seemed to apply were the gcc / gcc-libs issue which I resolved and merging my pacman.conf.pacnew file into pacman.conf file (only two non-comments were new and they didn't seem related).
Perhaps I can't assess the applicability of a post to my symptoms.
@karol: I did -Syu, as I always do, but this time I got this:
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
I tried both 'Yes' and 'no' and both failed. 'No' took much longer because it had to download a couple hundred packages (I have been trying to resolve this myself for over a week and the list keeps getting longer) before failing so I switched to just pacman.
Pacman was in the list of packages and I couldn't figure out how to exclude it to see if the others would update. Reinstalling gcc worked.
[gordiegii@Ion-Arch man]$ stat -c %s $(find /var/lib/pacman/local -name "pacman-4*")/files
0
[gordiegii@Ion-Arch man]$
Please pardon my newbieness, I came from Ubuntu when GnomeBloat became too much for my Intel ATOM and am still learning the Arch way.

[Solved] pacman -Syu fails because of libreoffice conflict

I haven't done a system update for a little while - now when I attempt pacman -Syu, I get a failure due to libreoffice conflicts:
[peter@desktop AURBuilds]$ sudo pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed retrieving file 'archVMrepo.db' from repo.ktz.me : Connection timed out after 10000 milliseconds
error: failed to update archVMrepo (download library error)
:: Starting full system upgrade...
:: Replace libreoffice-still-base with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-calc with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-common with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-draw with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-gnome with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-impress with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-kde4 with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-math with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-postgresql-connector with extra/libreoffice-still? [Y/n]
:: Replace libreoffice-still-writer with extra/libreoffice-still? [Y/n]
resolving dependencies...
warning: dependency cycle detected:
warning: freetype2 will be installed before its harfbuzz dependency
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2 dependency
looking for inter-conflicts...
:: libreoffice-still-sdk and libreoffice-still-sdk-doc are in conflict. Remove libreoffice-still-sdk-doc? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libreoffice-still-sdk and libreoffice-still-sdk-doc are in conflict
[peter@desktop AURBuilds]$
How do I resolve this?
Last edited by PeterBell (2015-02-08 02:18:43)

Trilby wrote:What are you doing? Wine was never a problem.
I'm sorry - I was trying to help myself by following the errors, as reported. It seemed that my problem stemmed from lib32-harfbuzz and lib32-freetype2, so I was attempting to remove those. However, wine was dependent on them so had to be removed first.
I told you want needed to be done. If you ignore provided advice and instead do other random things (without actually specifying what you are doing) then no one can help you.
Indeed, your posting did point me in the right direction, but did not appear until after I had posted about my experiment with wine. Wine is no great loss, anyway - I've never managed to achieve anything useful with it!
As you indicated, my problems were resolved by updating package-query:
yaourt package-query
Edit: In my searching, I did come across advice to use pacaur instead of yaourt - I'm not sure whether this would have made any difference in my case.
My analysis, wrongly or rightly, is this:
1) AUR packages (some?) appear to list pacman version as a dependency. "pacman -Syu" was attempting to update itself to 4.2 which broke the dependency (<4.2), even though 4.1.x was running at the time - there's a recipe for confusion! This was resolved by rebuilding package-query before updating the rest of the system, because the latest version has updated the pacman dependency.
2) lib32-harfbuzz and lib32-freetype2 (both AUR packages?) were in conflict - they cannot (must not) be dependent on each other. This was resolved by pulling later versions during the rebuild of package-query.
3) The libreoffice problem was not an issue. My mistake was that I ignored a lifetime of experience working in IT - I concentrated on the last-reported error rather than the first! All I can say in my defence is that eight years of retirement must have addled my brain!
In short, two, unrelated, errors, conflated with another, relatively insignificant, error message, led me on a wild goose chase.
I thank you for your wise counsel!
Last edited by PeterBell (2015-02-08 02:21:24)

Pacman upgrade fails because of unsatisfied pacman-color dependency *

Hello, my most recent attempt to run pacman -Suy results in pacman trying to update itslef and failing:
:: Synchronizing package databases...
core 35.4K 500.1K/s 00:00:00
[#####################] 100%
extra 453.0K 2.2M/s 00:00:00
[#####################] 100%
community 377.2K 2.2M/s 00:00:00
[#####################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] Y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: pacman-color: requires pacman=3.3.3
Any idea how to fix this?
Last edited by .:B:. (2010-06-28 20:26:09)

There are a couple of threads about this.
1.Uninstall pacman-color
2. pacman -Syu
3. Reinstall pacman-color
4. Put the kettle on...
#edit too much detail...
Last edited by jasonwryan (2010-06-28 19:48:50)

[SOLVED]Full upgrade fails after new install

Hello,
Please note before reading that I know about the recent changes with the /lib symlink to /usr/lib and the filesystem (I read the home page).
After a fresh install, I try to upgrade the system :
pacman -Syy && pacman -Syu : it asks for pacman update, I say yes.
pacman -S pacman : fails because of glibc
pacman -S pacman --ignore glibc : fails, won't upgrade because glibc it's a dependency of pacman
pacman -Syu : say no to pacman upgrade, fails because of glibc and filesystem
pacman -Syu --ignore glibc --ignore fliesystem : upgrade almost nothing because most of the packages (~400M) need glibc
I can't upgrade anything at the end...
Thanks for any help
Last edited by John0000 (2012-07-19 14:52:17)

If either of this steps does not work (e.g. due to dependency version issues, file conflicts in /lib), refer to this G U I D E for more detailed instructions on performing this upgrade.
Did you read this guide?
There is thread about it also: https://bbs.archlinux.org/viewtopic.php?id=144620
And Allan wrote a blog entry about upgrading from core installation: http://allanmcrae.com/2012/07/updating- … e-install/
BTW as Pres suggested go with the net-install, core installation was always kind of a fallback for me and I had to do this just once because of network troubles. It just doesn't make much sense to do core installation if there is no holdback because with first pacman -Syu you'll end up downloading the same amount of data as if you would do a clean net-install, and it's faster and you probably won't get conflicts accumulated from year or so.
Last edited by masteryod (2012-07-19 14:38:38)

[SOLVED] pacman update fails: gcc requires gcc-libs=4.7.0-3

Hi
I ran pacman -Syu this morning and there's an update to pacman to install first, so I say yes but it fails like this:
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: requires gcc-libs=4.7.0-3
But I have gcc-libs 4.7.0-3 installed:
pacman -Qs gcc-libs
local/gcc-libs 4.7.0-3 (base)
Runtime libraries shipped by GCC
So what's going on?
Last edited by useradded (2012-04-11 08:08:09)

How might that break pacman? Assuming databases are current, is running
pacman -S pacman
followed by
pacman -Syu
different from what pacman itself is trying to do?
Is the message that pacman should be updated first just wrong?
So is this what you should do?
$ pacman -Syu
Recent ML chatter: linux(2)
:: Synchronizing package databases...
core 101.8 KiB 480K/s 00:00 [########################################] 100%
extra 1385.2 KiB 832K/s 00:02 [########################################] 100%
community 1636.1 KiB 810K/s 00:02 [########################################] 100%
multilib 86.4 KiB 522K/s 00:00 [########################################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
:: gcc-libs and gcc-libs-multilib are in conflict. Remove gcc-libs-multilib? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc-multilib: requires gcc-libs-multilib=4.7.0-3
No pacnew files to update.
$ pacman -Syu
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] N
I thought that itself might break pacman, which is why I updated pacman on its own. So I obviously don't get how it works...
Plus, why did you say "Or, just..." which suggests it is an alternative method rather than a better one...?
Last edited by cfr (2012-04-11 22:49:15)

[SOLVED] pacman upgrade won't work because of unresolved dependency

Hey all,
I tried a pacman -Syyu today and it found some things and said:
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: requires gcc-libs=4.6.2-6
I have gcc-libs=4.6.2-7 and I apparently need 4.6.2-6 but I can't change anything without pacman, and pacman won't change anything without updating itself first, and it can't because of this unmet dependency, so there's a stalemate.
Any ideas what to do?
Last edited by jdoggsc (2012-02-13 21:00:47)

Awebb wrote:What's a repost?
http://www.urbandictionary.com/define.php?term=repost

[SOLVED]pacman upgrade: error# failed to prepare transaction

Whenever I am trying to install some packages using pacman, I get a message to upgrade pacman. When I say 'yes', I get an error message.
##code_begin##
[root@arch matrix]# pacman -S libreoffice
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y
resolving dependencies...
warning: dependency cycle detected:
warning: udev will be installed before its util-linux dependency
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: requires gcc-libs=4.7.0-3
[root@arch matrix]#
##code_end##
This started after adding a new mirror and performing "pacman -Syu" (I was trying to install firefox in arch, which didn't go through even with different mirrors).
What should I do now to upgrade pacman?
Last edited by matrix13 (2012-04-11 14:48:24)

Anyone else, looking at this, look at https://bbs.archlinux.org/viewtopic.php … 3#p1086153 which suggests the above method could break pacman (but I don't understand why yet).

[SOLVED] Pacman Upgrade Issue

Hello,
I upgraded Pacman to the latest version and I may have messed up the .pacnew files, not sure. Anyhow here's the issue I'm currently facing:
[richard@rh-laptop ~]$ su root
Password:
[root@rh-laptop richard]# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: cpufrequtils: forcing upgrade to version 004-1
warning: iproute: forcing upgrade to version 2.6.25-1
warning: vlc: forcing upgrade to version 0.8.6i-3
warning: xf86-video-vesa: forcing upgrade to version 1.3.0-6
resolving dependencies...
warning: provider package was selected (giflib provides libungif)
looking for inter-conflicts...
Targets (155): a52dec-0.7.4-4 gpm-1.20.5-1 aalib-1.4rc5-5 apr-1.3.2-2
gcc-libs-4.3.1-3 pcre-7.7-2 glib2-2.16.5-1 avahi-0.6.23-1
bash-3.2.039-2 bzip2-1.0.5-3 cdparanoia-10.1-1
zlib-1.2.3.3-2 file-4.25-1 cdrkit-1.1.8-1 cpufrequtils-004-1
desktop-file-utils-0.15-1 gnome-desktop-2.22.3-1 eog-2.22.3-1
esd-0.2.39-1 gnome-keyring-2.22.3-1 gnutls-2.4.1-1
heimdal-1.2-1 libpng-1.2.29-1 libcups-1.3.8-2
randrproto-1.2.2-1 libxrandr-1.2.3-1 freetype2-2.3.7-1
fontconfig-2.6.0-2 libxft-2.1.13-1 pango-1.20.5-1
gtk2-2.12.11-3 poppler-0.8.4-1 poppler-glib-0.8.4-1
evince-2.22.2-3 libsoup-2.4.1-2
evolution-data-server-2.22.3-2 faad2-2.6.1-1
filesystem-2008.07-1 fakeroot-1.9.5-1 lame-3.98-1
x264-20080625-1 ffmpeg-20080715-3 file-roller-2.22.4-1
wxgtk-2.8.8-1 filezilla-3.1.1.1-1 hunspell-1.2.6-1
xulrunner-1.9.0.1-2 mime-types-1.0-1 firefox-3.0.1-2
flex-2.5.35-1 gail-1.22.3-1 gcalctool-5.22.3-1 gcc-4.3.1-3
ghostscript-8.63-3 libgtop-2.22.3-1 libgksu-2.0.7-1
gksu-2.0.0-3 glibmm-2.16.4-2 gnash-common-0.8.3-3
gucharmap-2.22.3-1 xorg-xkb-utils-7.3-1
xkeyboard-config-1.3-1 libxklavier-3.6-1 libgnomekbd-2.22.0-2
gnome-applets-2.22.3-1 gstreamer0.10-good-plugins-0.10.8-3
gnome-media-2.22.0-2 gnome-session-2.22.3-1
smbclient-3.0.30-2 gnome-vfs-2.22.0-4 libwnck-2.22.3-1
gnome-system-monitor-2.22.3-1 gnome-terminal-2.22.3-1
gtk-engines-2.14.3-1 gtksourceview2-2.2.2-1
libgphoto2-2.4.2-1 gvfs-0.2.5-2 hdparm-8.9-1
icon-naming-utils-0.8.7-1 imagemagick-6.4.2.7-1
initscripts-2008.08-1 iproute-2.6.25-1 jre-6u7-1
kernel-headers-2.6.25.8-1 module-init-tools-3.4-1
kernel26-2.6.26.2-1 klibc-1.5-6 klibc-extras-2.4-2
klibc-kbd-1.15.20080312-6 klibc-module-init-tools-3.4-1
klibc-udev-116-4 lib32-zlib-1.2.3.3-2 lib32-freetype2-2.3.7-1
lib32-fontconfig-2.6.0-2 lib32-gcc-libs-4.3.1-3
lib32-glib2-2.16.4-1 lib32-libpng-1.2.29-1
lib32-libcups-1.3.8-1 lib32-libxrandr-1.2.3-1
lib32-libxft-2.1.13-1 lib32-pango-1.20.5-1
lib32-gtk2-2.12.11-2 lib32-libgcrypt-1.4.1-1
lib32-e2fsprogs-1.40.8-1.1 lib32-libsm-1.1.0-1.1
lib32-libtasn1-1.4-1 lib32-pcre-7.7-2 libgnomecups-0.2.3-3
libgnomeprint-2.18.3-3 libgweather-2.22.3-1 libmpeg2-0.5.1-1
libsasl-2.1.22-7 libsm-1.1.0-1 libxfont-1.3.3-1
libxp-1.0.0-2 libxtrap-1.0.0-2 libxxf86vm-1.0.2-1
lirc-utils-0.8.3-1 madwifi-utils-0.9.4.3844-1
madwifi-0.9.4.3844-1 man-pages-3.06-1 ttf-dejavu-2.26-1
giflib-4.1.6-3 mplayer-1.0rc2-5 nautilus-2.22.5.1-1
neon-0.28.2-2 db4.5-4.5.20-1 python-2.5.2-5
openoffice-base-2.4.1-2 pam-1.0.1-2 openssh-5.0p1-2
pciutils-3.0.0-2 perl-5.10.0-4 pm-utils-1.1.2.4-1
preload-0.6.3-2 qt3-3.3.8-8 rarian-0.8.0-2 rsync-3.0.3-1
scrnsaverproto-1.1.0-2 speex-1.2rc1-1 sqlite3-3.6.1-1
swfdec-0.6.8-1 transcode-1.0.6rc1-2 tzdata-2008e-1
vi-7.1.315-1 vlc-0.8.6i-3 wget-1.11.4-1
xf86-input-mouse-1.3.0-1 xf86-video-vesa-1.3.0-6
xfsprogs-2.9.8-1 xorg-twm-1.0.4-1 xorg-xauth-1.0.3-1
xscreensaver-5.07-1 xtrans-1.2.1-1 yelp-2.23.1-2
Total Download Size: 0.00 MB
Total Installed Size: 1322.50 MB
Proceed with installation? [Y/n] y
checking package integrity...
(155/155) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
xulrunner: /usr/include/xulrunner-1.9 exists in filesystem
xulrunner: /usr/lib/xulrunner-1.9 exists in filesystem
xulrunner: /usr/lib/xulrunner-devel-1.9 exists in filesystem
xulrunner: /usr/share/idl/xulrunner-1.9 exists in filesystem
Errors occurred, no packages were upgraded.
Any ideas?
Thanks.
Last edited by RAH (2008-08-15 18:28:42)

pacman -Rd xulrunner and delete these files /usr/include/xulrunner-1.9 /usr/lib/xulrunner-1.9 /usr/lib/xulrunner-devel-1.9 /usr/share/idl/xulrunner-1.9. Re-install xulrunner and your good to go. Alternatively force the upgrade with pacman -Syuf.

[solved]pacman upgrade issue using axel

i changed the default downloading tool to axel, but ervery time before i run pacman -Syu, i need to rm /var/lib/pacman/sync/*.db. If I don't do this, axel can't overwrite the database automatically, which can result in the fail of pacman upgrade.
what should i do so needn't i rm the db files before upgrade.
Last edited by zsrkmyn (2013-09-18 14:16:58)

karol wrote:
Post the XferCommand you're using. Is it https://wiki.archlinux.org/index.php/Im … plications
XferCommand = /usr/bin/axel -n 2 -v -a -o %o %u
Seems to work for me.
oh, it works, thx a lot!
but why i could't succeed when i using "XferCommand = /usr/bin/axel -n 2 -v -a -o `basename %u` %u" before?

[Solved] pacman-color failed to install missing dependencies

Just upgraded my AUR packages and I get this error:
:: Starting AUR upgrade...
:: perl-class-load-xs 0.04-2 -> 0.06-1
AUR Targets (1): perl-class-load-xs
Proceed with installation? [Y/n] y
:: Edit perl-class-load-xs PKGBUILD? [Y/n] n
:: Building perl-class-load-xs package...
==> Making package: perl-class-load-xs 0.06-1 (Sat Nov 3 09:14:38 PDT 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
error: target not found: perl-test-without-module
==> ERROR: 'pacman-color' failed to install missing dependencies.
:: perl-class-load-xs cleaned
Any help appreciated.
Last edited by lagagnon (2012-11-04 03:07:33)

perl-test-without-module is in the AUR.
edit: build the package yourself in makepkg or use an aur helper.
Last edited by SS4 (2012-11-03 16:41:55)

[Solved] Pacman preparation failed

I'm trying a new installation from a USB key and it fails on the Package Selection phase. The error message I get on tty7 is:
Execute(): worker_package_list exit state was 1
More info:
- arch is x86_64
- I'm installing from a USB stick on a laptop that has been running x32 arch for at least a year (it's a core2 cpu)
- I've checked and double-checked the md5sum of the iso and the image on the stick
- I'm using a core iso - no network access
- I select the local core repo when running aif
- I can see all the packages in /repo/core/x86_64/{core,any}
- I've read the aif bash scripts but so far I've been unable to see what the problem might be
I've read all I've found about the subject (there are many threads on this problem), but nothing that describes my exact situation; nothing has helped me. If somebody has any pointers, I'll be grateful!
-- buo
P.S: I've solved this problem; here's the solution in case anyone else encounters something similar. My drive was already partitioned and formatted, so I was telling aif to leave it alone. After I allowed it to reformat the root partition, the problem went away.
Last edited by buo (2012-05-25 15:50:26)

I get an error, "pacman preparation failed. check /dev/tty7 for errors"
did you?

[Solved] Full system upgrade fails because of Nvidia dependencies

Problem:
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-dkms: requires nvidia-utils=346.35
Things I have tried:
$ makepkg -s
==> Making package: nvidia-dkms 346.47-1 (Sun Mar 1 11:42:11 PST 2015)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[sudo] password for digger:
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-dkms: requires nvidia-utils=346.35
==> ERROR: 'pacman' failed to install missing dependencies.
# pacman -R nvidia-utils
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-dkms: requires nvidia-utils=346.35
:: nvidia-libgl: requires nvidia-utils
Some info:
$ uname -a
Linux <hostname> 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux
# dkms status
nvidia, 346.35, 3.18.5-1-ARCH, x86_64: installed
nvidia, 346.35, 3.18.6-1-ARCH, x86_64: installed
$ lspci -k | grep -A 2 -i "VGA"
03:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 640] (rev a1)
Subsystem: eVga.com. Corp. Device 2643
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia
Subsystem: eVga.com. Corp. Device 2643
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
# pacman -Ss nvidia | grep installed
extra/libvdpau 0.9-1 [installed]
extra/nvidia-libgl 346.47-2 [installed: 346.35-2]
extra/nvidia-utils 346.47-2 [installed: 346.35-2]
# cat /etc/mkinitcpio.conf | grep ^HOOKS
HOOKS="base udev autodetect modconf block lvm2 nvidia filesystems keyboard fsck"
# systemctl status dkms
● dkms.service - Dynamic Kernel Modules System
Loaded: loaded (/usr/lib/systemd/system/dkms.service; enabled; vendor preset: disabled)
Active: active (exited) since Sun 2015-03-01 11:40:15 PST; 1h 43min ago
Process: 6196 ExecStart=/usr/lib/systemd/scripts/dkms start (code=exited, status=0/SUCCESS)
Main PID: 6196 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/dkms.service
# pacman -Qm | grep nvidia
nvidia-dkms 346.35-2
nvidia-hook 2.2-3
Let me know if any other information is needed.
Thanks.
Last edited by digger (2015-03-03 03:12:52)

The fix, thanks to Xabre
# pacman -R nvidia-dkms
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-hook: requires nvidia-dkms
# pacman -Rs nvidia-dkms
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia-hook: requires nvidia-dkms
[root@big-kahuna ~]# pacman -Rdd nvidia-dkms
Packages (1) nvidia-dkms-346.35-2
Total Removed Size: 12.29 MiB
:: Do you want to remove these packages? [Y/n] Y
-------- Uninstall Beginning --------
Module: nvidia
Version: 346.35
Kernel: 3.18.5-1-ARCH (x86_64)
Status: Before uninstall, this module version was ACTIVE on this kernel.
nvidia.ko:
- Uninstallation
- Deleting from: /usr/lib/modules/3.18.5-1-ARCH/kernel/drivers/video/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
nvidia-uvm.ko:
- Uninstallation
- Deleting from: /usr/lib/modules/3.18.5-1-ARCH/kernel/drivers/video/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod....
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: nvidia
Version: 346.35
Kernel: 3.18.6-1-ARCH (x86_64)
Status: Before uninstall, this module version was ACTIVE on this kernel.
nvidia.ko:
- Uninstallation
- Deleting from: /usr/lib/modules/3.18.6-1-ARCH/kernel/drivers/video/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
nvidia-uvm.ko:
- Uninstallation
- Deleting from: /usr/lib/modules/3.18.6-1-ARCH/kernel/drivers/video/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.....
DKMS: uninstall completed.
Deleting module version: 346.35
completely from the DKMS tree.
Done.
(1/1) removing nvidia-dkms [######################] 100%
# pacman -Syu ### This ran as expected.
All I wanted was to have the simplest use of the Nvidia proprietary driver. So I followed https://wiki.archlinux.org/index.php/NV … any_kernel
So what I gather from the discussion here is that this (nvidia-dkms) should only be used for custom kernels? And the topic should be a sub topic of https://wiki.archlinux.org/index.php/NV … tom_kernel? Is that right?
Thanks for you help.
Last edited by digger (2015-03-03 03:11:58)

[Solved] Upgrade fails because of net-tools

It was almost a week since I last did a "pacman -Syu" on my system. Before that, I had read about depreciation of net-tools and have already modified my rc.conf to use the newer simple network setup. Everything was working fine. Even upgradation of the system (pacman -Syu) also worked fine last week.
I was out of town for a few days. So, when I came back on Sunday, I tried updating the system. Pacman found updates and downloaded them. But it failed when actually upgrading the packages. It gives the following error:
[vinay@arch ~]$ sudo pacman -Syu
Password:
:: Synchronizing package databases...
core 37.0K 44.9K/s 00:00:01 [######################] 100%
extra 465.7K 39.1K/s 00:00:12 [######################] 100%
community 441.9K 123.2K/s 00:00:04 [######################] 100%
multilib is up to date
archlinuxfr 24.7K 74.6K/s 00:00:00 [######################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (10): gdk-pixbuf2-2.23.4-1 gtk-update-icon-cache-2.24.5-2
gtk2-2.24.5-2 libmodplug-0.8.8.3-1 libxml++-2.34.1-1
libofx-0.9.4-1 net-tools-1.60-18 soprano-2.6.0-6
strigi-0.7.5-2 xdg-utils-1.1.0rc1-3
Total Download Size: 7.85 MB
Total Installed Size: 47.46 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
gtk-update-icon-ca... 10.9K 22.1K/s 00:00:00 [######################] 100%
gtk2-2.24.5-2-x86_64 4.9M 60.9K/s 00:01:23 [######################] 100%
libmodplug-0.8.8.3... 145.8K 53.5K/s 00:00:03 [######################] 100%
libofx-0.9.4-1-x86_64 223.9K 60.2K/s 00:00:04 [######################] 100%
soprano-2.6.0-6-x86_64 2.0M 68.2K/s 00:00:30 [######################] 100%
strigi-0.7.5-2-x86_64 504.2K 75.7K/s 00:00:07 [######################] 100%
xdg-utils-1.1.0rc1... 46.3K 46.1K/s 00:00:01 [######################] 100%
(10/10) checking package integrity [######################] 100%
(10/10) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
net-tools: /bin/hostname exists in filesystem
net-tools: /usr/share/man/man1/hostname.1.gz exists in filesystem
Errors occurred, no packages were upgraded.
As you can see it complains about /bin/hostname file existing in the filesystem and that causing problem for net-tools package. I'm not sure how or why this happened. The /bin/hostname is supposed to be available on the filesystem, right?
Since net-tools was depreciated in favour of netcfg, I tried removing net-tools. When I try that, it offers to remove netcfg package as well!
[vinay@arch ~]$ sudo pacman -Rcsu net-tools
Password:
checking dependencies...
Remove (2): netcfg-2.5.5-1 net-tools-1.60-16
Total Removed Size: 0.61 MB
Do you want to remove these packages? [Y/n] n
What I did was to upgrade each package manually (excluding net-tools package). But this is cumbersome and tedious. I did a search on the forum and on internet and did not find other people with the same problem. So, is something wrong/corrupt on my arch installation?
If so, how do I fix it?
Thanks in advance,
Vinay V
Last edited by vinayv (2011-06-22 01:31:49)

Thanks for the reply. I should have searched for a generic "exists in filesystem" rather than net-tools error specific "/bin/hostname exists in filesystem". I thought this was because of the recent move to netcfg from net-tools. Maybe I'm mistaken.
Anyway, thanks for pointing out that stikie to me. Let me try the suggestions in that post

[SOLVED] Pacman upgrade failed because of gcc-libs

Similar Messages

Maybe you are looking for