You are not logged in.
Pages: 1
Tried to pacman -S kde and it needed to upgrade pacman first. so when it tried to upgrade pacman lots of files existed so nothing was downloaded. then I tried to pacman -Syu with the following:
pacman: error while loading shared libraries: libarchive.so.1 : cannot open shared object file: no such file or directory.
tried rm libarchive.so.1 with the following: rm cannot remove libarchive.so.1 no such file exists.
tried pacman -Qo libarchive.so.1 and got
pacman: error while loading shared libraries: libarchive.so.1 : cannot open shared object file: no such file or directory.
So if I cannot remove it and cannot Syu what do I do?
AMD 64 and just finished loading Archlinux duke and trying to get kde on it.
Offline
Try "pacman.static -S libarchive".
Offline
Tried pacman.static -S libarchive with the following results
libarchive-2.4.12-1 : local version is up to date. upgrade anyway?
it resolved dependencies and interdependencies, checked package integrity, done. error: missing package filelist /var/cache/packman/pkg/libarchive-2.4.12-1-i686.pkg.tar.gz, generating one.
cleaned up and checked for file conflicts, upgraded libarchive.
so then I tried pacman -Syu to update all the files before going on and I got
pacman: error while loading shared libraries: libarchive.so.1: cannot open shared object file: no such file or directory.
Now did pacman.static -S libarchive work and are there still somethings missing or is the libarchive still messed up??
Offline
Hmm, you have no idea what this errors means, right?
Your pacman is built against the libarchive.so.1 shared lib. You can also see it with :
ldd /usr/bin/pacman | grep libarchive
If this file isn't available on your system, this binary of pacman simply can't work. So you have to use pacman.static until the problem is resolved.
This file isn't available anymore because you upgraded libarchive. This new libarchive version now provides /usr/lib/libarchive.so.2
So either you downgrade libarchive, or you upgrade pacman, but reinstalling libarchive won't solve anything.
Of course the preferred solution is to upgrade pacman, and eventually get your whole system up to date.
However, I am not sure how you managed to upgrade libarchive only, without pacman. Your post wasn't very clear. It would help to have some more details about it. Like the pacman output of the upgrade that went wrong. Or maybe the relevant part from your pacman.log
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
tried ldd /usr/bin/pacman | grep libarchive and got
libarchive.so.1 =not found
checked /usr/lib/ and found libarchive.a
libarchive.1a
libarchive.so
libarchive.so.2
libarchive.so.2.4.12
I started out loading Archlinux duke version 2007-05 got logged in and went to download kde. Then it said there was a new version of pacman did I want to upgrade it before doing anything else. I hit yes and that was when lots of files existed so nothing was downloaded.
So I take it I need to downgrade to libarchive.so.1, How do I do that ??
Offline
So I take it I need to downgrade to libarchive.so.1, How do I do that ??
Of course the preferred solution is to upgrade pacman, and eventually get your whole system up to date.
pacman.static -S pacman ...
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
tried pacman.static -S pacman and got the following
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
gcc-libs: /usr/lib/libgcc_s.so exists in filessystem
gcc-libs: /usr/lib/libgcc_s.so.1 exists in filesystem
gcc-libs: /usr/lib/libmudflap.a exists in filesystem
gcc-libs: /usr/lib/libmudflap.so exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.O.O.O exists in filesystem
gcc-libs: /usr/lib/libmudflapth.a exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.O exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.O.O.O exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so exists in filesystem
gcc-libs: /usr/lib/libobjc.a exists in filesystem
gcc-libs: /usr/lib/libobjc.so exists in filesystem
gcc-libs: /usr/lib/libssp.a exists in filesystem
gcc-libs: /usr/lib/libssp.so exists in filesystem
gcc-libs: /usr/lib/libssp.so.O exists in filesystem
gcc-libs: /usr/lib/libssp.so.O.O.O exists in filesystem
gcc-libs: /usr/lib/libssp_nonshared.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.so exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6 exists in filesystem
gcc-libs: /usr/lib/libsupc++.a exists in filesystem
gcc-libs: /usr/share/locale/de/LC_MESSAGES/libstdc++.mo exists in filesystem
gcc-libs: /usr/share/locale/fr/LC_MESSAGEA/libstdc++.mo exists in filesystem
so is this part of the gcc-libs that was split and needs a fix or can I do something?? or do I need to remove gcc-libs directory and start over??
Offline
assuming your going to upgrade the whole system before a reboot,
i think it should be safe to just force the upgrade
pacman -Sf pacman...
Offline
tried pacman -Sf pacman and got
pacman: error while loading shared libraries: libarchive.so.1 :cannot open shared object file :no such file or directory.
So how do I delete all of pacman and start over since nothing is working, or do I have to wipe and reload Archlinux??
Offline
I think he meant try pacman.static -Sf pacman.
Offline
tried pacman -Sf pacman and got
pacman: error while loading shared libraries: libarchive.so.1 :cannot open shared object file :no such file or directory.
If this file isn't available on your system, this binary of pacman simply can't work. So you have to use pacman.static until the problem is resolved.
A bit of thinking... you should rather try 'pacman.static -Sf pacman'
A bit of explanation: binaries in linux are either "dynamically linked" (the code that is actually in some library is *not* included in the binary itself, the binary just contains a link to the library file. Hence if that library is not present, the binary *will not* run (as shining already wrote)) or "statically linked" (*everything* needed to run the binary is included in it, so it should theoretically run on any linux system).
EDIT: likpok got me beaten...
Last edited by bender02 (2008-03-17 01:30:28)
Offline
pacman.static -Sf pacman worked for pacman and now I am doing a pacman -Syu this should upgrade all the files and I guess theoretically upgrade the files so they are now dynamically linked? Now does pacman.static work for any files that have this problem with an out of date file needed when a newer one is in the directory? Thanks for the lesson.
Offline
Pages: 1