On 23 March 2016 at 15:06, David Ames <david.a...@canonical.com> wrote: > On 03/21/2016 06:54 PM, Stuart Bishop wrote: >> >> On 22 March 2016 at 11:42, Rick Harding <rick.hard...@canonical.com> >> wrote: >>> >>> I believe that went out and is ok Stuart. The charmstore update is >>> deployed >>> and when you upload a multi-series charm to the charmstore it creates >>> separate charms that work on older clients. If you hit issues with that >>> please let me know. >> >> >> Its only fixed for charms served from the charm store. CI systems and >> such test branches, for example ensuring tests pass before uploading a >> release to the charm store. I suspect this is exactly what Ryan needs >> to do and why I mentioned the open bug. Unless 1.25 is updated to >> handle the different data types, CI systems will need to work around >> the issue by either roundtripping through the charm store (in a >> personal namespace to avoid mid air collisions) or munging >> metadata.yaml.
ISTM that munging metadata.yaml could be a reasonable way to go here. It's not too hard. Here's a program you could use: http://play.golang.org/p/xl7yArJhtT -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju