juju 2.1 packaging / binaries needs some polish
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Invalid
|
Medium
|
Unassigned | ||
OpenStack Charm Test Infra |
Invalid
|
High
|
Ryan Beisner | ||
juju-release-tools |
Fix Released
|
Critical
|
Nicholas Skaggs |
Bug Description
dpb@helo:~[0]$ juju-2.0
The program 'juju-2.0' is currently not installed. You can install it by typing:
sudo apt install juju-2.0
dpb@helo:~[0]$ sudo apt-get install juju-2.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
juju-2.0 is already the newest version (1:2.1~
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
dpb@helo:~[0]$ dpkg -l |grep juju-2
ii juju-2.0 1:2.1~beta1-
dpb@helo:~[0]$ dpkg -L juju-2.0 |grep /usr/bin/juju-2
/usr/bin/juju-2.1
dpb@helo:~[0]$ ll /usr/bin/
lrwxrwxrwx 1 root root 9 Aug 16 14:04 /usr/bin/juju-1 -> juju-1.25*
-rwxr-xr-x 1 root root 68 Aug 16 14:04 /usr/bin/juju-1.25*
-rwxr-xr-x 1 root root 67 Nov 17 09:40 /usr/bin/juju-2.1*
1) package is 'juju-2.0' yet binary is not there anymore. One of these should change.
2) command-not-found needs updating?
3) Maybe introdce a 'juju-2' link?
no longer affects: | juju |
Changed in juju-release-tools: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-release-tools: | |
importance: | High → Critical |
tags: | added: uosci |
Changed in charm-test-infra: | |
assignee: | nobody → Ryan Beisner (1chb1n) |
importance: | Undecided → High |
no longer affects: | juju |
Changed in landscape: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in landscape: | |
milestone: | 16.12 → 17.01 |
Changed in landscape: | |
milestone: | 17.01 → 17.02 |
Changed in charm-test-infra: | |
status: | New → Triaged |
Changed in charm-test-infra: | |
status: | Triaged → Invalid |
Changed in juju-release-tools: | |
status: | Fix Committed → Fix Released |
So we have to make a decision on how we're going to treat 2.x releases. We can swap all of these things to ensure juju 2.1 works in this scenarios. We can also ensure you either can or cannot install them alongside either other. Do we need a generic juju-2 symlink?
Either way, the work here is to improve debian/rules to respect $VERSION.