upgraded to apt 1.4~beta3 and the problem's "gone away". so, this bug can be closed.... but can i suggest (i don't know how to do it myself, guillem) reassigning it to apt... and *then* closing it, so that there's a proper record associated with the right program, in case someone also encounters this same bug over the next few weeks/months?
l.
