Hi,

this bugs seems to be gone in the "newest" upstream version 1.51 of
jumpnbump which I plan to package for debian unstable. In any case this is
a bug of jumpnbump and not of jumpnbump-levels as you already said.

Greetings,
Kilian.



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

Reply via email to