CI tests are installing Juju on the CI machine ...

[Curtis Hovey-Canonical]

On Fri, Aug 1, 2014 at 4:03 PM, Martin Packman
<martin.packman at canonical.com> wrote:
> On 01/08/2014, David Cheney <david.cheney at canonical.com> wrote:
...
>> /usr/bin/juju (juju) in auto mode.
>> Setting up rsyslog-gnutls (5.8.6-1ubuntu8.6) ...
>>
>> ^ it's leaking in from a dependency, this is risky to say the least.
>
> This is because of our Makefile, which includes juju-local[1] in the
> packages installed as part of the 'install-dependencies' target. I'm
> very tempted to just change it to be the juju-local dependencies on
> minus juju-core itself, but that put the onus on us for keeping that
> in sync.

Users were irate when juju wouldn't tell them straight up that
juju-local is required to guarantee it works locally. Developers are a
different matter. I the need to change deps. I test with fake
packages. Attached is my fake juju-local. It does nothing but tell
juju the juju-local is installed. Anyone is welcome to install it for
development...but it wont make juju work, you need to do that
yourself.



-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
-------------- next part --------------
A non-text attachment was scrubbed...
Name: juju-local_1.99.0_amd64.deb
Type: application/x-debian-package
Size: 2270 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140801/ba473be7/attachment.deb>