Welcome to my blog !

The famous author Arthur Koestler once said that “Creativity is a type of learning process where the teacher and pupil are located in the same individual.” My main purpose for this blog is to depict the little tricks I've learned over time in Computers and my increasing adaptation towards Open Source Software.
More about me... here

November 06 2008

Symlink errors

Tagged Under :

Recently I had to reinstall my Windows box so I decided to reinstall my Archlinux box as well. So I started taking backups which I must say that backing up data is starting to hurt the wallet since I have about 20-35 GB of data I need to save. So continued on and backed up everything and reinstalled Windows first since I wanted a dual boot configuration on this system. My system has a IDE and SATA hard disk which tends to cause problems when I configure it for dual booting. Usually I end up with having to use the BIOS boot options to go to either Linux or Windows. Well with the help of a friend on IRC (Thanks Qwerty) I created a /boot partition on the IDE drive which Windows was installed and then the rest of the Linux partitions on the SATA drive and then installed the GRUB to sda instead of the boot partition like I was doing previously and now I have a perfectly configured Dual boot.

Now if you are wondering what does this have to do with Symlink errors, hold your horses I’m getting there. After continuing with the install I did a pacman -Syu and made sure I upgraded all base packages but after downloading the updates it just wouldn’t get upgraded but rather gave me the following error.


checking package integrity...
checking for file conflicts...
error: could not prepare transaction
klibc: /usr/lib/klibc/include/asm/Kbuild exists in filesystem
klibc: /usr/lib/klibc/include/asm/a.out-core.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/a.out.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/acpi.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/agp.h exists in filesystem
............  (Couple 100 of errors deleted) ................
klibc: /usr/lib/klibc/include/asm/xor_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xor_64.h exists in filesystem
Errors occurred, no packages were upgraded.

Checked around and found that without performing the following command would result in the above error.




rm /usr/lib/klibc/include/asm

Running this command fixed the problem and I was able to upgrade the packages with no problem. The reason for this is shown below as quoted per www.archlinux.com

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 before 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.

Source

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • StumbleUpon
  • Slashdot
  • Google
  • E-mail this story to a friend!
  • Print this article!
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...


Post a comment