installing mojo upgrades juju-deployer from 0.6.4 to 0.9.2, but still depends on 0.6.4 - The 'juju-deployer' distribution was not found and is required by mojo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Fix Released
|
High
|
Tim Kuhlman | ||
juju-deployer |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Installing mojo from mojo-maintainers ppa ends up upgrading juju-deployer on Trusty. But package dependencies still point to 0.6.4:
=======
$ sudo apt-get install mojo
sudo: unable to resolve host oil-ci-2-bastion
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
juju-deployer python3-
The following NEW packages will be installed:
mojo python3-
The following packages will be upgraded:
juju-deployer
1 upgraded, 2 newly installed, 0 to remove and 60 not upgraded.
Need to get 0 B/146 kB of archives.
After this operation, 7,168 B disk space will be freed.
Do you want to continue? [Y/n] y
Selecting previously unselected package python3-
(Reading database ... 57632 files and directories currently installed.)
Preparing to unpack .../python3-
Unpacking python3-
dpkg: error processing archive /var/cache/
trying to overwrite '/usr/bin/
Preparing to unpack .../juju-
Unpacking juju-deployer (0.9.2~
Selecting previously unselected package mojo.
Preparing to unpack .../archives/
Unpacking mojo (0.3.2-10) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ dpkg -l|grep juju
ii juju 1.25.8-
ii juju-core 1.25.8-
iU juju-deployer 0.9.2~bzr203~
ii juju-local 1.25.6-
ii juju-mongodb 2.4.9-0ubuntu3 amd64 MongoDB object/
ii python-jujuclient 0.53.3+
ii python3-jujuclient 0.53.3+
$ sudo apt-get install -f
sudo: unable to resolve host oil-ci-2-bastion
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
python3-
The following NEW packages will be installed:
python3-
0 upgraded, 1 newly installed, 0 to remove and 60 not upgraded.
2 not fully installed or removed.
Need to get 0 B/49.0 kB of archives.
After this operation, 293 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 57646 files and directories currently installed.)
Preparing to unpack .../python3-
Unpacking python3-
Setting up python3-
Setting up juju-deployer (0.9.2~
Setting up mojo (0.3.2-10) ...
sudo: unable to resolve host oil-ci-2-bastion
sudo: unable to resolve host oil-ci-2-bastion
If you want non-root user to run mojo (e.g.: jenkins), review below file and install it with:
sudo install -o root -g root -m 0440 /usr/share/
sudo usermod -aG mojo jenkins
=======
Also, note that there are installation errors which I am able to resolve with apt-get install -f and I had also hit bug 1643878; it seems like those 2 could be related. In any case, the real issue is this:
=======
$ apt-cache showpkg mojo
Package: mojo
Versions:
0.3.2-10 (/var/lib/
Description Language:
Description Language: en
Reverse Depends:
Dependencies:
0.3.2-10 - python (2 2.7) python (3 2.8) python:any (2 2.7.1-0ubuntu2) python-apt (2 0.8.3) python-jujuclient (2 0.0.7) juju-deployer (2 0.6.4) python-codetree (4 0.1.0) lxc (2 1.0.0) python-cinderclient (2 1.0.0) python-bzrlib (0 (null)) python-jinja2 (0 (null)) bzr (0 (null)) lxc-templates (0 (null)) debootstrap (0 (null)) python-argcomplete (0 (null)) juju-local (0 (null)) canonical-mojo (0 (null)) canonical-mojo (0 (null))
Provides:
0.3.2-10 - canonical-mojo
=======
The dependency issue then shows up as:
=======
$ mojo
Traceback (most recent call last):
File "/usr/bin/mojo", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/
@_call_aside
File "/usr/lib/
f(*args, **kwargs)
File "/usr/lib/
working_set = WorkingSet.
File "/usr/lib/
ws.
File "/usr/lib/
needed = self.resolve(
File "/usr/lib/
raise DistributionNot
pkg_resources.
=======
Related branches
- Tom Haddon: Approve
-
Diff: 12 lines (+1/-1)1 file modifieddebian/control (+1/-1)
Changed in mojo: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in mojo: | |
assignee: | nobody → Tim Kuhlman (timkuhlman) |
Changed in mojo: | |
status: | Confirmed → Fix Released |
I see what's happening. The juju-deployer in juju stable PPA,0.6. 4~bzr168~ 49~ubuntu14. 04.1, while seemingly being at the 0.6.4 level doesn't meet the depends "juju-deployer (>= 0.6.4)" for whatever reason.
So I installed from debs using juju-deployer_ 0.6.4-0ubuntu1_ all.deb and it overwrote 0.6.4~bzr168~ 49~ubuntu14. 04.1. Afterwards, the mojo install completed without attempting to upgrade juju-deployer.
So, went from:
$ apt-cache policy juju-deployer 49~ubuntu14. 04.1 60~ubuntu14. 04.1 9.2~bzr203~ 60~ubuntu14. 04.1 0 ppa.launchpad. net/mojo- maintainers/ ppa/ubuntu/ trusty/main amd64 Packages 49~ubuntu14. 04.1 0 ppa.launchpad. net/juju/ stable/ ubuntu/ trusty/main amd64 Packages dpkg/status nova.clouds. archive. ubuntu. com/ubuntu/ trusty/universe amd64 Packages
juju-deployer:
Installed: 0.6.4~bzr168~
Candidate: 0.9.2~bzr203~
Version table:
0.
500 http://
*** 0.6.4~bzr168~
500 http://
100 /var/lib/
0.3.6-0ubuntu2 0
500 http://
to:
$ apt-cache policy juju-deployer 60~ubuntu14. 04.1 9.2~bzr203~ 60~ubuntu14. 04.1 0 ppa.launchpad. net/mojo- maintainers/ ppa/ubuntu/ trusty/main amd64 Packages dpkg/status 6.4~bzr168~ 49~ubuntu14. 04.1 0 ppa.launchpad. net/juju/ stable/ ubuntu/ trusty/main amd64 Packages nova.clouds. archive. ubuntu. com/ubuntu/ trusty/universe amd64 Packages
juju-deployer:
Installed: 0.6.4-0ubuntu1
Candidate: 0.9.2~bzr203~
Version table:
0.
500 http://
*** 0.6.4-0ubuntu1 0
100 /var/lib/
0.
500 http://
0.3.6-0ubuntu2 0
500 http://