You are not logged in.
I'm getting the following error when trying to pacman -Syu. I've shown all the output so my sources can be seen as well:
[root@salamander trey]# pacman -Syu
:: Synchronizing package databases...
gnome27 [################] 100% 4K 2.3K/s 00:00:01
gnome25 [################] 100% 1K 1.8K/s 00:00:00
incoming [################] 100% 3K 1.4K/s 00:00:02
current [################] 100% 39K 31.5K/s 00:00:01
extra [################] 100% 137K 55.4K/s 00:00:02
unstable [################] 100% 1K 5.1K/s 00:00:00
contrasutra [################] 100% 0K 0.1K/s 00:00:03
staging [################] 100% 15K 23.8K/s 00:00:00
Targets: arts-1.2.3-1 fontconfig-2.2.90-3 iputils-021109-2 kdelibs-3.2.3-1
kdemultimedia-3.2.3-1 kdeaddons-3.2.3-1 kdebase-3.2.3-1
kdeadmin-3.2.3-1 kdeartwork-3.2.3-1 kdebindings-3.2.3-1 kdeedu-3.2.3-1
kdegames-3.2.3-1 kdegraphics-3.2.3-1 kdenetwork-3.2.3-1 kdepim-3.2.3-1
kdesdk-3.2.3-1 kdetoys-3.2.3-1 kdeutils-3.2.3-1 lcms-1.13-1 m4-1.4.1-1
sylpheed-claws-0.9.11-1 vim-6.3-2 xsane-0.94-3
Proceed with upgrade? [Y/n]
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
/usr/lib/perl5/5.8.4/i686-linux-thread-multi/perllocal.pod: exists in filesyst em
Haven't seen pacman kick an error out like this before and I'm looking for some next steps.
Thanks.
Offline
Step 1. Search and read the forums for similar error solutions before posting.
Step 2. If nobody have done it so far file a bug report http://bugs.archlinux.org. (Hint: use pacman -Qo path_to_the_file_in_question to check what package owns this file - do this before step 3).
Step 3. Force an upgrade by adding f option to pacman options.
Offline
find the package this error is refering to
and jsut do pacman -Sf PKG
Offline
Force it is, then. I had exhausted other methods and did not see a similar posting for this (should have mentioned that in my original post). Just thought it might be something that I was overlooking.
Thanks for the feedback.
Offline
you should have no perllocl.pods on your system. i strongly recommend finding out which package you installed before had one and which you installed had one aas well so you can report both to the bug tracker (seprate bugs). these are useless but common files in perl compatable packages.
AKA uknowme
I am not your friend
Offline