While trying to reproduce this, I was able to observe it once, but then
unable to reproduce further.

The only explanation I can think of right now is some edge case related to
upgrading the package.  I was unable to reproduce that either, however.

In any case, the working version of this package (1.2.0-2) should be
*unfrozen* for wheezy, because shipping 1.2.0-1 with wheezy would mean
shipping a broken package that cannot be installed unattended without
additional measures.


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to