I've attempted to see if I could understand how this could happen, and I 
can't.

python-minimal ships the /usr/bin/python symlink.  Once python2.x is unpacked 
(I checked this) then /usr/bin/python2.x is available.  Since the version of 
python-minimal shown in the bug being unpacked depends on python2.6-minimal it 
should (not shown in the log) have been unpacked already and so 
/usr/bin/python2.6 should have been available.

I've run through this several different ways for Squeeze and Wheezy and don't 
see a failure mechanism based on an issue in this package.  

I'd reassing it, but I'm not sure where.  If python2.6-minimal wasn't unpacked 
yet, that would explain it, but given the depends relationship, I don't think 
that should happen.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to