As this issue will be addressed through packaging and juju-release-tools
project, I am marking it as Invalid for "juju" itself.
** Changed in: juju
Status: Triaged => Invalid
** Changed in: juju
Milestone: 2.1.0 => None
--
You received this bug notification because you are a member
The packages for X and Y need to retain this behavior. However, the
zesty archive won't have juju-core or juju-1.25.
** Project changed: juju-reports => juju-release-tools
** Changed in: juju-release-tools
Importance: High => Medium
--
You received this bug notification because you are a
** Also affects: juju-reports
Importance: Undecided
Status: New
** Changed in: juju-reports
Status: New => Triaged
** Changed in: juju-reports
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Project changed: juju-core => juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574076
Title:
juju package should suggest juju-1.25 not juju-core
To manage notifications about this bug go to:
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574076
Title:
juju package should suggest juju-1.25 not juju-core
To manage notifications about this bug go to:
Cunning! Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574076
Title:
juju package should suggest juju-1.25 not juju-core
To manage notifications about this bug go to:
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
