Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Refactor installation dependency chain #55
Conversation
|
Seems reasonable. |
|
Built and everything appears to be working as expected. |
mbruzek
reviewed
Sep 1, 2016
| @@ -3,26 +3,29 @@ set -e | ||
| HOME=/home/ubuntu | ||
| # Add tims awesome PPA for the 2.0 bleeding edge tooling | ||
| -sudo add-apt-repository -y ppa:tvansteenburgh/ppa |
|
This change seems reasonable to me. I encountered a problem with a downlevel version of amulet today in my tests of the etcd charm. I am hoping the pip version is more recent. |
|
+1 LGTM |
mbruzek
merged commit 38f6700
into
juju-solutions:master
Sep 1, 2016
This was referenced Sep 1, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
chuckbutler commentedSep 1, 2016
I conferred with @marcoceppi this morning about the charm-tools and
charm dependency chain and the future facing move to snap delivery.
We're currently pressed as we cant deliver software via snaps inside
docker unless we're running systemd amenities. Docker doesn't play well
with running an init, so we're at an impass. Here's the current
packaging notes:
latest stable release of charm-tools
delivery pipeline sorted
dependencies such as pyyaml. So a simple
pip installvspip install -Uwill suffice.This build was tested as a base for cwrbox and resolves the dependency
chain issues that surfaced on 8/30/2016