juju package should suggest juju-1.25 not juju-core
Bug #1574076 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Unassigned | ||
juju-release-tools |
Triaged
|
Medium
|
Unassigned | ||
juju (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
As per the title, since juju-core is a transitional package, the suggests for juju should be juju-1.25 and the depends should be juju-2.0
tags: | added: packaging |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju-reports: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
The Suggests is dual purpose for Xenial. Both does the normal job of informing the user of the new juju 1.X specific package, but is also a tricky upgrade hack. The release team noted that the upgrade process now autoremoves packages in its default behaviour, so going to Xenial and 2.0 juju would take away everyone's working client. The Suggests on the old package name avoids that. A Suggests on the new package name would not, and 2.0 juju doesn't really want to Depends or Recommends on 1.X juju.
For Y, the old aliases and other transitional elements related to package upgrades from 1.X should be removed.