These updates were presented to slangasek and the point of the making
juju1 the default is the one point left that we requested feedback on.
Feedback from slangasek is that if we're not prepared to make juju1 the default
then:
"upon upgrade, juju == juju2; if you want juju1, run juju-1.$fwibble
- adding a comment to the juju 2.0 FFe that clarifies that the juju
client is built and runs on all architectures, including 32bit.
Comment added under the heading Mongodb to this effect since that's
where the confusion derived from.
- document the process for avoiding a late stage FFe and
See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.
** Description changed:
When upgrading to Xenial the new default Juju version is going to be
2.0.
Because 2.0 clients are not compatible with 1.X environments,
See https://bugs.launchpad.net/juju-core/+bug/1564622 for the reasoning
of this path.
--
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/1564670
Title:
After upgrade Juju 1.X should
This will be a target for the Juju team to update and verify that the
stripping of the binary is safe and passes all testing. This requires
building in some gating based on if the binary is golang vs gccgo.
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in:
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as
Add item
- document the process for avoiding a late stage FFe and package upload
for 16.10
--
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/1545913
Title:
[FFe] juju-core 2.0
To
In an IRC conversation with: stgraber, infinity, mgz
We agreed that the outstanding issues are the following:
- adding a comment to the juju 2.0 FFe that clarifies that the juju client is
built and runs on all architectures, including 32bit.
- move the juju binary metapackage suggest juju-1.25
No, there is no KVM local provider in Juju 2.0. Product management has
made the determination that the lxd tool provides the needed
functionality for both the lxc and kvm use cases. lxd in Juju 2.0 will
be the answer.
--
You received this bug notification because you are a member of Ubuntu
As part of our exception, we're blocking the inclusion of two other
packages:
https://bugs.launchpad.net/ubuntu/+bug/1561043
https://bugs.launchpad.net/ubuntu/+bug/1561037
As we update Juju around this exception those will be effected and will
need to have some leeway in the process.
--
You
Curtis, did you have a bug filed I can look back at the history there? I
faintly recall the conversation but I don't remember if we had some
documentation/bug to go with it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
We'd like to complete updating juju-quickstart to support a $JUJU env
variable to help enable and aid CI and testing. This would allow the
user to specify which Juju client to use which would open the doors to
testing quickstart on one system against several versions of Juju.
Public bug reported:
We have the goal this cycle of updating juju-quickstart to be able to
build the environments.yaml block for MAAS as it can for local, ec2,
hpcloud, etc. This work is not yet complete, but we'd like to request an
exception to get it in.
There is little risk that adding
** Changed in: juju-quickstart
Status: New = Triaged
** Changed in: juju-quickstart
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
Brian, can you do me a favor and check out the network inspector tool of
the browser in your scenario? The client you load the GUI from needs to
be able to login/pull down the JS from the GUI charm, however it also
needs to talk on other ports as it holds a websocket connection to the
juju state
*** This bug is a duplicate of bug 1306537 ***
https://bugs.launchpad.net/bugs/1306537
Marked as a dupe. This is corrected in juju-quickstart 1.3.2. We'll work
on getting it updated in Trusty after the holiday this week.
** This bug has been marked a duplicate of bug 1306537
LXC local
Yes, we were originally told the feature we were waiting on would be in
release 1.18. It ended up they cut additional releases ahead of 1.18
that implemented what was required. The 1.18 note is no longer valid.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
@Michael
- Can you explain what all the PPA adding and pulling in packages from
universe is about? Why not depend on juju-core directly, or is this
installation done on other machines?
Quickstart is meant to provide a nice single point to get developers and
users started with Juju as fast and
Marking invalid as fixes have been released and things have been quite
for a while. If the issue returns please open a new bug.
** Changed in: juju-gui
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
Segfaults in apache2 with libapache2-mod-php5 installed
https://bugs.launchpad.net/bugs/418897
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Just to verify the workaround above of disabling the session encryption
seems to be working so far.
--
Segfaults in apache2 with libapache2-mod-php5 installed
https://bugs.launchpad.net/bugs/418897
You received this bug notification because you are a member of Ubuntu
Server Team, which is
22 matches
Mail list logo
