Turns out this is actually triggered by `set -v` itself (there was
another problem as well, but I can't reproduce it will enough for a
proper ticket after all.) Closing.
** Changed in: cram (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901372
Title:
cram3 crashes with "invalid literal for int"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cram/+bug/1901372/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
