You are not logged in.
[root@arch pkg]# pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (4): glibc-2.10.1-3 zlib-1.2.3.3-3 binutils-2.19.1-5 db-4.7.25.4-1
Total Download Size: 18.93 MB
Total Installed Size: 51.56 MB
Proceed with installation? [Y/n] ^C
Interrupt signal received
[root@arch pkg]# pacman -Q zlib
zlib 1.2.3.3-3
[root@arch pkg]# pacman -Q binutils
binutils 2.19.1-5
[root@arch pkg]# pacman -Q db
db 4.7.25.4-1
[root@arch pkg]#
You can see every pkg it asked to download are not in newer version.
Why?
Offline
Have you tried using pacman -Syu?
Offline
tried. same.
Offline
Maybe refreshing the package list is necessary? Have you tried doing a pacman -Syy and then see what happens with pacman -Su?
Offline
tried Syy, again, it's the same..
Offline
This is odd. Did you try removing those packages and then reinstalling them?
If that doesn't work, try removing them again, clean the uninstalled cache pkgs, and then reinstall.
Offline
This works. I tried remove db first, then install it. Then things go right.
Offline
I can vouch for Pacman doing weird things to lately...I try to grab webkitkde from AUR and look at this:
Note the KDE depends--which I already have installed as a result of running a normal KDE install...that Yaourt/pacman wants me top install/upgrade.
It says package KDEBase not found...which is funny since I have it installed on my box.
==> webkitkde-svn dependencies:
- kdebase (package found)
- cmake (already installed)
- automoc4 (already installed)
- subversion (already installed)
==> Continue the building of webkitkde-svn ? [Y/n]
==> ----------------------------------------------
==>y
==> Building and installing package
mkdir: cannot create directory `/var/abs': Permission denied
==> WARNING: Unable to write in /var/abs/local/yaourtbuild/webkitkde-svn directory. Using /tmp directory
==> Determining latest svn revision...
-> Version found: 1010646
==> Making package: webkitkde-svn 1010646-1 x86_64 (Fri Aug 14 21:08:29 CDT 2009)
==> Checking Runtime Dependencies...
==> Installing missing dependencies...
Password:
kdebase package not found, searching for group...
:: group kdebase (including ignored packages):
kdebase-dolphin kdebase-kappfinder kdebase-kdepasswd kdebase-kdialog
kdebase-keditbookmarks kdebase-kfind kdebase-kinfocenter kdebase-konqueror
kdebase-konsole kdebase-kwrite kdebase-nsplugins kdebase-plasma
:: Install whole content? [Y/n] y
warning: kdebase-dolphin-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kappfinder-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kdepasswd-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kdialog-4.3.0-1 is up to date -- reinstalling
warning: kdebase-keditbookmarks-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kfind-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kinfocenter-4.3.0-1 is up to date -- reinstalling
warning: kdebase-konqueror-4.3.0-1 is up to date -- reinstalling
warning: kdebase-konsole-4.3.0-1 is up to date -- reinstalling
warning: kdebase-kwrite-4.3.0-1 is up to date -- reinstalling
warning: kdebase-nsplugins-4.3.0-1 is up to date -- reinstalling
warning: kdebase-plasma-4.3.0-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (12): kdebase-dolphin-4.3.0-1 kdebase-kappfinder-4.3.0-1 kdebase-kdepasswd-4.3.0-1
kdebase-kdialog-4.3.0-1 kdebase-keditbookmarks-4.3.0-1 kdebase-kfind-4.3.0-1
kdebase-kinfocenter-4.3.0-1 kdebase-nsplugins-4.3.0-1 kdebase-konqueror-4.3.0-1
kdebase-konsole-4.3.0-1 kdebase-kwrite-4.3.0-1 kdebase-plasma-4.3.0-1
Total Download Size: 0.00 MB
Total Installed Size: 17.59 MB
Proceed with installation? [Y/n] y
checking package integrity...
(12/12) checking for file conflicts [#######################################] 100%
( 1/12) upgrading kdebase-dolphin [#######################################] 100%
( 2/12) upgrading kdebase-kappfinder [#######################################] 100%
( 3/12) upgrading kdebase-kdepasswd [#######################################] 100%
( 4/12) upgrading kdebase-kdialog [#######################################] 100%
( 5/12) upgrading kdebase-keditbookmarks [#######################################] 100%
( 6/12) upgrading kdebase-kfind [#######################################] 100%
( 7/12) upgrading kdebase-kinfocenter [#######################################] 100%
( 8/12) upgrading kdebase-nsplugins [#######################################] 100%
( 9/12) upgrading kdebase-konqueror [#######################################] 100%
(10/12) upgrading kdebase-konsole [#######################################] 100%
(11/12) upgrading kdebase-kwrite [#######################################] 100%
(12/12) upgrading kdebase-plasma [#######################################] 100%
==> Missing Dependencies:
-> kdebase
==> Checking Buildtime Dependencies...
==> ERROR: Could not resolve all dependencies.Last edited by Skripka (2009-08-15 02:11:03)
Offline
@Skripka: Hmmm.... that seems makepkg does not work when a package depends on a group. Please file a bug report.
Offline
@Skripka: Hmmm.... that seems makepkg does not work when a package depends on a group. Please file a bug report.
I did some playing, and got past the depend checks--by fixing the PKGBUILD to take into account the name change for meta-packages with split KDE (D'oh, shoulda though about that for a PKGBUILD last updated in April, what can I say-not enough vino tonight) i.e. depends=("kdebase") should cause problems because there isn't a "kdebase" packages for 4.3, but rather a "kde-meta-kdebase" meta-package. It still won't compile, but it doesn't look like there's a bug with Pacman/Yaourt on this one from here.
Last edited by Skripka (2009-08-15 03:16:15)
Offline
Skripka : Nice offtopic, this has absolutely nothing to do with the original problem.
fluke : I have seen similar problems in the past, where a user had a corrupted local database with several entries (with different versions) for the same package.
in your case, you could have had more than one entry for glibc zlib binutils db
you could have checked that by doing ls /var/lib/pacman/local/glibc*
and you can actually reproduce the bug by doing : cp -r /var/lib/pacman/local/glibc-2.10.1-3 /var/lib/pacman/local/glibc-2.10.1-2
then pacman -Su / pacman -Q glibc
But don't ask me how it happened, I have no idea at all. pacman always remove the old entry before installing the new one. And if removing the old one failed, pacman should fail as well. Or maybe you manipulated the local db yourself, eg by restoring an old backup or things like that.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline