You are not logged in.
I just removed the package pidgin-libnotify with the command pacman -Rscn pidgin-libnotify and it also removed the package expat, I didnt know what it was until it was to late.
Remove (3): pidgin-libnotify-0.14-4 perl-xml-parser-2.40-2 expat-2.0.1-6
Total Removed Size: 1.44 MB
Do you want to remove these packages? [Y/n]
(1/3) removing pidgin-libnotify [######################] 100%
(2/3) removing perl-xml-parser [######################] 100%
(3/3) removing expat [######################] 100%Why did it remove expat? It totaly broke my system:
$ sudo pacman -Syu
pacman: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directoryI did solved it by manually copying the files to its right place from the tar.gz file. But I dont understand why it removed a package from core.
Last edited by Hund (2011-03-23 19:02:19)
Offline
libarchive has expat dependency. I wonder why was removed...
Last edited by wonder (2011-03-23 19:04:45)
Give what you have. To someone, it may be better than you dare to think.
Offline
`pacman -Qi libarchive pacman` output, please.
Offline
Name : pacman
Version : 3.4.3-1
URL : http://www.archlinux.org/pacman/
Licenses : GPL
Groups : base
error: could not open file /var/lib/pacman/local/pacman-3.4.3-1/depends: No such file or directory
Provides : None
Depends On : None
error: could not open file /var/lib/pacman/local/pacman-3.4.3-1/depends: No such file or directory
Optional Deps : None
Required By : None
error: could not open file /var/lib/pacman/local/pacman-3.4.3-1/depends: No such file or directory
Conflicts With : None
Replaces : None
Installed Size : 2456.00 K
Packager : Dan McGee <dan@archlinux.org>
Architecture : x86_64
Build Date : Sat 22 Jan 2011 09:52:28 PM CET
Install Date : Sun 20 Mar 2011 01:41:52 AM CET
Install Reason : Explicitly installed
Install Script : Yes
Description : A library-based package manager with dependency supportOffline
So what is going on here? One, I don't see any libarchive output at all (is it installed). Two, you clearly upgraded to pacman 3.5.0 from testing, upgraded your local database, and then downgraded back to 3.4.3 on March 20th, which is why you see all those "error: could not open file /var/lib/pacman/local/pacman-3.4.3-1/depends: No such file or directory" errors you seem fine with ignoring.
When you did the -Rcs operation with an upgraded local DB, you hosed your system because the old version of pacman wasn't able to actually read the dependency information. Note in your output above how pacman lists no depends at all- clearly not the case.
A lesson to all- you cannot downgrade from 3.5.X once you have upgraded. And including said details in your first post would have been quite helpful.
Offline