Introducing a Daily PPA for Juju

[Nicholas Skaggs]

Yea, I saw the latest package got named twice as it were. I'll have a 
look. It doesn't hurt anything, but the package should be

2.0-beta7~20160512~3966+0bd48e6f~16.04

On 05/12/2016 05:15 PM, Adam Stokes wrote:
> Nice but this version is a bit crazy:
>
> 2.0-beta7~20160512~3966~0bd48e6f-20160512+3966+0bd48e6f~16.04
>
> Maybe just drop -20160512+3966+0bd48e6f as it seems to be repetative
>
> On Thu, May 12, 2016 at 4:39 PM, Ryan Beisner 
> <ryan.beisner at canonical.com <mailto:ryan.beisner at canonical.com>> wrote:
>
>     Absolutely <3 this.
>
>     On Thu, May 12, 2016 at 3:36 PM, Nicholas Skaggs
>     <nicholas.skaggs at canonical.com
>     <mailto:nicholas.skaggs at canonical.com>> wrote:
>
>         Whether you want to track Juju development more closely, or
>         simply like living on the edge, there is a new ppa available
>         for you. Dubbed the Juju Daily ppa[1], it] contains the latest
>         blessed builds from CI testing. Installing this ppa and
>         upgrading regularly allows you to stay in sync with the
>         absolute latest version of Juju that passes our CI testing.
>         New packages are copied as soon as a blessed build is
>         complete. This can occur multiple times a day should every
>         build pass, or it may be several days between builds should
>         new revisions contain failures.
>
>
>         The Juju QA team don’t recommend running this ppa for
>         production or critical system usage, but we are happy to hear
>         about bugs[2] you may encounter while running these versions
>         of Juju. To add the ppa, you will need to add ppa:juju/daily
>         to your software sources.
>
>
>         sudo add-apt-repository ppa:juju/daily
>
>
>         Do be aware that adding this ppa will upgrade any version of
>         Juju you may have installed. Also note this ppa contains
>         builds without published streams, so you will need to generate
>         or acquire streams on your own. For most users, this means you
>         should pass --upload-tools during the bootstrap process.
>         However you may also pass the agent-metadata-url and
>         agent-stream as config options. See the ppa description and
>         simplestreams documentation for more details[3].
>
>
>         Finally, should you wish to revert to a stable version of
>         Juju, you can use the ppa-purge tool[4] to remove the daily
>         ppa and the installed version of Juju.
>
>
>         We hope this proves useful to you, feedback welcome!
>
>
>
>         Nicholas
>
>         1.
>
>         https://launchpad.net/~Juju/+archive/ubuntu/daily
>         <https://launchpad.net/%7EJuju/+archive/ubuntu/daily>
>            <https://launchpad.net/%7Ejuju/+archive/ubuntu/daily>
>
>         2.
>
>         https://bugs.launchpad.net/juju-core/+filebug
>
>         3.
>
>         https://github.com/juju/juju/blob/master/doc/simplestreams-metadata.txt
>
>         4.
>
>         http://askubuntu.com/a/310
>
>
>         -- 
>         Juju mailing list
>         Juju at lists.ubuntu.com <mailto:Juju at lists.ubuntu.com>
>         Modify settings or unsubscribe at:
>         https://lists.ubuntu.com/mailman/listinfo/juju
>
>
>
>     --
>     Juju mailing list
>     Juju at lists.ubuntu.com <mailto:Juju at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/juju
>
>