Comment 4 for bug 1205466

Please don't change that.

The system is acting correctly by caching the charm with the given URL and revision. If I destroy a service and re-create, and suddenly that service is different, although the charm URL and revision did not change, *that's* surprising and a bug.

In other words, do not use a single revision identifier for different content. That's wrong in Bazaar, in deb packaging, and it's wrong in juju as well. If you do it, bad things will happen.

Note that deploy has an --upgrade identifier precisely so you can easily bump the revision number on quick local iterations of a charm.