Arch Linux

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Failed upgrade

Simply put, pacman won't update the system. I don't know how to retrieve the error list either. I've looked in /var/log and there's nothing there. This is the third install I've attempted because various errors. I don't know how to make this thing work. Help please!

Ruckus

Member

Registered: 2007-02-17

Posts: 204

Re: Failed upgrade

Simply put, pacman won't update the system. I don't know how to retrieve the error list either. I've looked in /var/log and there's nothing there. This is the third install I've attempted because various errors. I don't know how to make this thing work. Help please!

Paste the actual output of pacman.

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

I don't know how, sorry. How can you get the output from one computer with arch to another with windows?

RaisedFist

Member

From: Romania

Registered: 2007-01-30

Posts: 556

Website

Re: Failed upgrade

Is it too much to write it yourself?

---

last.fm

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

Well it's the update straight after the install. The start of it goes off the screen...

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

It must be this file conflicts that was mentioned in the sticky. What has happened in the last 8 months with pacman? I remember pacman would overwrite older versions and there would never have been a problem...

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: Failed upgrade

does it have to do with the klibc?

Try reading the front page, the problem is that pacman will not overwrite a file it didn't install. The klibc error is due to some symlinking that was done in the post_install script. Pacman didn't install the symlinks, so when it comes time to overwrite them pacman says 'wait a min, I can't do that because that is not my default behavior'. So the upgrade fails.

To solve it is simple, don't upgrade the package causing the conflict. Instead upgrade that package seperately and follow the directions posted on this site on how to solve the klibc error.

If it's not klibc packagecausing the error then you need to provide us with atleast one line of the error or something. I think you can manually type one significant line from the output.

Mr.Elendig

#archlinux@freenode channel op

From: The intertubes

Registered: 2004-11-07

Posts: 4,092

Re: Failed upgrade

You can use shift-PageUp to scroll up the buffer.

---

Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

Thanks guys. Yes I believe it was klibc, apologies for my ignorance.

sand_man

Member

From: Australia

Registered: 2008-06-10

Posts: 2,164

Re: Failed upgrade

You may have to force the kernel upgrade.
Don't force the whole system upgrade though.

---

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

I was attempting the following as per instructions.

Due to a limitation in pacman's conflict checking and symbolic link resolution, the upgrade to klibc-1.5.14-1 requires manual removal of a symbolic link befole updating. Please run the command "rm /usr/lib/klibc/include/asm" as root to remove the symbolic link that will otherwise cause a few hundred false file conflicts.

I still get this after performing "pacman -Sy klibc"

error: could not prepare transaction
error: failed to commit transaction (conflicting files)
klibc: /usr/lib/klibc/bin/mknod exists in filesystem
Errors occured, no packages were upgraded.

So can I just do "rm /usr/lib/klibc/bin/mknod" to remove this then update klibc?

peart

Member

From: Kanuckistan

Registered: 2003-07-28

Posts: 510

Re: Failed upgrade

... Please run the command "rm /usr/lib/klibc/include/asm" as root ...

BR

Member

From: Australia

Registered: 2008-07-08

Posts: 20

Re: Failed upgrade

I did that before running "pacman -Sy klibc". It doesn't matter I ended up forcing it anyway, if that's ok.

Last edited by BR (2009-02-04 23:50:25)

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: Failed upgrade

the proper way is to never force upgrade any package unless you are sure of what it is overwriting. an example would be a file you put there.

The correct way would be to rm the symlinks then install the new klibc.

But,

using pacman -Syf klibc would have solved the issue with no ill effects, this time. Don't become dependent upon the f switch and don't ever use it like this

pacman -Syuf

It's just plain dumb

Last edited by jacko (2009-02-05 01:09:59)