[Bug 1267393] Juju MIR resposne

Colin Watson cjwatson at canonical.com
Mon Sep 28 11:04:11 UTC 2015


On Mon, Sep 28, 2015 at 07:51:47AM -0000, Tim Penhey wrote:
> We do test a number of upgrade combinations, and I'm curious as to why
> you say it is impossible to upgrade? What exactly is the situation you
> are attempting?

It's just about version numbers, as Seth says.  The constraint that
should be satisfied is that, if a package is in both series A and series
B and B > A, then version(B, package) >= version(A, package).  juju-core
fails this constraint because 15.04 hasn't been upgraded to Juju 1.22.6
but 14.04 LTS has:

  $ rmadison juju-core | egrep 'trusty|vivid'
   juju-core | 1.18.1-0ubuntu1         | trusty/universe         | source, amd64, arm64, armhf, i386, powerpc, ppc64el
   juju-core | 1.22.1-0ubuntu1         | vivid/universe          | source, amd64, arm64, armhf, i386, powerpc, ppc64el
   juju-core | 1.22.6-0ubuntu1~14.04.1 | trusty-updates/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1267393

Title:
  [MIR] juju-core, juju-mongodb, gccgo, golang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions



More information about the Ubuntu-server-bugs mailing list