Quoting Martin T (m4rtn...@gmail.com): > On 8/27/15, David Wright <deb...@lionunicorn.co.uk> wrote:
> > So what depends on python2.6 that won't be satisfied with 2.7? > > > > My wheezy shows libdb5.1:i386 5.1.29-5 and jessie has libdb5.3:i386 > > 5.3.28-9 > > (assuming they're related). Neither has python2.6. > How would you check the packages which depend on python2.6 that won't > be satisfied with python2.7? Simply compare the outputs of "apt-cache > rdepends python2.6" and "apt-cache rdepends python2.7"? I would use aptitude why python2.6 to see why it's still there. If the list is "boring", lots of A(utomatic) items and/or Suggests, then you don't need it. The way that I would purge it is probably also to run aptitude (with no arguments): /^python2.6 n (as many times as required to highlight python2.6 itself) _ (to purge) See if you get a red response. If so (and you'll probably get its pythonXXX-minimal highlighted) ^u (to back out) Move to the offending package _ (to purge it) If that is happy (no red), navigate to python2.6 _ (to purge it again) and carry on like that. When you eventually press g you may see other packages listed that it can remove as they were automatically installed. If you don't like g's list, back out with q. q backs out of g, and ^u backs out of _ (^u may be needed multiple times). Cheers, David.