[Bug 1182905] Re: charm-tools installs juju-0.7

[Marco Ceppi]

** Description changed:

  This is what happened to me:
  
-  * Configured environments.yaml for AWS.
-  * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo!
-  * While doing this I decided to install charm-tools
-  * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml
+  * Configured environments.yaml for AWS.
+  * I bootstrapped Juju, deployed wordpress and mysql and related them. I exposed wordpress and hit it in the browser. It worked. Woo!
+  * While doing this I decided to install charm-tools
+  * Now when I use Juju it errors requiring me to configure additional parts of environments.yaml
  
  Now, at first it only required me to configure a default-series for each
  provider, which is a no-brainer, but then it asked for maas-oauth
  config.
  
  This completely stopped me in my tracks. I don't care about the other
  providers as I have already got my AWS provider configured and up and
  running, and it put Juju in a position where it stopped working for me
  due to the missing configuration.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: charm-tools 0.3+151-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
  Uname: Linux 3.9.0-2-generic i686
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: i386
  Date: Wed May 22 06:49:59 2013
  InstallationDate: Installed on 2013-05-05 (17 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130504)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: charm-tools
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ [Impact]
+ 
+  * Users who install juju-core, then install charm-tools will have their installations broken in precise
+  * This fix decouples juju from charm-tools as a Recommended package to a Suggested package. This also makes juju-core package a satisfactory Suggestion in addition to juju
+ 
+ [Test Case]
+ 
+  * On precise, install juju-core and juju-local using the preferred installation method, from cloud-tools pocket archive.
+  * Run `juju init` to create environments.yaml
+  * Switch to local environment, `juju switch local`
+  * Verify version of juju installed, `juju version`
+  * Bootstrap with `sudo juju bootstrap`
+  * Deploy a charm, `juju deploy ubuntu`
+  * Install charm-tools package from precise archives
+  * Run `juju version`, command should fail.
+  * Run `juju --version`, command should succeed with a verion < 1.0.0
+  * Attempt to connect to environment with `juju status`, should fail
+ 
+ [Regression Potential]
+ 
+  * This simply changes the the control file to lower priority of
+ "Recommended" packages.
+ 
+ [Other Info]
+  
+  * This has been patched and updated in Saucy and Trusty as of version 1.0.0 of charm-tools. However, 1.0.0 breaks backwards compatibility with 0.3 packaging wise. charm-helper-sh and charm-helper-python are no longer supported and subsequently dropped from 1.0.0 version of charm-tools and it's packaging. Otherwise I likely would have requested a backport of 1.0.0 to precise.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1182905

Title:
  charm-tools installs juju-0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1182905/+subscriptions