Marc Wilson wrote:
But Friday night, I did an "apt-get update" then an "apt-get -d upgrade", which *did* download 116 packages for upgrade, and 411 not upgraded -- 90 MB in just over 6 hours. Saturday morning, I did an "apt-get upgrade" to complete the upgrade, and it completed.On Sun, Aug 24, 2003 at 11:38:06AM -0400, David Crane wrote:12 packages upgraded, 20 newly installed, 65 to remove and 387 not upgraded.Well, it looks like your box is significantly behind in updates. It thinks there are 387 packages available for upgrade, but you're not installing any of them. Quite a few of those have no doubt gone through the type of transition described elsewhere in this thread. I suspect that the dependency solution apt came up with is the best of a bad situation.
So I doubt that I am significantly behind in updates.I could be missing something, and probably am. I assumed that those 411 packages were up-to-date. Does a debian that is significantly behind (I started with 3.0r1 CD-ROMs) need multiple rounds of "apt-get upgrade" to catch up? Now, "apt-get upgrade" says:
237 packages upgraded, 0 newly installed, 0 to remove and 162 not upgraded. I am unsure what I should be moving toward:(1) Go back to the "stable" distribution, and find backports at www.apt-get.org?
(2) Try to install individual packages from "testing", instead of full upgrades?
(3) Regularly do full upgrades from "testing" (I did, or tried, one 36 hours ago)?
Thanks, David Crane