On Mon, May 12, 2014 at 02:32:02AM -0000, Ian Booth wrote: > We do need the actual series name and version number in the code. The > reason is that there's validation to ensure that simplestreams metadata > for images and tools is correct, and we need to check that the series > information encoded in the metadata is correct. We read the series info > from /usr/share/distro-info/ubuntu.csv. However, we can't guarantee that > the distro-info-data package is installed, so use hard coded fallbacks > just in case.
In my failure case, I did have distro-info available, but juju still failed for me on Utopic. I haven't verified this though. BTW, are we sure that /usr/share/distro-info/ubuntu.csv a published interface, or should we be calling distro-info for the data instead? Maybe we could have juju-core in archive depend on distro-info-data, and then dep8 test just this path with a newer release? This is for the specific case of installing juju from the archive as shipped with a release. Then this would no longer be an issue for juju in the archive. I understand that other cases have different needs (and this particular bug isn't an issue in that case). > just in case. I guess a question I have is do we really care about > running Juju 1.18 on Utopic given that by the time Utopic is released, > there will be a matching Juju version also. We've got some other 1.18 > bugs to fix so we are also able to easily add Utopic support anyway in > this case, but in general, I wonder what our policy will be? The problem is that we cannot land even an unrelated SRU to Trusty, because the standard SRU process is to fix the development release first, and Utopic is broken so I can't verify anything. This prevents James from bumping the microrelease in Trusty, so we can't fix anything else in Trusty's juju right now. This also affects other packages. For example, I cannot land a juju-quickstart fix for bug 1306537. We could ask for an exception, but it seems to me that we shouldn't have it broken this way by design in the first place, so I'm asking if there's a way we can fix it that works for all cases instead. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1314686 Title: Please add support for utopic To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1314686/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
