Comment 1 for bug 1789447

The issue here is that we now run "git describe --dirty" to pick up the sha of the latest commit and include that in a version file in the charm archive. This is reported in juju status.

However, it seems git describe can sometimes fail with error code 128 if it can't find any suitable tags. Using --always should fix this.

Note that it is just noise in that if there's an error running git describe, the charm deploy still goes ahead.