[Solved]Upgrade pacman 4.1 - no usable package repositories configured

Hi, i am another guy who fail with upgrade pacman 4.1
I has pacman 4.0.3-7 and for some dependancy (like yaourt), i need pacman 4.1
He wasn't in system update, so i download it from git : git clone git://projects.archlinux.org/pacman.git pacman
sh ./autogen.sh
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-doc
make -j8
sudo make install
And now, i got this error
sudo pacman -Syu
error: no usable package repositories configured.
I backup my /etc/pacman.conf and use the new one like this topic : https://bbs.archlinux.org/viewtopic.php … 7#p1254497
I check the version :
Pacman v4.1.0 - libalpm v8.0.0
I try to upgrade my DB
sudo /usr/local/bin/pacman-db-upgrade
==> ERROR: /usr/local/var/lib/pacman/ is not a pacman database directory.
The only solution i found right now is reinstalling arch linux o.0
Thanks for you help.
Last edited by mathben (2013-04-06 22:56:39)

mathben wrote:
I has pacman 4.0.3-7 and for some dependancy (like yaourt), i need pacman 4.1
He wasn't in system update, so i download it from git : git clone git://projects.archlinux.org/pacman.git pacman
sh ./autogen.sh
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-doc
make -j8
sudo make install
Why would you do that? Why would you not use pacman to upgrade/install pacman, or any other package for that matter?
Honestly, this was such a bad idea that I'm finding it difficult to keep myself from berating you with inappropriate language (some of which I instinctively blurted out when I read your post).
mathben wrote:
I try to upgrade my DB
sudo /usr/local/bin/pacman-db-upgrade
==> ERROR: /usr/local/var/lib/pacman/ is not a pacman database directory.
pacman-db-upgrade is a transition tool to convert pacman 3.x databases to pacman 4.x databases. Is there some guide that told you to use that to update the database?
I pride myself on trying to be helpful on the forum, but you do not seem to have any idea of how package management works on Arch Linux. This is all covered in the wiki and on the forum. I really do not mean to be rude, but I believe that you would be better off with something else as you seem to just be naively trying random shit.
If you really want to clean up the mess that you've made, uninstall the manually installed pacman, remove whatever AUR apps you have installed that prevent you from upgrading via pacman, then rebuild and re-install those apps after the upgrade.
I also suspect that you are using Archbang or some other distro given that you seem to be new to the distro yet already have yaourt installed. If this is the case then you should direct yourself to their forum. This forum is for Arch Linux.

Similar Messages

Error: no usable package repositories configured.

I get this error when trying to pacman -Syu the system.
So I downloaded the current pacman package and updated it with pacman -U.
[root@1jzgte ~]# pacman -U pacman-3.0.4-3.pkg.tar.gz
warning: current locale is invalid; using default "C" locale
loading package data... done.
checking dependencies... done.
cleaning up... done.
(1/1) checking for file conflicts [#############...########################################] 100%
(1/1) upgrading pacman [#############...########################################] 100%
>>> PLEASE READ THE FOLLOWING!
>>> Use of the new rankmirrors script on your /etc/pacman.d/ files is
>>> highly recommended. Python is required, and read rankmirrors --help
>>> for details. In addition, mirrors are now listed by country, so
>>> move those that are geographically close to you to the top and
>>> remove the others BEFORE running rankmirrors.
[root@1jzgte ~]#
I still get the error though. How do I fix this? Where can I get the defualt /etc/pacman.d/ files?
This happened one day without me making any changes to any files.
Last edited by Phjeerable (2007-06-05 22:58:06)

I must have edited the pacman.conf file for some reason and not remembered. I copied the pacman.conf file from the pacman package and everything worked fine.
Thanks!

Cannot upgrade pacman due to conflict with package-query [SOLVED]

Package query 0.9 requires pacman <4, package-query 1 requires pacman >=4, therefore I am totally unable to upgrade, even using pacman -f
I'm aware that package-query is unsupported software, but this seems a bit stupid to me! Am I to uninstall package-query and therefore yaourt, only to reinstall them by hand, or is there a safe workaround?
Last edited by markhadman (2012-01-24 11:02:20)

jasonwryan wrote:
markhadman wrote:Groan - guess pacman 4 is going to eat a day of my life after all...
Or, realistically, 5 minutes.
But if that is too much for you to spare, rather than bemoaning the fact that the developers have spent a significant amount of time and effort on this upgrade that will cause you such inconvenience, you could just install another distro - that would probably eat a day.
Every other distro I've tried is inferior and eats up far more frustration time than Arch, which is why it's now on all my machines. I'm still putting off upgrading my 4 machines, though - because painful recent experience tells me that the chances of all 4 getting through this without day-eating breakage is about 6% (If you want a laugh at my expense, see this woeful example of breakage https://bugs.archlinux.org/task/27385). And yes, I'm aware that the longer I put it off, the worse my chances get.
Edit:
machine one (netbook).
Time taken so far: 44 minutes (inc reading up on a few errors, plus line-by-line comparison of rc.conf.pacnew, reboot plus check of basic system workiness, plus waiting unsuccessfully for package-query source to download).
Status: yaourt uninstallable (package-query git server appears to be down), openjdk6 broken due to bug, system otherwise appears healthy.
Prognosis: Total 90 minutes for 4 machines seems a reasonable (optimistic) estimate, but I'll further put the other machines off until package-query git server is back up and running.
And many apologies, this has veered somewhat off-topic and off-forum. I will probably make this my last post and let it die.
Further edit: How do I mark a thread as SOLVED? I can't see an option anywhere, or any way to edit the thread title!
edit: Nevermind, the trick is to edit the first post in the thread, it would seem.
Last edited by markhadman (2012-01-24 11:03:17)

No Usable Pacman Repositories Configured

Before we continue, I want to say that this is an Arch system and the following has to do with pacman-3.2.1.
Just for the sake of open source, I decided that I wanted to compile pacman, which it seems I successfully did, but there is a minor issue also when I execute it.
$ pacman -Syu
error: no usable package repositories configured.
I did a Google search, and found this thread where the guy successfully solved this problem after doing exactly what Cerebral said and editing /etc/pacman.conf. I did not find any other results from Google though.
To compile it, I did
$ ./configure
$ make
$ make install
Which is exactly how the pacman homepage said how to do it and how most other things are compiled too, which since I didn't use --prefix=/usr, it originally ended up /usr/local/bin like anything else would and I originally attempt to run it there using /usr/local/bin/pacman -Syu, which gave the same error, then I attempted what Cerebral said, but that did not work either and the same error is produced. I had the original pacman binary inside of my root directory, and it worked fine before I foolish removed it so I cannot test it right now (I am not concerned about it really because the goal is to compile pacman and use that one instead, but certainly it would've helped to know if /etc/pacman.conf is setup right after removing the original /etc/pacman.conf by mistake not paying attention too much to the --sysconfdir=/etc trigger - again not a real issue for me). Cerebral recommended that the OP of that thread/starter of that thread to issue:
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
$ make || return 1
$ make install || return 1
I believe he said that it shouldn't really be done with DESTDIR in his thread so I removed that part, but I also did try it with DESTDIR for the sake of saying I tried it if anyone wants to mention how I deviated from his post. He said what was important was the triggers on the ./configure line.
I was thinking my problem has something to do with repo-add (like I need to use it), but trying to figure out how to get that to work was hopeless because I couldn't find any db.pkg.tar.gz file, which is what I think it needs (the examples uses /path/to/your/repo.db.pkg.tar.gz, I am not entirely sure if it is a *.pkg.tar.gz extension and db is just to say repo database or if *.db.pkg.tar.gz is the extension), but I did try using it with the contents located in /var/cache/pacman/pkg/ and /var/lib/pacman/. I viewed it's man/info page, and the online documentation is the exact same. Again, I think that's what I need to learn to understand, or at least it would be good to know, right, haha, but also that since I do not know much about repo-add, maybe it wouldn't be the solution. It's just an educated guess.
This is what my current /etc/pacman.conf looks like.
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
RootDir = /
DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl %u > %o
#CleanMethod = KeepInstalled
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#NoPassiveFtp
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# An example of a disabled remote package repository with multiple servers
# available. To enable, uncomment the following lines. You can add preferred
# servers immediately after the header and they will be used before the
# default mirrors.
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
# The file referenced here should contain a list of 'Server = ' lines.
#Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
Which was generated by Cerebral's method for compiling, and then adjusted so my original pacman could work (everything was originally commented out, and I found that out by reading further on).
If you guys have any recommendation that may cause me to lose everything I have, I am not afraid to try it and I will not lose anything important.
Thank you in advance.
Last edited by Aprz (2008-12-05 12:02:02)

Cerebral wrote:
To make sure it's reading your conf file correctly, you could try pacman -v - which will spit out some info:
$ pacman -v
Root : /
Conf File : /etc/pacman.conf
DB Path : /var/lib/pacman/
Cache Dirs: /var/cache/pacman/pkg/
Lock File : /var/lib/pacman/db.lck
Log File : /var/log/pacman.log
Targets : None
error: no operation specified (use -h for help)
For even more detail, you can run pacman --debug 1
Interesting! I did not know that and I can see that I must of done something wrong because everything is pointing too /usr/local/ instead. Very interesting. Let me edit the files in there and check that out.
$ Root : /
Conf File : /usr/local/etc/pacman.conf
DB Path : /usr/local/var/lib/pacman/
Cache Dirs: /usr/local/var/cache/pacman/pkg/
Lock File : /usr/local/var/lib/pacman/db.lck
Log File : /usr/local/var/log/pacman.log
Targets : None
error: no operation specified (use -h for help)
That may be the culprit.
Edit: Yeap, it is working now when I edited the configuration files in /usr/local/etc/pacman.conf. That must mean that I forgot the --sysconfdir=/etc when I did ./configure, sounds right? I'll try recompiling it making sure that option is in there along with the options you mentioned in the post, which is funny that I was refering to what you said on that other post, failed, and all of the sudden here you are helping. Pretty neat. ^_^
Compiling now...
Nope, it still tries to read from /usr/local/etc/pacman.conf.
It still creates /usr/local/etc/pacman.conf, but I decided to experiment and remove it to see what would happen.
$ pacman -v
error: config file /usr/local/etc/pacman.conf could not be read.
$ ln -s /etc/pacman.conf /usr/local/etc/
necessary changes are made to /etc/pacman.conf
$ pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
local database is up to date
Which after I do make install following your instructions on the other thread, /etc/pacman.conf is overwritten with the new one that comments out everything and doesn't have all the necessary server/include lines at the bottom.
What's going on here? I compile it exactly like this:
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
$ make
$ make install
Last edited by Aprz (2008-12-05 15:27:51)

(solved) repositories configured after removal/installation of Pacman

Hi!
I just had a wierd problem with Pacman : when I typed
pacman -Syu
it said that it was unable to get core.db.tar.gz and so on for other repos.
Then, I found a post that said the person had uninstalled pacman using
pacman -R pacman
Well, I tried to do by downloading the tarred package, then extracted it then :
./configure --prefix=/usr/bin --exec-prefix=/usr/bin && make && make install && make clean
Now, when I type pacman -Syu, it returns :
error: no usable package repositories configured.
Here are my config files :
/etc/pacman.conf
# /etc/pacman.conf
# See the pacman manpage for option directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# Testing is disabled by default. To enable, uncomment the following
# two lines. You can add preferred servers immediately after the header,
# and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Server = ftp://ftp.archlinux.org/core/os/i686
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
# Unstable is disabled by default. To enable, uncomment the following
# two lines. You can add preferred servers immediately after the header,
# and they will be used before the default mirrors.
#[unstable]
#Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
and /etc/aacman.d/mirrorlist
# Arch Linux repository mirrorlist
# United States
Server = ftp://ftp.archlinux.org/$repo/os/i686
Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/i686
Server = ftp://mirrors.unixheads.org/archlinux/$repo/os/i686
Server = ftp://ftp-linux.cc.gatech.edu/pub/linux/distributions/archlinux/$repo/os/i686
Server = ftp://mirror.cs.vt.edu/pub/ArchLinux/$repo/os/i686
Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/i686
Server = ftp://ftp.ibiblio.org/pub/linux/distributions/archlinux/$repo/os/i686
Server = http://holmes.umflint.edu/archlinux/$repo/os/i686
Server = http://mirror.neotuli.net/arch/$repo/os/i686
# South America
# - Brazil
#Server = http://archlinux.c3sl.ufpr.br/$repo/os/i686
#Server = ftp://archlinux.c3sl.ufpr.br/archlinux/$repo/os/i686
#Server = ftp://ftp.las.ic.unicamp.br/pub/archlinux/$repo/os/i686
# Europe
# - Austria
#Server = ftp://gd.tuwien.ac.at/opsys/linux/archlinux/$repo/os/i686
# - Belgium
#Server = ftp://ftp.belnet.be/mirror/archlinux.org/$repo/os/i686
# - Czech Republic
#Server = ftp://ftp.sh.cvut.cz/MIRRORS/arch/$repo/os/i686
# - Estonia
#Server = ftp://ftp.estpak.ee/pub/archlinux/$repo/os/i686
# - France
#Server = ftp://mir1.archlinuxfr.org/archlinux/$repo/os/i686
#Server = ftp://mir2.archlinuxfr.org/archlinux/$repo/os/i686
#Server = ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/$repo/os/i686
#Server = http://mir.archlinux.fr/$repo/os/i686
#Server = ftp://ftp.free.fr/mirrors/ftp.archlinux.org/$repo/os/i686
# - Germany
#Server = ftp://ftp.hosteurope.de/mirror/ftp.archlinux.org/$repo/os/i686
#Server = ftp://ftp5.gwdg.de/pub/linux/archlinux/$repo/os/i686
#Server = ftp://ftp.uni-bayreuth.de/pub/linux/archlinux/$repo/os/i686
#Server = ftp://ftp.archlinuxppc.org/i686/$repo/os/i686
#Server = ftp://ftp.tu-chemnitz.de/pub/linux/archlinux/$repo/os/i686
#Server = http://ftp.uni-kl.de/pub/linux/archlinux/$repo/os/i686
## - Great Britain
#Server = http://www.mirrorservice.org/sites/ftp.archlinux.org/$repo/os/i686
# - Greece
#Server = ftp://ftp.ntua.gr/pub/linux/archlinux/$repo/os/i686
# - Hungary
#Server = ftp://ftp.mfa.kfki.hu/pub/mirrors/ftp.archlinux.org/$repo/os/i686
# - Ireland
#Server = ftp://ftp.heanet.ie/mirrors/ftp.archlinux.org/$repo/os/i686
# - Italy
#Server = ftp://mi.mirror.garr.it/mirrors/archlinux/$repo/os/i686
# - Netherlands
#Server = ftp://ftp.nluug.nl/pub/metalab/distributions/archlinux/$repo/os/i686
#Server = ftp://ftp.surfnet.nl/pub/os/Linux/distr/archlinux/$repo/os/i686
# - Poland
#Server = ftp://mirror.icis.pcz.pl/archlinux/$repo/os/i686
#Server = http://piotrkosoft.net/pub/mirrors/ftp.archlinux.org/$repo/os/i686
#Server = ftp://ftp.piotrkosoft.net/pub/mirrors/ftp.archlinux.org/$repo/os/i686
# - Portugal
#Server = ftp://cesium.di.uminho.pt/pub/archlinux/$repo/os/i686
# - Romania
#Server = ftp://ftp.iasi.roedu.net/mirrors/archlinux.org/$repo/os/i686
# - Russia
#Server = ftp://mirror.yandex.ru/archlinux/$repo/os/i686
#Server = http://archlinux.freeside.ru/$repo/os/i686
# - Sweden
#Server = ftp://ftp.ds.hj.se/pub/os/linux/archlinux/$repo/os/i686
#Server = ftp://ftp.gigabit.nu/$repo/os/i686
# - Switzerland
#Server = ftp://archlinux.puzzle.ch/$repo/os/i686
# - Turkey
#Server = http://server.elsistech.com/archlinux/$repo/os/i686
# - Ukraine
#Server = ftp://hell.org.ua/archlinux/$repo/os/i686
# NOTE: ftp.linux.kiev.ua only has the i686 arch and not x86_64
Server = ftp://ftp.linux.kiev.ua/pub/Linux/ArchLinux/$repo/os/i686
# Asia
# - Israel
#Server = http://mirror.isoc.org.il/pub/archlinux/$repo/os/i686
# Australia
#Server = ftp://mirror.pacific.net.au/linux/archlinux/$repo/os/i686
#Server = ftp://mirror.aarnet.edu.au/pub/archlinux/$repo/os/i686
What's the problem? Thank you!
Last edited by valandil (2008-03-13 12:52:19)

Thanks guys, it worked.
However, now pacman returns this to pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : No address record
error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : No address record
error: failed retrieving file 'core.db.tar.gz' from locke.suu.edu : No address record
error: failed retrieving file 'core.db.tar.gz' from mirrors.unixheads.org : No address record
error: failed retrieving file 'core.db.tar.gz' from ftp-linux.cc.gatech.edu : No address record
error: failed retrieving file 'core.db.tar.gz' from mirror.cs.vt.edu : No address record
error: failed retrieving file 'core.db.tar.gz' from mirrors.easynews.com : No address record
error: failed retrieving file 'core.db.tar.gz' from ftp.ibiblio.org : No address record
error: failed retrieving file 'core.db.tar.gz' from holmes.umflint.edu : No address record
error: failed retrieving file 'core.db.tar.gz' from mirror.neotuli.net : No address record
error: failed retrieving file 'core.db.tar.gz' from ftp.linux.kiev.ua : No address record
error: failed retrieving file 'extra.db.tar.gz' from ftp.archlinux.org : No address record
error: failed retrieving file 'extra.db.tar.gz' from locke.suu.edu : No address record
error: failed retrieving file 'extra.db.tar.gz' from mirrors.unixheads.org : No address record
error: failed retrieving file 'extra.db.tar.gz' from ftp-linux.cc.gatech.edu : No address record
error: failed retrieving file 'extra.db.tar.gz' from mirror.cs.vt.edu : No address record
error: failed retrieving file 'extra.db.tar.gz' from mirrors.easynews.com : No address record
error: failed retrieving file 'extra.db.tar.gz' from ftp.ibiblio.org : No address record
error: failed retrieving file 'extra.db.tar.gz' from holmes.umflint.edu : No address record
error: failed retrieving file 'extra.db.tar.gz' from mirror.neotuli.net : No address record
error: failed retrieving file 'extra.db.tar.gz' from ftp.linux.kiev.ua : No address record
error: failed retrieving file 'community.db.tar.gz' from ftp.archlinux.org : No address record
error: failed retrieving file 'community.db.tar.gz' from locke.suu.edu : No address record
error: failed retrieving file 'community.db.tar.gz' from mirrors.unixheads.org : No address record
error: failed retrieving file 'community.db.tar.gz' from ftp-linux.cc.gatech.edu : No address record
error: failed retrieving file 'community.db.tar.gz' from mirror.cs.vt.edu : No address record
error: failed retrieving file 'community.db.tar.gz' from mirrors.easynews.com : No address record
error: failed retrieving file 'community.db.tar.gz' from ftp.ibiblio.org : No address record
error: failed retrieving file 'community.db.tar.gz' from holmes.umflint.edu : No address record
error: failed retrieving file 'community.db.tar.gz' from mirror.neotuli.net : No address record
error: failed retrieving file 'community.db.tar.gz' from ftp.linux.kiev.ua : No address record

[Solved]Gnome-pacman asking to upgrade packages, that were removed

Dear Archers
I have removed from my system 'eog', 'cheese' and other gnome packages that I do not use. Today, when I tried to upgrade, it is including the removed packages also. Is it now like this? All or none?
[root@KRISHNA san2ban]# pacman -Syu
:: Synchronizing package databases...
core 101.8 KiB 159K/s 00:01 [######################] 100%
extra 1389.9 KiB 74.5K/s 00:19 [######################] 100%
community 1647.0 KiB 62.9K/s 00:26 [######################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (153): accountsservice-0.6.18-1 at-spi2-atk-2.4.0-1
at-spi2-core-2.4.1-1 atk-2.4.0-1 baobab-3.4.1-1
brasero-3.4.1-1 cantarell-fonts-0.0.8-1 caribou-0.4.2-1
cheese-3.4.1-1 clutter-1.10.2-1 clutter-gst-1.5.4-1
clutter-gtk-1.2.0-1 cogl-1.10.2-1 colord-0.1.19-1
cups-pk-helper-0.2.2-1 dconf-0.12.0-1 eog-3.4.1-1
eog-plugins-3.4.0-1 evince-3.4.0-1
evolution-data-server-3.4.1-1 folks-0.6.9-2
gcalctool-6.4.1.1-1 gconf-3.2.5-2 gcr-3.4.1-1
gdk-pixbuf2-2.26.1-1 gdm-3.4.1-2 gedit-3.4.1-1
geoclue-0.12.0-5 gjs-1.32.0-1 glib-networking-2.32.1-1
glib2-2.32.1-2 glibmm-2.32.0-1 gmime-2.6.9-1
gnome-applets-3.4.1-1 gnome-backgrounds-3.4.1-1
gnome-bluetooth-3.4.0-1 gnome-color-manager-3.4.0-2
gnome-contacts-3.4.0-1 gnome-control-center-3.4.1-1
gnome-desktop-1:3.4.1-1 gnome-dictionary-3.4.0-1
gnome-disk-utility-3.4.0-1 gnome-documents-0.4.1-1
gnome-font-viewer-3.4.0-1 gnome-games-3.4.1-1
gnome-icon-theme-3.4.0-1 gnome-icon-theme-extras-3.4.0-1
gnome-icon-theme-symbolic-3.4.0-1 gnome-keyring-3.4.1-1
gnome-media-3.4.0-1 gnome-menus-3.4.0-1 gnome-nettool-3.1.1-1
gnome-online-accounts-3.4.1-1 gnome-panel-3.4.1-2
gnome-power-manager-3.4.0-1 gnome-screensaver-3.4.1-1
gnome-screenshot-3.4.1-1 gnome-search-tool-3.4.0-1
gnome-session-3.4.1-1 gnome-settings-daemon-3.4.1-1
gnome-shell-3.4.1-1 gnome-system-log-3.4.1-1
gnome-system-monitor-3.4.1-1 gnome-terminal-3.4.1.1-1
gnome-themes-standard-3.4.1-1 gnome-user-docs-3.4.1-1
gnome-utils-3.4.0-1 gnome-video-effects-0.4.0-1
gobject-introspection-1.32.1-1
gsettings-desktop-schemas-3.4.1-1 gstreamer0.10-bad-0.10.23-1
gtk-vnc-0.5.0-1 gtk3-3.4.1-1 gtkmm3-3.4.0-1
gtksourceview3-3.4.1-1 gucharmap-3.4.1.1-1 gvfs-1.12.1-1
gvfs-obexftp-1.12.1-1 icu-49.1.1-1 iproute2-3.3.0-1
libchamplain-0.12.2-1 libcroco-0.6.5-1 libgdata-0.12.0-1
libgnome-keyring-3.4.1-1 libgnomekbd-3.4.0.2-1
libgsf-1.14.23-1 libgweather-3.4.1-1 libgxps-0.2.2-1
libimobiledevice-1.1.1-3 libmusicbrainz4-4.0.0-1
libpeas-1.4.0-1 libplist-1.8-2 libquvi-0.4.0-3
libquvi-scripts-0.4.2-1 libreoffice-base-3.5.2-1
libreoffice-calc-3.5.2-1 libreoffice-common-3.5.2-1
libreoffice-draw-3.5.2-1 libreoffice-en-GB-3.5.2-1
libreoffice-gnome-3.5.2-1 libreoffice-impress-3.5.2-1
libreoffice-math-3.5.2-1
libreoffice-postgresql-connector-3.5.2-1
libreoffice-sdk-3.5.2-1 libreoffice-sdk-doc-3.5.2-1
libreoffice-writer-3.5.2-1 librsvg-2.36.1-1
libsocialweb-0.25.20-1 libsoup-2.38.1-1 libsoup-gnome-2.38.1-1
libsystemd-44-5 libtracker-sparql-0.14.0-3 libwacom-0.4-1
libwebkit3-1.8.0-2 libwnck3-3.4.0-1 libxklavier-5.2.1-2
man-pages-3.39-1 mash-0.2.0-1 metacity-2.34.3-1
mousetweaks-3.4.1-1 mutter-3.4.1-1 mx-1.4.3-2
nautilus-3.4.1-1 nautilus-sendto-3.0.2-1
network-manager-applet-0.9.4.1-1 networkmanager-0.9.4.0-2
nmap-5.51-3 pango-1.30.0-1 pyatspi-2.4.0-1
pygobject-devel-3.2.0-1 pylint-0.25.1-1
python-egenix-mx-base-3.2.3-1 python-logilab-astng-0.23.1-1
python-logilab-common-0.58.0-1 python2-gobject-3.2.0-1
raptor-2.0.7-2 seahorse-3.4.1-1 sound-juicer-3.4.0-1
sushi-0.4.1-1 telepathy-glib-0.18.1-1 telepathy-logger-0.4.0-1
telepathy-mission-control-5.12.0-1 totem-3.4.1-1
totem-plparser-3.4.1-1 tracker-0.14.0-3 udisks2-1.94.0-1
vinagre-3.4.1-1 vino-3.4.1-1 vte-common-0.32.1-1
vte3-0.32.1-1 yelp-3.4.1-1 yelp-xsl-3.4.1-1 zenity-3.4.0-1
Total Download Size: 243.26 MiB
Total Installed Size: 1290.16 MiB
Net Upgrade Size: 205.83 MiB
Proceed with installation? [Y/n] n
[root@KRISHNA san2ban]#
Removed unwanted packages manually
Last edited by San2ban (2012-04-24 17:02:50)

Anyway, as usual, I have to manually remove unused packages. Earlier, only tose packages that were explicitly installed, were upgraded. Now, it is forcing me to accept all, or none

I can't update packages after upgrading pacman to 4.0.3

I know this was already treated broadly about two months ago, but I can't update after upgrading pacman because of continuous problems with certain signatures (at least one).
I have already tried this:
rm -rf /etc/pacman.d/gnupg
pacman -Scc
pacman-key --init
pacman-key --populate archlinux
But I still get this error when trying to upgrade the system:
error: virtuoso: signature from "Andrea Scarpino (Arch Linux) <[email protected]>" is invalid
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
Could anybody help me? I'm pretty devastated with this.
Thanks!
My /etc/pacman.conf
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#UseDelta
#TotalDownload
CheckSpace
#VerbosePkgLists
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
#SigLevel = Optional TrustedOnly
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
[community]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
Last edited by [DoodoM] (2012-08-03 23:39:56)

Thanks everyone! I guess it was a faulty mirror.
I also had problems upgrading glibc because /lib had to be linked to /usr/lib, but I fixed it seeking for helpful tips on the forum. What I did was move everything from /lib to /usr/lib, shutdown, start adding break=postmount to kernel line, mount the filesystem, remove /lib folder, link /usr/lib to /lib and reboot. Then I reinstalled glibc and everything went well.
Now some fonts look half-cutted in Gnome Shell when the window or panel which contains them is in background and I don't know why. But it is not the first time I have "graphical artifacts" with Arch Linux on this laptop. I think has something to do with the compositing.

[Solved] No Usable Pacman Repositories Configured

I had the liblzma.so.0 problem and tought pacman was the problem. I tried to reinstall pacman several time and find out that the liblzma.so.0 symlink was the problem.
Now pacman don't work I have the following message:
No Usable Pacman Repositories Configured
Here is the pacman -v output:
Root : /
Conf File : /usr/local/etc/pacman.conf
DB Path : /usr/local/var/lib/pacman/
Cache Dirs: /usr/local/var/cache/pacman/pkg/
Lock File : /usr/local/var/lib/pacman/db.lck
Log File : /usr/local/var/log/pacman.log
Targets : --
Erreur: aucune opération spécifiée (utiliser -h pour l'aide)
That wrong! /usr/local/ shouldn't be there but I am unable to change it!
Last edited by srivo (2010-12-19 20:39:14)

Here is the output:
# /usr/bin/pacman -Qil pacman
Nom : pacman
Version : 3.4.1-1
URL : [url]http://www.archlinux.org/pacman/[/url]
Licences : GPL
Groupes : base
Fournit : --
Dépend de : bash libarchive>=2.7.1 libfetch>=2.25
pacman-mirrorlist
Dépendances opt. : fakeroot: for makepkg usage as normal user
curl: for rankmirrors usage
Requis par : archup package-query pkgstats yaourt
Est en conflit avec : --
Remplace : --
Taille (installé) : 2244,00 K
Paqueteur : Dan McGee <[email protected]>
Architecture : i686
Compilé le : ven 03 sep 2010 21:12:12 EDT
Installé le : dim 19 déc 2010 13:31:36 EST
Motif d'installation : Explicitement installé
Script d'installation : Oui
Description : A library-based package manager with dependency support
pacman /etc/
pacman /etc/bash_completion.d/
pacman /etc/bash_completion.d/pacman
pacman /etc/makepkg.conf
pacman /etc/pacman.conf
pacman /usr/
pacman /usr/bin/
pacman /usr/bin/cleanupdelta
pacman /usr/bin/makepkg
pacman /usr/bin/pacman
pacman /usr/bin/pacman-optimize
pacman /usr/bin/pkgdelta
pacman /usr/bin/rankmirrors
pacman /usr/bin/repo-add
pacman /usr/bin/repo-remove
pacman /usr/bin/testdb
pacman /usr/bin/testpkg
pacman /usr/bin/vercmp
pacman /usr/include/
pacman /usr/include/alpm.h
pacman /usr/include/alpm_list.h
pacman /usr/lib/
pacman /usr/lib/libalpm.a
pacman /usr/lib/libalpm.so
pacman /usr/lib/libalpm.so.5
pacman /usr/lib/libalpm.so.5.0.1
pacman /usr/share/
pacman /usr/share/locale/
pacman /usr/share/locale/ca/
pacman /usr/share/locale/ca/LC_MESSAGES/
pacman /usr/share/locale/ca/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/ca/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/cs/
pacman /usr/share/locale/cs/LC_MESSAGES/
pacman /usr/share/locale/cs/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/cs/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/de/
pacman /usr/share/locale/de/LC_MESSAGES/
pacman /usr/share/locale/de/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/de/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/el/
pacman /usr/share/locale/el/LC_MESSAGES/
pacman /usr/share/locale/el/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/el/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/en_GB/
pacman /usr/share/locale/en_GB/LC_MESSAGES/
pacman /usr/share/locale/en_GB/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/en_GB/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/es/
pacman /usr/share/locale/es/LC_MESSAGES/
pacman /usr/share/locale/es/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/es/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/fr/
pacman /usr/share/locale/fr/LC_MESSAGES/
pacman /usr/share/locale/fr/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/fr/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/hu/
pacman /usr/share/locale/hu/LC_MESSAGES/
pacman /usr/share/locale/hu/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/hu/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/it/
pacman /usr/share/locale/it/LC_MESSAGES/
pacman /usr/share/locale/it/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/it/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/kk/
pacman /usr/share/locale/kk/LC_MESSAGES/
pacman /usr/share/locale/kk/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/kk/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/nb/
pacman /usr/share/locale/nb/LC_MESSAGES/
pacman /usr/share/locale/nb/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/nb/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/pl/
pacman /usr/share/locale/pl/LC_MESSAGES/
pacman /usr/share/locale/pl/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/pl/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/pt/
pacman /usr/share/locale/pt/LC_MESSAGES/
pacman /usr/share/locale/pt/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/pt/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/pt_BR/
pacman /usr/share/locale/pt_BR/LC_MESSAGES/
pacman /usr/share/locale/pt_BR/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/pt_BR/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/ro/
pacman /usr/share/locale/ro/LC_MESSAGES/
pacman /usr/share/locale/ro/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/ro/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/ru/
pacman /usr/share/locale/ru/LC_MESSAGES/
pacman /usr/share/locale/ru/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/ru/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/sk/
pacman /usr/share/locale/sk/LC_MESSAGES/
pacman /usr/share/locale/sk/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/sk/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/sv/
pacman /usr/share/locale/sv/LC_MESSAGES/
pacman /usr/share/locale/sv/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/sv/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/tr/
pacman /usr/share/locale/tr/LC_MESSAGES/
pacman /usr/share/locale/tr/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/tr/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/uk/
pacman /usr/share/locale/uk/LC_MESSAGES/
pacman /usr/share/locale/uk/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/uk/LC_MESSAGES/pacman.mo
pacman /usr/share/locale/zh_CN/
pacman /usr/share/locale/zh_CN/LC_MESSAGES/
pacman /usr/share/locale/zh_CN/LC_MESSAGES/libalpm.mo
pacman /usr/share/locale/zh_CN/LC_MESSAGES/pacman.mo
pacman /usr/share/man/
pacman /usr/share/man/man3/
pacman /usr/share/man/man3/libalpm.3.gz
pacman /usr/share/man/man5/
pacman /usr/share/man/man5/PKGBUILD.5.gz
pacman /usr/share/man/man5/makepkg.conf.5.gz
pacman /usr/share/man/man5/pacman.conf.5.gz
pacman /usr/share/man/man8/
pacman /usr/share/man/man8/makepkg.8.gz
pacman /usr/share/man/man8/pacman.8.gz
pacman /usr/share/man/man8/repo-add.8.gz
pacman /usr/share/man/man8/repo-remove.8.gz
pacman /usr/share/pacman/
pacman /usr/share/pacman/ChangeLog.proto
pacman /usr/share/pacman/PKGBUILD-split.proto
pacman /usr/share/pacman/PKGBUILD.proto
pacman /usr/share/pacman/proto.install
pacman /usr/share/zsh/
pacman /usr/share/zsh/site-functions/
pacman /usr/share/zsh/site-functions/_pacman
pacman /var/
pacman /var/cache/
pacman /var/cache/pacman/
pacman /var/cache/pacman/pkg/
pacman /var/lib/
pacman /var/lib/pacman/

[SOLVED] Make Pacman cache packages installed with -U

When installing a package with -U, pacman doesn't cache packages as it does when installing with -S. Is there a way to change this behavior?
I read somewhere that specifying the package's full path and prepending "file://", as in "pacman -U file://path/to/package.pkg.tar.xz", but this often complains of an "invalid or corrupted package (PGP signature)".
How can I make pacman always copy installed packages to the cache?
MOD EDIT: change 'closed' to 'solved' in title to avoid confusion
Last edited by fukawi2 (2013-07-06 13:09:21)

You can't. This has been discussed on the bugtracker several times.
https://bugs.archlinux.org/task/35699
https://bugs.archlinux.org/task/31243
https://bugs.archlinux.org/task/15143
https://bugs.archlinux.org/task/18012
If you're building the packages yourself with makepkg, you can set PKGDEST to your cache in makepkg.conf. Otherwise you could write a small pacman wrapper that copies the package after installing it.

[SOLVED]Cannot upgrade pacman because gnupg and gnupg2 are in conflict

I have tried a system update with "pacman -Syu". Pacman says that pacman needs to be upgraded first. I let this happen. Then I get the conflict. Both paths (remove gnupg2 and not remove gnupg2) fail.
:: gnupg and gnupg2 are in conflict. Remove gnupg2? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: requires gcc-libs=4.6.2-7
:: gnupg and gnupg2 are in conflict. Remove gnupg2? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
Has anybody an idea how to proceed. An atempt to upgrade gcc fails as well
pacman -S gcc
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] n
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: libtool: requires gcc=4.6.2
Since any incosistency between gcc and its related libraries are usual fatal, I prefer not to experiment.
Thanks in advance for any hint.
Helmut
Last edited by helmut (2012-05-30 19:49:59)

Covered extensively over the last couple of months, eg:
https://bbs.archlinux.org/viewtopic.php?id=139412
https://bbs.archlinux.org/viewtopic.php?pid=1057709
et al...

[SOLVED] Would "pacman -S foo" fail if system's package list is old?

I'm new to Arch and want to understand my system as much as possible.
In several places in the wiki it is recommended to install a single package with "pacman -S foo" instead of "pacman -Sy foo" unless I'm doing a system upgrade at the same time, so that versions of foo and its dependencies are in sync with all the other packages on my system. This seems to be good advice and I follow it.
However, I recently read that the Arch repos only have the latest version of any given package. Now I'm confused. So what happens if the versions of foo and its dependencies on my package masterlist are outdated? Would "pacman -S foo" fail? If not, how can it possibly work if pacman is trying to install package versions that are no longer in the repository?
Last edited by bdantas (2014-06-18 12:34:01)

To be safest, always use `pacman -Syu <newpackage>`.
I generally use `pacman -S <newpackage>` which is a bit quicker - and this is fine if you update frequently. I do a `-Syu` at least once a day.
Never ever do a `pacman -Sy <newpackage>`. This can lead to severe breakage and potentially a completely unbootable system. In fact never do `pacman -Sy` in any way unless there is also a 'u' there (i.e. "-Syu"). I think a feature request for pacman could be made to have a prompt when such a command is entered "Are you an idiot?[Y/n] Do you want pacman to destroy your system? [Y/n]".
In contrast, `pacman -S <newpackage>` should never do any damage. If your package database is still current, it will work fine. If you package database is too old, it will exit with an error message without making any changes to your system. The error message is along the lines of the package/file not being found in the repos or on the server(s).
EDIT: as this is already well covered in the wiki this may be best suited to the NC.

[SOLVED] pacman: grep database for specific packages?

$ pacman -Ss zsh
extra/grml-zsh-config 0.9.1-1
grml's zsh setup
extra/zsh 5.0.2-4 [installed]
A very advanced and programmable command interpreter (shell) for UNIX
community/zsh-lovers 0.8.3-2
A collection of tips, tricks and examples for the Z shell.
community/zshdb 0.08-2
A debugger for zsh scripts.
$ pacman -Ss zsh | cut -s -d/ -f2 | grep '^zsh ' | cut -d' ' -f1
zsh
I'm trying to grep pacman output for a specific packages (not just zsh) and receive only the package name as it was passed to pacman as a output (if it exists in the repos that is, otherwise blank / exit 1). The above command works fine in the terminal but when I'm trying to use it from a bash script it only returns blanks. How come?
Simplified version of the script:
tank (zsh ksh)
for x in ${tank[*]}; do
echo $x
present=$(pacman -Qs ${x} | cut -s -d/ -f2 | grep '^${x} ' | cut -d' ' -f1)
echo $present
done
I expect it to return output of a pacman command in the second echo (or blank if there's no packgae like that).
edit: change of title.
2nd edit: added simplified script.
Last edited by thoajdzm (2013-11-16 14:34:59)

Raynman wrote:
And consider using
$ pacman -Ssq '^zsh$'
instead of that pipeline.
Brilliant! Much leaner. However it still doesn't work from a script:
tank=(zsh)
for x in ${tank[*]}; do
echo $x
present=$(pacman -Ssq '^${x}$')
echo $present
done
Second echo returns blank... Am I quoting something wrong?

[SOLVED] Can Pacman Manage My Custom Packages

I am going to make a custom build of MPlayer because I want it patched to take advantage of the Compiz Video plugin. I think I might enable a couple other options that are disabled as well. The thing I'm not sure of is how pacman will react to my package. I know I can install it with pacman, but when a new official MPlayer package is released in the repos, will it update it and override my custom package? If so, I thought it might help if I changed the package name, but then I thought that might mess up dependency tracking. For instance, if I make a custom package of which other packages rely on, will those other packages be able to see mine and list the dependency as fulfilled?
Basically I want a way for my system to see my custom package as something that can fulfill dependencies for other official packages that might rely on that particular program. But at the same time I don't want it overridden when a new official package comes out since it likely won't contain the options I want enabled. If it would give a message indicating a new version is available but not install it, that would really help. Is this possible, and what would be the best way to handle this?
Last edited by nLEyETn (2008-10-06 06:44:47)

Thanks, that seems to be just what I was looking for
Last edited by nLEyETn (2008-10-06 06:45:11)

[SOLVED] Pacman: cant install, remove, update packages

I'm new to Arch, and yes I've read the Wiki and the sticky post "pacman error: FILENAME exists in filesystem".
I can't install or update packages. Just synced the local database. I want to install the package "mc", so I ran:
pacman -S mc
All required packages were downloaded but then I got lots of:
[package-name]: /path/to/file exists in file system
I tried to remove that package but it says:
loading package data...
error: '[package-name]': could not find or read package
I'm totally confused!
Last edited by presario (2009-02-13 05:08:06)

here's the output from "pacman -S mc"
resolving dependencies...
looking for inter-conflicts...
Targets: kernel-headers-2.6.27.6-2 tzdata-2009a-1 glibc-2.9-4 ncurses-5.7-2
Total Download Size: 0.00 MB
Total Installed Size: 51.91 MB
checking package integrity...
checking for file conflicts...
error: could not prepare transaction
kernel-headers: /usr/include/asm-generic/errno-base.h exists in filesystem
kernel-headers: /usr/include/asm-generic/errno.h exists in filesystem
kernel-headers: /usr/include/asm-generic/fcntl.h exists in filesystem
kernel-headers: /usr/include/asm-generic/ioctl.h exists in filesystem
kernel-headers: /usr/include/asm-generic/mman.h exists in filesystem
kernel-headers: /usr/include/asm-generic/poll.h exists in filesystem
kernel-headers: /usr/include/asm-generic/resource.h exists in filesystem
kernel-headers: /usr/include/asm-generic/siginfo.h exists in filesystem
kernel-headers: /usr/include/asm-generic/signal.h exists in filesystem
kernel-headers: /usr/include/asm-generic/statfs.h exists in filesystem
kernel-headers: /usr/include/asm/a.out.h exists in filesystem
kernel-headers: /usr/include/asm/auxvec.h exists in filesystem
kernel-headers: /usr/include/asm/boot.h exists in filesystem
kernel-headers: /usr/include/asm/bootparam.h exists in filesystem
tzdata: /usr/bin/tzselect exists in filesystem
tzdata: /usr/sbin/zdump exists in filesystem
tzdata: /usr/sbin/zic exists in filesystem
tzdata: /usr/share/man/man3/newctime.3.gz exists in filesystem
tzdata: /usr/share/man/man3/newtzset.3.gz exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Abidjan exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Accra exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Addis_Ababa exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Algiers exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Asmara exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Asmera exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Bamako exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Bangui exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Banjul exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Bissau exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Blantyre exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Brazzaville exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Bujumbura exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Cairo exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Casablanca exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Ceuta exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Conakry exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Dakar exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Dar_es_Salaam exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Djibouti exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Douala exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/El_Aaiun exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Freetown exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Gaborone exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Harare exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Johannesburg exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Kampala exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Khartoum exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Kigali exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Kinshasa exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Lagos exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Libreville exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Lome exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Luanda exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Lubumbashi exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Lusaka exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Malabo exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Maputo exists in filesystem
tzdata: /usr/share/zoneinfo/Africa/Maseru exists in filesystem
glibc: /etc/locale.gen exists in filesystem
glibc: /etc/nscd.conf exists in filesystem
glibc: /etc/rc.d/nscd exists in filesystem
glibc: /etc/rpc exists in filesystem
glibc: /lib/ld-linux.so.2 exists in filesystem
glibc: /lib/libBrokenLocale.so.1 exists in filesystem
glibc: /lib/libSegFault.so exists in filesystem
glibc: /lib/libanl.so.1 exists in filesystem
glibc: /lib/libc.so.6 exists in filesystem
glibc: /lib/libcidn.so.1 exists in filesystem
glibc: /lib/libcrypt.so.1 exists in filesystem
glibc: /lib/libdl.so.2 exists in filesystem
glibc: /lib/libm.so.6 exists in filesystem
glibc: /lib/libmemusage.so exists in filesystem
glibc: /lib/libnsl.so.1 exists in filesystem
glibc: /lib/libnss_compat.so.2 exists in filesystem
glibc: /lib/libnss_dns.so.2 exists in filesystem
glibc: /lib/libnss_files.so.2 exists in filesystem
glibc: /lib/libnss_hesiod.so.2 exists in filesystem
glibc: /lib/libnss_nis.so.2 exists in filesystem
glibc: /lib/libnss_nisplus.so.2 exists in filesystem
glibc: /lib/libpcprofile.so exists in filesystem
glibc: /lib/libpthread.so.0 exists in filesystem
glibc: /lib/libresolv.so.2 exists in filesystem
glibc: /lib/librt.so.1 exists in filesystem
glibc: /lib/libthread_db-1.0.so exists in filesystem
glibc: /lib/libthread_db.so.1 exists in filesystem
glibc: /lib/libutil.so.1 exists in filesystem
glibc: /sbin/ldconfig exists in filesystem
glibc: /sbin/sln exists in filesystem
glibc: /usr/bin/catchsegv exists in filesystem
glibc: /usr/bin/gencat exists in filesystem
glibc: /usr/bin/getconf exists in filesystem
glibc: /usr/bin/getent exists in filesystem
glibc: /usr/bin/iconv exists in filesystem
glibc: /usr/bin/ldd exists in filesystem
glibc: /usr/bin/lddlibc4 exists in filesystem
glibc: /usr/bin/locale exists in filesystem
glibc: /usr/bin/localedef exists in filesystem
glibc: /usr/bin/mtrace exists in filesystem
glibc: /usr/bin/pcprofiledump exists in filesystem
glibc: /usr/bin/rpcgen exists in filesystem
glibc: /usr/bin/sprof exists in filesystem
glibc: /usr/bin/xtrace exists in filesystem
glibc: /usr/include/_G_config.h exists in filesystem
glibc: /usr/include/a.out.h exists in filesystem
glibc: /usr/include/aio.h exists in filesystem
glibc: /usr/include/aliases.h exists in filesystem
glibc: /usr/include/alloca.h exists in filesystem
glibc: /usr/include/ar.h exists in filesystem
glibc: /usr/include/argp.h exists in filesystem
glibc: /usr/include/argz.h exists in filesystem
glibc: /usr/include/arpa/ftp.h exists in filesystem
glibc: /usr/include/arpa/inet.h exists in filesystem
glibc: /usr/include/arpa/nameser.h exists in filesystem
glibc: /usr/include/arpa/nameser_compat.h exists in filesystem
glibc: /usr/include/arpa/telnet.h exists in filesystem
glibc: /usr/include/arpa/tftp.h exists in filesystem
glibc: /usr/include/assert.h exists in filesystem
glibc: /usr/include/bits/a.out.h exists in filesystem
glibc: /usr/include/bits/byteswap.h exists in filesystem
glibc: /usr/include/bits/cmathcalls.h exists in filesystem
glibc: /usr/include/bits/confname.h exists in filesystem
glibc: /usr/include/bits/dirent.h exists in filesystem
glibc: /usr/include/bits/dlfcn.h exists in filesystem
glibc: /usr/include/bits/elfclass.h exists in filesystem
glibc: /usr/include/bits/endian.h exists in filesystem
glibc: /usr/include/bits/environments.h exists in filesystem
glibc: /usr/include/bits/errno.h exists in filesystem
glibc: /usr/include/bits/error.h exists in filesystem
glibc: /usr/include/bits/fcntl.h exists in filesystem
glibc: /usr/include/bits/fcntl2.h exists in filesystem
glibc: /usr/include/bits/fenv.h exists in filesystem
glibc: /usr/include/bits/fenvinline.h exists in filesystem
glibc: /usr/include/bits/huge_val.h exists in filesystem
glibc: /usr/include/bits/huge_valf.h exists in filesystem
glibc: /usr/include/bits/huge_vall.h exists in filesystem
glibc: /usr/include/bits/in.h exists in filesystem
glibc: /usr/include/bits/inf.h exists in filesystem
glibc: /usr/include/bits/initspin.h exists in filesystem
glibc: /usr/include/bits/ioctl-types.h exists in filesystem
glibc: /usr/include/bits/ioctls.h exists in filesystem
glibc: /usr/include/bits/ipc.h exists in filesystem
glibc: /usr/include/bits/ipctypes.h exists in filesystem
glibc: /usr/include/bits/libc-lock.h exists in filesystem
glibc: /usr/include/bits/libio-ldbl.h exists in filesystem
glibc: /usr/include/bits/link.h exists in filesystem
glibc: /usr/include/bits/local_lim.h exists in filesystem
glibc: /usr/include/bits/locale.h exists in filesystem
glibc: /usr/include/bits/mathcalls.h exists in filesystem
glibc: /usr/include/bits/mathdef.h exists in filesystem
glibc: /usr/include/bits/mathinline.h exists in filesystem
glibc: /usr/include/bits/mman.h exists in filesystem
glibc: /usr/include/bits/monetary-ldbl.h exists in filesystem
glibc: /usr/include/bits/mqueue.h exists in filesystem
glibc: /usr/include/bits/mqueue2.h exists in filesystem
glibc: /usr/include/bits/msq.h exists in filesystem
glibc: /usr/include/bits/nan.h exists in filesystem
glibc: /usr/include/bits/netdb.h exists in filesystem
glibc: /usr/include/bits/poll.h exists in filesystem
glibc: /usr/include/bits/posix1_lim.h exists in filesystem
glibc: /usr/include/bits/posix2_lim.h exists in filesystem
glibc: /usr/include/bits/posix_opt.h exists in filesystem
glibc: /usr/include/bits/printf-ldbl.h exists in filesystem
glibc: /usr/include/bits/pthreadtypes.h exists in filesystem
glibc: /usr/include/bits/resource.h exists in filesystem
glibc: /usr/include/bits/sched.h exists in filesystem
glibc: /usr/include/bits/select.h exists in filesystem
glibc: /usr/include/bits/sem.h exists in filesystem
glibc: /usr/include/bits/semaphore.h exists in filesystem
glibc: /usr/include/bits/setjmp.h exists in filesystem
ncurses: /bin/tput exists in filesystem
ncurses: /lib/libncursesw.so.5 exists in filesystem
ncurses: /usr/bin/captoinfo exists in filesystem
ncurses: /usr/bin/clear exists in filesystem
ncurses: /usr/bin/infocmp exists in filesystem
ncurses: /usr/bin/infotocap exists in filesystem
ncurses: /usr/bin/ncursesw5-config exists in filesystem
ncurses: /usr/bin/reset exists in filesystem
ncurses: /usr/bin/tic exists in filesystem
ncurses: /usr/bin/toe exists in filesystem
ncurses: /usr/bin/tset exists in filesystem
ncurses: /usr/include/curses.h exists in filesystem
ncurses: /usr/include/cursesapp.h exists in filesystem
ncurses: /usr/include/cursesf.h exists in filesystem
ncurses: /usr/include/cursesm.h exists in filesystem
ncurses: /usr/include/cursesp.h exists in filesystem
ncurses: /usr/include/cursesw.h exists in filesystem
ncurses: /usr/include/cursslk.h exists in filesystem
ncurses: /usr/include/eti.h exists in filesystem
ncurses: /usr/include/etip.h exists in filesystem
ncurses: /usr/include/form.h exists in filesystem
ncurses: /usr/include/menu.h exists in filesystem
ncurses: /usr/include/ncurses.h exists in filesystem
ncurses: /usr/include/ncurses_dll.h exists in filesystem
ncurses: /usr/include/panel.h exists in filesystem
ncurses: /usr/include/term.h exists in filesystem
ncurses: /usr/include/termcap.h exists in filesystem
ncurses: /usr/include/unctrl.h exists in filesystem
ncurses: /usr/lib/libcurses.a exists in filesystem
ncurses: /usr/lib/libcurses.so exists in filesystem
ncurses: /usr/lib/libcursesw.so exists in filesystem
ncurses: /usr/lib/libform.a exists in filesystem
ncurses: /usr/lib/libform.so exists in filesystem
ncurses: /usr/lib/libformw.a exists in filesystem
ncurses: /usr/lib/libformw.so exists in filesystem
ncurses: /usr/lib/libformw.so.5 exists in filesystem
ncurses: /usr/lib/libmenu.a exists in filesystem
i can't post the everything since it's too long (about 6000 lines), the forum is not letting me to post everything

[solved] How is one supposed to upgrade pacman?

Just upgraded pacman to v4 and got a problem with libarchive.so.12 missing. So tried the other way round (upgraded libarchive first) but then pacman complained about libarchive.so.2. So no matter what I did, I ended up with a broken pacman...
What is the correct way to upgrade pacman?
Regards,
BTJ
Last edited by bjorntj (2012-01-20 08:57:38)

bjorntj wrote:Just upgraded pacman to v4 and got a problem with libarchive.so.12 missing. So tried the other way round (upgraded libarchive first) but then pacman complained about libarchive.so.2. So no matter what I did, I ended up with a broken pacman...
What is the correct way to upgrade pacman?
I made the stupid move to pacman -Sd pacman.
Now i have a broken pacman too. I saw the solution how to upgrade pacman properly but now it's too late.
I tried downgrade pacman to 3.5 but i have this output every time:
sudo pacman -U /var/cache/pacman/pkg/pacman-3.5.4-4-i686.pkg.tar.gz
pacman: error while loading shared libraries: libarchive.so.12: cannot open shared object file: No such file or directory
Please help . How did you managed to recover pacman and then upgrade it again ?

[Solved]Upgrade pacman 4.1 - no usable package repositories configured

Similar Messages

Maybe you are looking for