[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Woody: problems upgrading lately?



I've been doing apt-get update's for about a week now, on three
different Debian systems which are all more-or-less recent "testing"
systems, and none of them will let me do an "apt-get dist-upgrade".  I
keep getting some packages listed, then this error:

  Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I have no held packages on my system, though (I used --ignore-hold and
it made no difference).

I've gone through and tried to "fix" these problems by removing unused
and older packages; often this changes the packages that are named in
the error, but then another package gives an error.  I have to believe
that there's something a bit more fundamentally wrong here, but I don't
know how to figure it out :(

For example, on one of my systems:

  # apt-get -s --ignore-hold dist-upgrade
  Reading Package Lists... Done
  Building Dependency Tree... Done
  Calculating Upgrade... Failed
  Sorry, but the following packages have unmet dependencies:
    libgal4:E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

  # dlocate -l libgal4
  ii  libgal4        0.5-7          G App Libs (run time library)

  # apt-get -s install libgal4
  Reading Package Lists... Done
  Building Dependency Tree... Done
  Sorry, libgal4 is already the newest version.
  0 packages upgraded, 0 newly installed, 0 to remove and 220  not upgraded.

Before this it complained about libncurses4, blt4.0 vs. blt8.0, etc.

Anyone have any ideas on what's going on here, or ways to investigate
further?

Thanks...

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <pausmith@nortelnetworks.com> HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.



Reply to: