Launchpad really doesn't give you a way to pull the "latest" download or md5 hash. There's nothing wrong with using a "hard-coded" version of the release. It means the charm will always work even if upstream changes. Given they release about every 3-4 months it wouldn't be _too_ tedious to update every release, or not. For now, until a more clear release pattern emerges (and development settles) I would just hard-code "17213009a326a730a9de40b70ce93978" for the md5 hash of the tar.gz download from launchpad (https://launchpad.net/chive/1.1/1.1/+download/chive_1.1.tar.gz) So it would look something like this:
Launchpad really doesn't give you a way to pull the "latest" download or md5 hash. There's nothing wrong with using a "hard-coded" version of the release. It means the charm will always work even if upstream changes. Given they release about every 3-4 months it wouldn't be _too_ tedious to update every release, or not. For now, until a more clear release pattern emerges (and development settles) I would just hard-code "17213009a326a7 30a9de40b70ce93 978" for the md5 hash of the tar.gz download from launchpad (https:/ /launchpad. net/chive/ 1.1/1.1/ +download/ chive_1. 1.tar.gz) So it would look something like this:
chive_file= `ch_get_ file "https:/ /launchpad. net/chive/ 1.1/1.1/ +download/ chive_1. 1.tar.gz" "17213009a326a7 30a9de40b70ce93 978"`
I would be great if they updated their PPA, you could consider contacting the author and asking them to update it.