On Fri, Jun 20, 2008 at 10:48:02AM +0000, Alan Mackenzie <[EMAIL PROTECTED]> was heard to say: > On Thu, Jun 19, 2008 at 08:47:35PM -0500, Mumia W.. wrote: > > I suspect that your attempt to upgrade python broke your system. If you > > are not an expert with Debian, it is best to stick with a single > > distribution (e.g. "stable") rather than to mix distributions (e.g. > > "oldstable"+"stable"). > > I was expecting that in using a package manager, it would simply do the > Right Thing, without me having to worry.
aptitude prior to 0.4 gets really confused (as do other apt-based package managers) if you try to mix distributions. You can do it, but you have to manually resolve any dependency problems that come up because the package manager doesn't know how. I think that 0.4 should be better, but I don't normally use it this way. > Again, I think the problem for > me is that the meaning of "stable" has changed from "sarge" to "etch". > Presumably this was a deliberate choice of the Debian team, on the > assumption that most people would be upgrading as early as possible > anyhow. Is there a symbolic link (or something similar) in the Debian > archive, something like "sarge" -> "oldstable", that I could use here in > place of "stable"? There is not a symbolic link from sarge to oldstable, because that would be a symlink loop. :-) Release status names, like "stable" and "testing", are symlinks to release names, like "sarge" and "etch"; they exist for the convenience of people who want to always have whatever is currently "stable" or "testing". If for some reason you really want to keep using sarge, you should change "stable" to "sarge" in sources.list. Personally, I'd recommend upgrading to etch unless you have a situation that prevents that (e.g., you have a low-powered computer that you know can't run etch). Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
