Tons of tput: default: unknown terminal "unknown" (Vagrant)

[reubenavery]

After applying bashrc on a Vagrant Ubuntu box, the provisioning now spits out a huge number of "tput: default: unknown terminal "unknown"" messages.

==> default: Running provisioner: puppet...
==> default: Running Puppet with nodes.pp...
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: we were not given a process to search for as an argument, and no config files are present. failing
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:

~/.profile: executed by Bourne-compatible login shells.

==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"
==> default: tput:
==> default: unknown terminal "unknown"

[wolfspyre]

I think e5ebfe6 should address this. Can you pull and check?