You are not logged in.

#1 2009-11-13 15:14:04

wunki
Member
Registered: 2009-02-17
Posts: 10

[SOLVED][glibc] A lot of conflicts. Already existing files.

I'm trying to update my system with a ''pacman -Syu''. But I keep getting a conflict.

Targets (12): kernel-headers-2.6.31.5-1  glibc-2.11-1  binutils-2.20-2  bzip2-1.0.5-5  dhcpcd-5.1.3-1  fakeroot-1.14.3-1  gcc-4.4.2-3  gcc-libs-4.4.2-3  hal-0.5.13-3  kernel26-2.6.31.6-1  libcups-1.4.2-1  sqlite3-3.6.20-1
error: failed to commit transaction (conflicting files)
glibc: /lib/ld-2.11.so exists in filesystem
glibc: /lib/libBrokenLocale-2.11.so exists in filesystem
glibc: /lib/libanl-2.11.so exists in filesystem
glibc: /lib/libc-2.11.so exists in filesystem
glibc: /lib/libcidn-2.11.so exists in filesystem
glibc: /lib/libcrypt-2.11.so exists in filesystem
glibc: /lib/libdl-2.11.so exists in filesystem
glibc: /lib/libm-2.11.so exists in filesystem
glibc: /lib/libnsl-2.11.so exists in filesystem
glibc: /lib/libnss_compat-2.11.so exists in filesystem
glibc: /lib/libnss_dns-2.11.so exists in filesystem
glibc: /lib/libnss_files-2.11.so exists in filesystem
glibc: /lib/libnss_hesiod-2.11.so exists in filesystem
glibc: /lib/libnss_nis-2.11.so exists in filesystem
glibc: /lib/libnss_nisplus-2.11.so exists in filesystem
glibc: /lib/libpthread-2.11.so exists in filesystem
glibc: /lib/libresolv-2.11.so exists in filesystem
glibc: /lib/librt-2.11.so exists in filesystem
glibc: /lib/libutil-2.11.so exists in filesystem
glibc: /lib64/ld-2.11.so exists in filesystem
glibc: /usr/include/bits/setjmp2.h exists in filesystem
glibc: /usr/share/i18n/locales/dv_MV exists in filesystem
glibc: /usr/share/i18n/locales/my_MM exists in filesystem
glibc: /usr/share/i18n/locales/ps_AF exists in filesystem
glibc: /usr/share/i18n/locales/ur_IN exists in filesystem
bzip2: /usr/bin/bzdiff exists in filesystem
bzip2: /usr/bin/bzgrep exists in filesystem
bzip2: /usr/bin/bzmore exists in filesystem
Errors occurred, no packages were upgraded.

Should I forcefully remove the old glibc to update? How can I update to the newest kernel?

Thanks in advance.

Last edited by wunki (2009-11-15 15:31:40)

Offline

#2 2009-11-13 15:17:08

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

post the output of

pacman -Qo /lib/ld-2.11.so
pacman -Qo /usr/bin/bzdiff

Last edited by wonder (2009-11-13 15:17:37)


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2009-11-13 15:17:29

wsduvall
Member
From: Blacksburg
Registered: 2009-02-05
Posts: 54
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

Whenever I get these issues I just do sudo pacman -Syuf and that forces the update. Not sure how safe it is in this case...


My 5 node 9 CPU cluster: www.amenrecluster.com
OS: Arch Linux
Machines:Fujitsu T4210 and IBM eServer xSeries 335

Offline

#4 2009-11-13 15:21:28

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

wsduvall wrote:

Whenever I get these issues I just do sudo pacman -Syuf and that forces the update. Not sure how safe it is in this case...

never associate -f with -u


Give what you have. To someone, it may be better than you dare to think.

Offline

#5 2009-11-13 15:31:13

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,672
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

wunki wrote:

Should I forcefully remove the old glibc to update?

Well.....  no.  You should never remove glibc from your system.

Offline

#6 2009-11-13 15:58:15

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

wonder wrote:

post the output of

pacman -Qo /lib/ld-2.11.so
pacman -Qo /usr/bin/bzdiff

This is my output:

/lib/ld-2.11.so is owned by glibc 2.11-1
/usr/bin/bzdiff is owned by bzip2 1.0.5-5

Offline

#7 2009-11-13 16:00:17

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,672
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

That makes no sense!   Why would you be updating to packages that are already installed?

Offline

#8 2009-11-13 16:04:51

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

Allan wrote:

That makes no sense!   Why would you be updating to packages that are already installed?

Ha, you tell me smile

Maybe an update went wrong the first time or something...

Offline

#9 2009-11-13 16:09:39

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

i think is safe to do pacman -Sf glibc bzip2. i don't know why is conflicting.


Give what you have. To someone, it may be better than you dare to think.

Offline

#10 2009-11-13 16:17:16

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

wonder wrote:

i think is safe to do pacman -Sf glibc bzip2. i don't know why is conflicting.

Auch, that just killed my system. System hanged, and now at reboot I'm getting a:

kinit: /sbin/init: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: kinit Not tainted 2.6.31-ARCH #1
Call Trace:
...

Offline

#11 2009-11-13 16:30:29

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

oh i'm sorry. get the installation cd, mount the partition and use pacman -Sf glibc bzip -r /path/to/directory and then pacman -Syu -r  /path/to/directory


Give what you have. To someone, it may be better than you dare to think.

Offline

#12 2009-11-13 16:36:07

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,672
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

I obviously do not need to tell you this, but something is seriously screwed with your system

> pacman -Qo /sbin/init
/sbin/init is owned by sysvinit 2.86-5

Offline

#13 2009-11-13 17:01:52

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

wonder wrote:

oh i'm sorry.

No, problem. Your also only trying to help.

get the installation cd, mount the partition and use pacman -Sf glibc bzip -r /path/to/directory and then pacman -Syu -r  /path/to/directory

I'm back in my system, but I think that everything is still broken.. I'm now getting:

pacman: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory

Is there a way to re-install the base packages?

Offline

#14 2009-11-13 17:03:56

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

i had a typo in there. reinstall bzip2

Last edited by wonder (2009-11-13 17:04:11)


Give what you have. To someone, it may be better than you dare to think.

Offline

#15 2009-11-13 17:10:56

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

Yeah, just did that.

Everything seems to be working now. Even could do a ''pacman -Syu'' and upgraded to the newest kernel.

Thanks for your help.

Offline

#16 2009-11-13 17:28:46

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

Some more strange stuff. When I do a 'pacman -Syu' I keep getting the following:

Targets (5): binutils-2.20-2  fakeroot-1.14.3-1  gcc-4.4.2-3  gcc-libs-4.4.2-3  kernel26-2.6.31.6-1

I select to proceed, everything seems to be installed just fine. But than, after a reboot and a 'pacman -Syu' I get the same packages that should be updated.

It seems like my system is totally corrupted. Should I be going for a reinstall of Arch?

Offline

#17 2009-11-15 15:31:18

wunki
Member
Registered: 2009-02-17
Posts: 10

Re: [SOLVED][glibc] A lot of conflicts. Already existing files.

Just for the logs.

I was able to stop the upgrading of the same packages by removing the older version of the packages from "/var/lib/pacman/local".

Offline

Board footer

Powered by FluxBB