Since you mentioned "recovery" I assume that you are using the "Device
-> Attempt Data Rescue" menu option. If this is the case then the
required package is "gpart" (guess partitions). The command to install
*gpart* on ubuntu is:
sudo apt-get update && apt-get install gpart
If my
I certify that juju 1.24.7 is suitable for local charm development and testing.
Users of trusty juju 1.24.7 can create new environments in private and public
clouds. Trusty juju 1.24.7 can maintain environments back to 1.18.1 (including
1.22.8 which trusty currently has). Upgrades of clients and
I certify that juju 1.24.7 is suitable for local charm development and testing.
Users of trusty juju 1.24.7 can create new environments in private and public
clouds. Trusty juju 1.24.7 can maintain environments back to 1.18.1 (including
1.22.8 which trusty currently has). Upgrades of clients and
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
** Description changed:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for
** Description changed:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To manage notifications
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To
Thank you Rolf for your interest in improving GParted.
This problem was fixed upstream in GParted 0.20.0. See the following
upstream bug report:
GParted resizes the wrong filesystem (does not pass the devid to btrfs
filesystem resize)
https://bugzilla.gnome.org/show_bug.cgi?id=723842
The
I certify that juju 1.25.0 is suitable for local charm development and testing
using both trusty and wily containers. Users of wily juju 1.25.0 can create
new environments in private and public clouds. wily juju 1.25.0 can maintain
environments back to 1.18.1 (including 1.24.7 which wily currently
I certify that juju 1.25.0 is suitable for local charm development and testing
using both trusty and wily containers. Users of wily juju 1.25.0 can create
new environments in private and public clouds. wily juju 1.25.0 can maintain
environments back to 1.18.1 (including 1.24.7 which wily currently
I certify that juju 1.24.7 is suitable for local charm development and testing
using both trusty and vivid containers. Users of vivid juju 1.24.7 can create
new environments in private and public clouds. Vivid juju 1.24.7 can maintain
environments back to 1.18.1 (including 1.24.6 which vivid
I certify that juju 1.24.7 is suitable for local charm development and testing
using both trusty and vivid containers. Users of vivid juju 1.24.7 can create
new environments in private and public clouds. Vivid juju 1.24.7 can maintain
environments back to 1.18.1 (including 1.24.6 which vivid
I certify that juju 1.24.7 is suitable for local charm development and testing
using both trusty and vivid containers. Users of vivid juju 1.24.7 can create
new environments in private and public clouds. Vivid juju 1.24.7 can maintain
environments back to 1.18.1 (including 1.24.6 which vivid
I certify that juju 1.24.7 is suitable for local charm development and testing
using both trusty and vivid containers. Users of vivid juju 1.24.7 can create
new environments in private and public clouds. Vivid juju 1.24.7 can maintain
environments back to 1.18.1 (including 1.24.6 which vivid
I restored verification-needed. This package is not in wily yet and
needs verification.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I restored verification-needed. This package is not in wily yet and
needs verification.
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue was fixed when trusty-updates got 1.22.6.
** Changed in: juju-core (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271144
This issue was certainly fixed when trusty got juju 1.20.11.
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330406
This issue was certainly fixed when trusty got juju 1.20.11.
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1510565
Title:
[needs-packaging] Juju 1.25.0 is not in xenial
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510565
Title:
[needs-packaging] Juju 1.25.0 is not in xenial and wily
To manage
This issue was fixed when trusty-updates got 1.22.6.
** Changed in: juju-core (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I certify that juju 1.25.0 is suitable for local charm development and testing
using both trusty and xenial containers. Users of xenial juju 1.25.0 can create
new environments in private and public clouds. Xenial juju 1.25.0 can maintain
environments back to 1.18.1 (including 1.24.7 which xenial
I certify that juju 1.25.0 is suitable for local charm development and testing
using both trusty and xenial containers. Users of xenial juju 1.25.0 can create
new environments in private and public clouds. Xenial juju 1.25.0 can maintain
environments back to 1.18.1 (including 1.24.7 which xenial
I removed block-proposed because Juju 1.25.0 is relesed upstream now.
** Tags removed: block-proposed
** Description changed:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable
I removed block-proposed because Juju 1.25.0 is relesed upstream now.
** Tags removed: block-proposed
** Description changed:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable
Public bug reported:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version
Public bug reported:
Juju 1.25.0 adds a payload management for charms. The Juju team want
this version of Juju in Xenial and Wily.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version
I created a branch for xenial. This is just a forward port of the wily
branch. Only the changelog differs.
** Branch linked: lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.24.7
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance
I created a branch for xenial. This is just a forward port of the wily
branch. Only the changelog differs.
** Branch linked: lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.24.7
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance
My juju-core 1.25.0 package is based on 1.24.6-0ubuntu3. 1.25.0 contains 16
dependencies changes:
* 2 new go packages, github.com/juju/deputy and gopkg.in/juju/environschema.v1
* 13 update go packages that are unique to juju-core
* 1 package, github.com/juju/loggo, is newer than the the dh-golang
The 1.24.6-0ubuntu3 package in both wily and xenial use:
golang-go-dbus-dev
golang-go.crypto-dev
golang-go.net-dev
golang-juju-loggo-dev
There are/were inompatabilities with some of the other -dev packakages in
wily. The Juju QA team are working on updating packages in Debian to so that
the they
My juju-core 1.25.0 package is based on 1.24.6-0ubuntu3. 1.25.0 contains 16
dependencies changes:
* 2 new go packages, github.com/juju/deputy and gopkg.in/juju/environschema.v1
* 13 update go packages that are unique to juju-core
* 1 package, github.com/juju/loggo, is newer than the the dh-golang
The deb.diff is from 1.24.6-0ubuntu3. I updated the copyright files for
the new revisions. I also reviewed all the dates of the copyrights of the
sources and found changes maybe should have been in the 1.24.6-0ubuntu3
package. Like my concurrent packages for juju-core 1.24.7 I removed the .pc/
dir
The deb.diff is from 1.24.6-0ubuntu3. I updated the copyright files for
the new revisions. I also reviewed all the dates of the copyrights of the
sources and found changes maybe should have been in the 1.24.6-0ubuntu3
package. Like my concurrent packages for juju-core 1.24.7 I removed the .pc/
dir
The diff of the juju-core 1.25.0 package is from 1.24.6-0ubuntu3. It is
196702 lines long. There are 623 new files, 109 removed files. Most of the
removes are really moves to new locations or other go packages.
** Patch added: "juju-core diff from 1.24.6"
The diff of the juju-core 1.25.0 package is from 1.24.6-0ubuntu3. It is
196702 lines long. There are 623 new files, 109 removed files. Most of the
removes are really moves to new locations or other go packages.
** Patch added: "juju-core diff from 1.24.6"
The 1.24.6-0ubuntu3 package in both wily and xenial use:
golang-go-dbus-dev
golang-go.crypto-dev
golang-go.net-dev
golang-juju-loggo-dev
There are/were inompatabilities with some of the other -dev packakages in
wily. The Juju QA team are working on updating packages in Debian to so that
the they
** Branch linked: lp:~sinzui/ubuntu/wily/juju-core/xenial-1.25.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510565
Title:
[needs-packaging] Juju 1.25.0 is not in xenial and wily
To manage
** Branch linked: lp:~sinzui/ubuntu/wily/juju-core/xenial-1.25.0
--
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/1510565
Title:
[needs-packaging] Juju 1.25.0 is not in xenial and
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1508577
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508577
Title:
[wily]
I updated all three branches to get the fake-future.sh fix that was
added to 1.24.6-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506652
Title:
[needs-packaging] Juju 1.24.7 is not in
I updated all three branches to get the fake-future.sh fix that was
added to 1.24.6-0ubuntu3.
--
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/1506652
Title:
[needs-packaging] Juju
lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7 is now rebased on
1.24.6-0ubuntu2. After running dep8 tests, I also ran the build deb
through the wily Juju CI tests to be certain the package is functionally
the same as my previous package.
We need to rethink our plans for backports. dh-golang is not
lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7 is now rebased on
1.24.6-0ubuntu2. After running dep8 tests, I also ran the build deb
through the wily Juju CI tests to be certain the package is functionally
the same as my previous package.
We need to rethink our plans for backports. dh-golang is not
To summarise:
There are 3 branches, one for wily, vivid, and trusty each.
juju-core's source has no dep changes, or new files. no copyrights or
licences changed.
The wily debian/tests dir was updated to remove the switch to upstart.
The wily debian/tests dir was updated to skip
To summarise:
There are 3 branches, one for wily, vivid, and trusty each.
juju-core's source has no dep changes, or new files. no copyrights or
licences changed.
The wily debian/tests dir was updated to remove the switch to upstart.
The wily debian/tests dir was updated to skip
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.24.7 is a backport of the wily
1.24.7 package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ trusty-1.24.7/ >
./1.24.7-trusty-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x
This a revised debian diff for wily. I revised the future tests because
they were no compatible with trusty. We want a simple backport to trusty
and vivid where only the changelog is different from wily. trusty is a
sensible to perform future series upgrade tests with because it does not
support
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.24.7 is a backport of the wily
1.24.7 package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ trusty-1.24.7/ >
./1.24.7-trusty-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.24.7 is a backport of the wily
1.24.7 package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ trusty-1.24.7/ >
./1.24.7-trusty-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x
This a revised debian diff for wily. I revised the future tests because
they were no compatible with trusty. We want a simple backport to trusty
and vivid where only the changelog is different from wily. trusty is a
sensible to perform future series upgrade tests with because it does not
support
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.24.7 is a backport of the wily
1.24.7 package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ trusty-1.24.7/ >
./1.24.7-trusty-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ wily-1.24.7/ > ./1.24.7-vivid-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x *.bzr
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ wily-1.24.7/ > ./1.24.7-vivid-backport.diff
only the changelogs differ.
** Patch added: "diff -r -u -x *.bzr
Correction:
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ vivid-1.24.7/ >
./1.24.7-vivid-backport.diff
only the changelogs differ.
** Attachment removed:
Correction:
lp:~sinzui/ubuntu/vivid/juju-core/vivid-1.24.7 is a backport of the wily 1.24.7
package I prepared. Attached is a diff of the two packages made using
diff -r -u -x *.bzr wily-1.24.7/ vivid-1.24.7/ >
./1.24.7-vivid-backport.diff
only the changelogs differ.
** Attachment removed:
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
** Description changed:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to
That workaround may be fine for some, but for my use case (documentation
involving UI controls), it's not desirable to have the cursor included.
Good to know, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu Vivid)
Status: Fix Committed => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
My branch lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7 is a simple
import of 1.24.7 from 1.24.6. Per previous suggestions, I removed the
rules to switch init systems in adt tests. Juju supports both upstart
and systemd and adt should test that juju "just works" with the Ubuntu
release.
** Patch
lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506652
Title:
[needs-packaging] Juju 1.24.7 is not in Ubuntu
To manage notifications about this bug go
lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7
--
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/1506652
Title:
[needs-packaging] Juju 1.24.7 is not in Ubuntu
To manage notifications
My branch lp:~sinzui/ubuntu/wily/juju-core/wily-1.24.7 is a simple
import of 1.24.7 from 1.24.6. Per previous suggestions, I removed the
rules to switch init systems in adt tests. Juju supports both upstart
and systemd and adt should test that juju "just works" with the Ubuntu
release.
** Patch
Attached is the diff from Juju 1.24.6 to 1.24.7. This is a painless diff
compared to most Juju releases.
No dependencies changed
Not files were added,
No copyrights or licences changed.
** Patch added: "Diff from jujuc-core 1.24.6 to 1.24.7"
Attached is the diff from Juju 1.24.6 to 1.24.7. This is a painless diff
compared to most Juju releases.
No dependencies changed
Not files were added,
No copyrights or licences changed.
** Patch added: "Diff from jujuc-core 1.24.6 to 1.24.7"
Public bug reported:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to work with
Public bug reported:
Juju 1.24.7 addresses changes happening in AWS and MAAS. AWS deprecated
the m1* instance types and users of older Jujus are seeing cases where
EC2 does not have enough instances. Juju 1.24.7 will ask for newer
instance types. Juju 1.24.7 has a dhcp related fix to work with
** Changed in: juju-core (Ubuntu Vivid)
Status: Fix Committed => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have verified that upgrading (with proposed enabled) from trusty to
vivid does upgrade all the juju-core related packages from 1.22.6 to
1.24.6. Juju works before and after the upgrade.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
** Description changed:
juju 1.18.1 is in trusty-release
Juju 1.22.6 is in trusty-updates
Juju 1.22.1 is in vivid-release, meaning upgrades from updated trusty to
vivid fail
Juju 1.22.6 is in wily
As a result of these version numbers, a fully-updated trusty system
should fail to
I have verified that upgrading (with proposed enabled) from trusty to
vivid does upgrade all the juju-core related packages from 1.22.6 to
1.24.6. Juju works before and after the upgrade.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
** Description changed:
juju 1.18.1 is in trusty-release
Juju 1.22.6 is in trusty-updates
Juju 1.22.1 is in vivid-release, meaning upgrades from updated trusty to
vivid fail
Juju 1.22.6 is in wily
As a result of these version numbers, a fully-updated trusty system
should fail to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Changed in: juju-core (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I certify that juju 1.24.6 is suitable for local charm development and
testing using both trusty and vivid containers. Users of vivid juju
1.24.6 can create new environments in private and public clouds. Vivid
juju 1.24.6 can maintain environments back to 1.18.1 (including 1.22.1
which vivid
I certify that juju 1.24.6 is suitable for local charm development and
testing using both trusty and vivid containers. Users of vivid juju
1.24.6 can create new environments in private and public clouds. Vivid
juju 1.24.6 can maintain environments back to 1.18.1 (including 1.22.1
which vivid
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
Looking at
http://reports.vapour.ws/releases/issue/559694bd749a5660bd8b8f07
running the unit tests with the race option is best at triggering a bad record
mac, though running in lxc might also be a factor. Unpack the juju-core tarfile
cd src/github.com/juju/juju
go test -race
Looking at
http://reports.vapour.ws/releases/issue/559694bd749a5660bd8b8f07
running the unit tests with the race option is best at triggering a bad record
mac, though running in lxc might also be a factor. Unpack the juju-core tarfile
cd src/github.com/juju/juju
go test -race
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
** Description changed:
Juju 1.24.6 is currently the stable Juju release and it is in Wily. The Juju
team want this version also in Vivid too. This release supports systemd for
local charm development and testing. Vivid needs a newer Juju version to
ensure Trusty users who upgrade to
501 - 600 of 5893 matches
Mail list logo
