Re: Aptitude cannot upgrade libperl5.10
On Mon, Aug 30, 2010 at 00:17:19 +, T o n g wrote:
On Sun, 29 Aug 2010 22:11:21 +0200, Florian Kulzer wrote:
% aptitude show libperl5.10 | awk '/^Package/,/^Version/' Package:
libperl5.10
State: not installed
Automatically installed: no
Version: 5.10.1-14
. . .
$ apt-cache policy libperl5.10
libperl5.10:
Installed: 5.10.1-12
Candidate: 5.10.1-14
Version table:
5.10.1-14 0
360 http://cdn.debian.net testing/main Packages
50 http://cdn.debian.net unstable/main Packages
*** 5.10.1-12 0
100 /var/lib/dpkg/status
: : :
OK, now I think the problem is that my aptitude's status log is messed
up. . .
Indeed, there seems to be a problem with aptitude's databases. Please
check what dpkg itself thinks about libperl, i.e.
dpkg -l libperl\* | awk '/^[^D|+]/{print $1,$2,$3}'
$ dpkg -l libperl\* | awk '/^[^D|+]/{print $1,$2,$3}'
ii libperl5.10 5.10.1-12
un libperl5.8 none
So both dpkg and apt-get think libperl is installed, except aptitude.
Is there any way for me to rebuild my aptitude's databases?
AFAIK, aptitude updates its database automatically before it is runs
commands that change the status of any packages (also when it is started
in interactive mode). Aptitude has to do this because the user might
have made changes to the installation with dpkg or another package
manager since the last time aptitude was run. This has always worked for
me so far. I have no idea why this fails on your system; you might have
found a bug that only manifests itself under very special circumstances,
or there could be a more subtle corruption of aptitude's database. The
first thing I would do is check the root filesystem and the SMART
information of its hard disk.
--
Regards,|
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100911150050.ga7...@bavaria.univ-lyon1.fr
Aptitude cannot upgrade libperl5.10
Thanks for your reply, Florian. On Sun, 29 Aug 2010 11:55:49 +0200, Florian Kulzer wrote: The following packages have unmet dependencies: libperl5.10: Depends: perl-base (= 5.10.1-12) but 5.10.1-14 is to be installed. So the problem is that aptitude thinks it cannot upgrade libperl5.10. What is the output of: aptitude show libperl5.10 | awk '/^Package/,/^Version/' aptitude % aptitude show libperl5.10 | awk '/^Package/,/^Version/' Package: libperl5.10 State: not installed Automatically installed: no Version: 5.10.1-14 Automatically installed: no? Strange, but this is not the first time that I see automatically installed packages are considered something else by aptitude. If you'd like, I can start another thread discussing specifically about it. Ops, just realize that aptitude thinks my libperl5.10 is not installed, but it is: $ apt-cache policy libperl5.10 libperl5.10: Installed: 5.10.1-12 Candidate: 5.10.1-14 Version table: 5.10.1-14 0 360 http://cdn.debian.net testing/main Packages 50 http://cdn.debian.net unstable/main Packages *** 5.10.1-12 0 100 /var/lib/dpkg/status OK, now I think the problem is that my aptitude's status log is messed up. Could it be that I mix apt-get install and aptitude install, or something else? (I don't do install/upgrade very often, as you can see.) --simulate --show-deps install libperl5.10=5.10.1-14 Here it goes, a bit long: % aptitude --simulate --show-deps install libperl5.10=5.10.1-14 The following packages will be upgraded: libperl5.10 perl-base 2 packages upgraded, 0 newly installed, 0 to remove and 555 not upgraded. Need to get 1,066kB of archives. After unpacking 0B will be used. The following packages have unmet dependencies: perl: Depends: perl-base (= 5.10.1-12) but 5.10.1-14 is to be installed. open: 231; closed: 784; defer: 180; conflict: 354 oThe following actions will resolve these dependencies: Remove the following packages: 1) acroread 2) acroread-data 3) acroread-debian-files 4) acroread-escript 5) acroread-l10n-en 6) acroread-plugins 7) alsaplayer-common 8) alsaplayer-gtk 9) apt-file 10) aqualung 11) autoconf 12) automake 13) bsd-mailx 14) build-essential 15) checkgmail 16) checkinstall 17) clive 18) cmap-adobe-cns1 19) cmap-adobe-gb1 20) cups 21) cups-bsd 22) cups-driver-gutenprint 23) cups-pdf 24) ddclient 25) debhelper 26) defoma 27) deluge 28) deluge-gtk 29) deluge-torrent 30) dh-make-perl 31) docbook-xml 32) docbook-xsl 33) dpkg-dev 34) dpkg-repack 35) emacs 36) emacs23 37) eog 38) fai-client 39) fai-server 40) fetchyahoo 41) file-roller 42) flashplugin-nonfree 43) foomatic-db-engine 44) foomatic-db-gutenprint 45) foomatic-filters 46) gcolor2 47) gconf-editor 48) gecko-mediaplayer 49) gedit 50) geeqie 51) getlive 52) gftp-gtk 53) ghostscript 54) ghostscript-cups 55) ghostscript-x 56) gimp 57) git 58) git-core 59) git-email 60) git-gui 61) gitk 62) gksu 63) gnome-about 64) gnome-applets 65) gnome-control-center 66) gnome-core 67) gnome-icon-theme 68) gnome-keyring 69) gnome-menus 70) gnome-mplayer 71) gnome-panel 72) gnome-power-manager 73) gnome-session 74) gnome-session-bin 75)
Re: Aptitude cannot upgrade libperl5.10
On Sun, Aug 29, 2010 at 18:26:44 +, T o n g wrote:
On Sun, 29 Aug 2010 11:55:49 +0200, Florian Kulzer wrote:
The following packages have unmet dependencies:
libperl5.10: Depends: perl-base (= 5.10.1-12) but 5.10.1-14 is to
be
installed.
So the problem is that aptitude thinks it cannot upgrade libperl5.10.
What is the output of:
aptitude show libperl5.10 | awk '/^Package/,/^Version/' aptitude
% aptitude show libperl5.10 | awk '/^Package/,/^Version/'
Package: libperl5.10
State: not installed
Automatically installed: no
Version: 5.10.1-14
Automatically installed: no? Strange, but this is not the first time
that I see automatically installed packages are considered something else
by aptitude. If you'd like, I can start another thread discussing
specifically about it.
I would say that is not necessary; the overall topic of this thread is
package management, so we stay within its scope and just start a more
specific sub-thread. It is good that you changed the subject, to make it
more likely to attract Daniel Burrows (the author of aptitude, who does
seem to read this list).
Ops, just realize that aptitude thinks my libperl5.10 is not installed,
but it is:
$ apt-cache policy libperl5.10
libperl5.10:
Installed: 5.10.1-12
Candidate: 5.10.1-14
Version table:
5.10.1-14 0
360 http://cdn.debian.net testing/main Packages
50 http://cdn.debian.net unstable/main Packages
*** 5.10.1-12 0
100 /var/lib/dpkg/status
OK, now I think the problem is that my aptitude's status log is messed
up. Could it be that I mix apt-get install and aptitude install, or
something else? (I don't do install/upgrade very often, as you can see.)
Indeed, there seems to be a problem with aptitude's databases. Please
check what dpkg itself thinks about libperl, i.e.
dpkg -l libperl\* | awk '/^[^D|+]/{print $1,$2,$3}'
I have in the past experimented with mixing apt-get and aptitude; I
never had any problems. There were (and maybe still are) some
differences with respect to handling of automatic installs and the
persistence of scheduled actions that one should be aware of, though.
In recent years I have only used aptitude in interactive mode (ncurses
interface), so I am hesitant to make any strong statements about
aptitude's behavior in command-line mode, and even more hesitant about
apt-get.
My personal philosophy is that I try to keep all packages on my Sid
systems up-to-date, because then I will only have normal Sid problems,
which are shared by many people, so they will discovered and solved
quickly. With a partially-outdated Sid system, there might be additional
issues (unforeseen by the package managers, who assume their packages
are installed on a current system), and you are more or less alone with
them.
--simulate --show-deps install libperl5.10=5.10.1-14
[ snip: Again, a nonsense proposal instead of simply upgrading all the
perl packages. This is not surprising, we have to figure out why
aptitude does not see libperl5.10 as installed. ]
--
Regards,|
Florian |
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100829201120.ga10...@isar.localhost
Re: Aptitude cannot upgrade libperl5.10
On Sun, 29 Aug 2010 22:11:21 +0200, Florian Kulzer wrote:
% aptitude show libperl5.10 | awk '/^Package/,/^Version/' Package:
libperl5.10
State: not installed
Automatically installed: no
Version: 5.10.1-14
. . .
$ apt-cache policy libperl5.10
libperl5.10:
Installed: 5.10.1-12
Candidate: 5.10.1-14
Version table:
5.10.1-14 0
360 http://cdn.debian.net testing/main Packages
50 http://cdn.debian.net unstable/main Packages
*** 5.10.1-12 0
100 /var/lib/dpkg/status
: : :
OK, now I think the problem is that my aptitude's status log is messed
up. . .
Indeed, there seems to be a problem with aptitude's databases. Please
check what dpkg itself thinks about libperl, i.e.
dpkg -l libperl\* | awk '/^[^D|+]/{print $1,$2,$3}'
$ dpkg -l libperl\* | awk '/^[^D|+]/{print $1,$2,$3}'
ii libperl5.10 5.10.1-12
un libperl5.8 none
So both dpkg and apt-get think libperl is installed, except aptitude.
Is there any way for me to rebuild my aptitude's databases?
--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/i5etaf$m8...@dough.gmane.org
