Why does --upload-tools now append a .1 build revision ?

[David Cheney]

This is a change in behaviour from yesterday. I thought that we were
getting rid of --dev altogether.

On 18/04/13 14:35, John Arbash Meinel wrote:
> On 2013-04-18 5:59, David Cheney wrote:
>> ubuntu at juju-hpgoctrl2-machine-0:~$ juju bootstrap -v
>> --upload-tools 2013/04/18 01:57:18 INFO environs/openstack: opening
>> environment "goscale2" 2013/04/18 01:57:22 INFO environs/tools:
>> built 1.9.15.1-precise-amd64 (2193kB) 2013/04/18 01:57:22 INFO
>> environs/tools: uploading 1.9.15.1-precise-amd64 2013/04/18
>> 01:57:22 INFO environs/openstack: bootstrapping environment 
>> "goscale2" 2013/04/18 01:57:32 INFO environs: reading tools with
>> major version 1 2013/04/18 01:57:32 INFO environs: filtering tools
>> by series: precise 2013/04/18 01:57:32 INFO environs: filtering
>> tools by version: 1.9.15.1 2013/04/18 01:57:32 WARNING
>> environs/openstack: ignoring constraints, using
>> default-instance-type flavor "standard.small" 2013/04/18 01:57:32
>> WARNING environs/openstack: forcing precise/amd64 tools for image
>> "68481" 2013/04/18 01:57:37 INFO environs/openstack: started
>> instance "1518355" ubuntu at juju-hpgoctrl2-machine-0:~$ grep 'const
>> version' src/*/*/*/* 
>> src/launchpad.net/juju-core/version/version.go:const version =
>> "1.9.15"
> 
> 
> I'm guessing so that it is always a --dev version.
> 
> John
> =:->
>