I got the same issue upgrading because a trigger was activated while upgrading python2.6/python2.6-minimal; the python2.6 updates were moving shutil across packages.
python2.6 correctly depends on python2.6-minimal (= ${binary:Version}), yet python2.6 was unpacked before python2.6-minimal.
I wonder if this is an aptitude bug or some dep loop somewhere, but I couldn't find the latter.
Are you upgrading with aptitude?
I got the same issue upgrading because a trigger was activated while upgrading python2. 6/python2. 6-minimal; the python2.6 updates were moving shutil across packages.
python2.6 correctly depends on python2.6-minimal (= ${binary:Version}), yet python2.6 was unpacked before python2.6-minimal.
I wonder if this is an aptitude bug or some dep loop somewhere, but I couldn't find the latter.