need pyasn1* python libs during maas deploy
Bug #1335473 reported by
David Britton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Juju Charms Collection) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Not sure how this was missed. the target I tested with (lxc) must have had something that the maas images don't:
unit-apache2-0: 2014-06-28 10:31:54 INFO reverseproxy-
unit-apache2-0: 2014-06-28 10:31:54 INFO reverseproxy-
unit-apache2-0: 2014-06-28 10:31:54 INFO reverseproxy-
Anyway, easy enough to fix. Branch coming shortly.
Related branches
lp:~dpb/charms/precise/apache2/1335473-pyasn1-libs
- Marco Ceppi (community): Approve
-
Diff: 20 lines (+7/-3)1 file modifiedhooks/hooks.py (+7/-3)
Changed in apache2 (Juju Charms Collection): | |
assignee: | nobody → David Britton (davidpbritton) |
Changed in apache2 (Juju Charms Collection): | |
assignee: | David Britton (davidpbritton) → nobody |
status: | In Progress → Incomplete |
status: | Incomplete → Won't Fix |
To post a comment you must log in.
Note I have an open MP against trusty to which I added this same fix:
https:/ /code.launchpad .net/~davidpbri tton/charms/ trusty/ apache2/ avoid-regen- cert/+merge/ 223990
Even though this won't be needed as trusty has the python- pyasn1- modules package, I felt it best to include it to keep the branches in sync.