You are not logged in.
- Topics: Active | Unanswered
#1 2012-08-13 18:55:49
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Upgrade glibc problem((Solved)
The procedure outlined for upgrade is shown below and the result is very confusing with this CFcard upgrade. Other upgrades were as expected and successful on CF cards in raid config.
sh-4.2# pacman -Syu --ignore glibc
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: glibc: ignoring package upgrade (2.15-12 => 2.16.0-2)
:: Replace grub2-bios with core/grub-bios? [Y/n]
:: Replace grub2-common with core/grub-common? [Y/n]
resolving dependencies...
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "binutils"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "binutils"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "binutils"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
warning: ignoring package glibc-2.16.0-2
warning: cannot resolve "glibc>=2.16", a dependency of "gcc-libs"
:: The following packages cannot be upgraded due to unresolvable dependencies:
ati-dri binutils boost-libs cryptsetup dbus dbus-core device-mapper
exiv2 ffmpeg firefox gcc gcc-libs gegl git glew glib2 glibmm
gnutls grep grub-bios grub-common gtk2 gtk3 icu initscripts
intel-dri kdebase-runtime kdelibs kdenlive libcups libegl libgl
libimobiledevice libmp4v2 libpulse libwebkit linux live-media lvm2
mesa mkinitcpio mlt mplayer opencv oss pcre pkg-config projectm
qt soprano strigi svga-dri syslog-ng systemd systemd-tools taglib
thunderbird upower vlc wpa_supplicant xf86-input-evdev
xf86-video-intel xine-lib xorg-server
Do you want to skip the above packages for this upgrade? [y/N] y
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: systemd: requires libsystemd=185
sh-4.2# When I ignore systemd as well as glibc, the same result obtains.
Please advise what to do next........
Last edited by lilsirecho (2012-08-14 15:36:52)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#2 2012-08-13 19:07:17
- joseperezc
- Member
- Registered: 2011-03-02
- Posts: 80
Re: Upgrade glibc problem((Solved)
Hi there, have you tried?:
https://wiki.archlinux.org/index.php/De … iki:usrlib
in brief:
1._ pacman -Sd binutils gcc gcc-libs
2._ pacman -Su
3._ Enjoy!
Hope to be helpfull
Offline
#3 2012-08-13 19:37:03
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
The following occured with the recommended procedure:
sh-4.2# pacman -Sd binutils gcc gcc-libs
resolving dependencies...
looking for inter-conflicts...
Targets (3): binutils-2.22-9 gcc-4.7.1-5 gcc-libs-4.7.1-5
Total Download Size: 22.49 MiB
Total Installed Size: 93.96 MiB
Net Upgrade Size: -0.02 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from core...
binutils-2.22-9-x86_64 3.4 MiB 166K/s 00:21 [######################] 100%
gcc-libs-4.7.1-5-x86_64 766.5 KiB 169K/s 00:05 [######################] 100%
error: failed retrieving file 'gcc-4.7.1-5-x86_64.pkg.tar.xz' from mirrors.gigenet.com : transfer closed with 7136280 bytes remaining to read
warning: failed to retrieve some files from core
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
sh-4.2# The use of pacman -Su is recommended after the packages other than glibc have been installed. Those packages were never installed as shown in the first post.
Therefore, since the binutils gcc and gcc-libs also failed, pacman -Su is not valid.
The installed Kernel is 3.4.4-2 and the latest kernel is much later.
Pacman has been upgraded.
What to do next?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#4 2012-08-13 20:54:42
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
performed step 1.
Received a failed download of gcc.
Performed step 1 again and stopped the download with controlC because gcc was not includeed.
Repeated the pacman -Sd binutils gcc and gcc-libs command.
This time gcc was downloaded along with the others.
I now decided I needed to run ....pacman -Syu --ignore glibc ....because the packages needed to load )158) were not yet loaded.
They subsequently were downloaded and successfully installed.
Then I ran ....pacman -Su
This failed due to a conflict in curl....glibc
EDIT: Then I tried
sh-4.2# pacman -Syu
pacman: /lib/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib/libcurl.so.4)
sh-4.2# I may try the obvious ...pacman -Su --ignore ,curl.
Or is some other procedure better?
Last edited by lilsirecho (2012-08-13 21:05:21)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#5 2012-08-13 21:08:19
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
The system is up and running in the latest kernel but cannot upgrade thru pacman which reports the glibc/curl problem.
I hope this ends up with a viable method of handling glibc upgrade.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#6 2012-08-13 21:11:42
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Upgrade glibc problem((Solved)
Please stop bumping your thread https://wiki.archlinux.org/index.php/Fo … te#Bumping
I suspect that the reason no-one else is responding is that this issue is already extensively documented.
Offline
#7 2012-08-13 22:19:38
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
Jasonwryan:
The documentation utilized by this user was the instructions given in the archnews. That failed. The procedure outlined in this post provided some relief but now pacman is stuck with the failure of pacman -Su.
I have attempted to follow the official news item which was inadequate. Now I need a corrective action which is reliable and repeatable.
With the failure of the archnews procedure I am losing confidence in pacman and do not know where to go to fix it.
I had no trouble with one arch setup but this one is failing the same procedure blessed by the system arch news.
Your response does not indicate a desire to help since not all documents on the subject are clear and concise.
Perhaps I am too old to comprehend?
My pacman is stuck....where is it documented to unstick my pacman? This isn't the same as not upgrading due to glibc but may be a subset of the curl/glibc problem but how do I know this?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#8 2012-08-13 23:37:48
- ngoonee
- Forum Fellow
- From: Between Thailand and Singapore
- Registered: 2009-03-17
- Posts: 7,362
Re: Upgrade glibc problem((Solved)
Your response does not indicate a desire to help since not all documents on the subject are clear and concise.
Your response does not indicate:-
a) what documents you're following (only the news announcement)
b) what troubleshooting you've done based on changes to your system (that only you know about)
c) superseding a) and b) - that you've actually searched for this error, its been covered in the forums before
This is Arch. Help yourself. As a long-time user, you should already know that 
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
#9 2012-08-14 00:58:43
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
ngoonee:
What reference document has information on what to do when pacman cannot respond to any command...it is stuck on:
sh-4.2# pacman -S pacman
pacman: /lib/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib/libcurl.so.4)
sh-4.2# Please indicate where this problem is documented...that is, pacman is STUCK on the reply given above.
Pacman does not repond to any command to enable fixing the glibc problem.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#10 2012-08-14 01:04:03
- FlyingHappy
- Member
- From: Cincinnati, OH
- Registered: 2011-04-18
- Posts: 192
Re: Upgrade glibc problem((Solved)
There have been multiple forum posts about this issue in the last week with the exact same issue.
Offline
#11 2012-08-14 01:34:01
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
Name one which has pacman stuck.
EDIT:
sh-4.2# pacman -Sc
pacman: /lib/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib/libcurl.so.4)
sh-4.2# sh-4.2# pacman _S vlc
pacman: /lib/libc.so.6: version `GLIBC_2.16' not found (required by /usr/lib/libcurl.so.4)
sh-4.2# Last edited by lilsirecho (2012-08-14 01:38:12)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
#12 2012-08-14 01:44:16
- 2ManyDogs
- Forum Fellow
- Registered: 2012-01-15
- Posts: 4,648
Re: Upgrade glibc problem((Solved)
I don't know why I'm doing this.
https://bbs.archlinux.org/viewtopic.php?id=146742
https://bbs.archlinux.org/viewtopic.php?id=146308
Offline
#13 2012-08-14 15:28:39
- lilsirecho
- Veteran
- Registered: 2003-10-24
- Posts: 5,000
Re: Upgrade glibc problem((Solved)
Perhaps I should clarify my approach to the solution of the glibc caused pacman failure.
In researching the fixes for the loss of pacman functionality, I read that a certain procedure outlined in a forum posting did not work for the user.
Thus, I assumed it wasn't viable.
After being advised to revisit the Forum post, I deduced that the data therein, altho outlined, was in need of interpretation .
Subsequent to performing the steps therein in proper arch format, I was able to re-establish pacman.
Thus, the references to forum fixes made by those answering my posts were indeed read and rejected because the fixes were reported as not working!
Much of the confusion would be eliminated if posters with detailed commands would utilize code to outline the postings. The purpose of the use of code is to make clear to others the steps in proper format which indeed is necessary to provide communication of the underlying reasoning behind the procedure.
For my mistake of assuming that the forum fix did not work because the user said so, I apologize. With code the user would likely have solved his pacman problem.
Last edited by lilsirecho (2012-08-14 15:31:45)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline