~benji/charms/precise/juju-gui/make-etags-ignore-inode : changes

~benji/charms/precise/juju-gui/make-etags-ignore-inode » Changes to server-requirements.pip from revision 150

From Revision 150

Rev		Summary	Authors	Date	Diff	Files
127		Fix base Python dependencies. Fix base Python dependencies. The install hook imported charmhelpers before installing python-yaml, and charmhelpers imports from yaml. This very old bug has been hidden by the fact that python-yaml is automatically installed in ec2/lxc instances, but showed itself when using the manual provider. Copy/pasting and integrating the QA from my last branch, a double check can help before the release. QA: - Bootstrap a Juju environment with --debug. - Deploy and expose the GUI (make deploy). - Check juju debug-log (or less ~/.juju/local/log/unit-juju-gui-0.log if you used lxc): you should see the following message at the beginning of the install hook log: "Installing base Python dependencies: python-apt, python-launchpadlib, python-tempita, python-yaml." - Wait for the GUI to be ready/started. - Deploy this bundle: http://pastebin.ubuntu.com/6411548/ - Check everything is ok, xy annotations work ( the services are vertically aligned), wordpress has customized constraints, mysql customized options and two units. - No try to deploy the same bundle again, you will see a "services already there" kind of error. R=gary.poster CC= https://codereview.appspot.com/26190043	Francesco Banconi	10 years ago
126		Update requirements and improve their handling. Update requirements and improve their handling. Updated the juju-deployer and jujucleint dependencies to the latest versions, which include our recent fixes. This way we avoid using our own forks of the projects. Updated the code that installs the builtin server dependencies: now a pip requirement file is used, and the test requirement file includes the former. The overall dependency infrastructure should now be less confusing. Also added documentation about how to update the builtin server requirements. Removed the no longer required --upload-tools from the functional tests runner. The deployer functional tests now also use bundles including numunits > 1 and constraints. QA: - Bootstrap a Juju environment. - Deploy and expose the GUI (make deploy). - Wait for the GUI to be ready/started. - Deploy this bundle: http://pastebin.ubuntu.com/6411548/ - Check everything is ok, xy annotations work ( the services are vertically aligned), wordpress has customized constraints, mysql customized options and two units. - No try to deploy the same bundle again, you will see a "services already there" kind of error. R=gary.poster CC= https://codereview.appspot.com/26130043	Francesco Banconi	10 years ago