Re: what can be done with broken packages
Roland Wegmann wrote:
Hi
I installed aptitude and therefore find out that I have some broken
packages on my debian powerpc box (testing).
cpp-2.95, perl, perl-base, libstdc++2.10-glibc2.10
What does a broken package mean? And how can I made a package 'unbroken'?
Kind regards, Roland
rowe_gnu@gmx.net
I doubt that they are really 'broken'. Unless you have been playing
around with 'dpkg --force-depends', the frontends, eg apt and dselect
and aptitude, are well designed to ensure that all the packages never
get into a 'broken' state so the current state of your installation is
perfectly fine. More likely, aptitude is trying to upgrade/install
something that would result in packages becoming 'broken' because it
thinks that you would want it to this. Obviously aptitude is delusional
since you would never want packages to be broken. You have several
options:
a) Remove all the 'broken' packages. Since perl and cpp-2.95 are
fairly important packages this is probably a bad idea.
b) Manually resolve the dependencies. Go into the packages and
select the dependencies for install by hitting '+' over them or if this
isn't possible hold the packages at a non-broken version by '='ing it.
c) If you aren't installing new packages, the easiest solution would
probably be to try to make what aptitude wants to do consistent with
what apt-get dist-upgrade wants to do.
Reply to: