** Changed in: juju-core
Milestone: 2.0-beta6 => 2.0-beta7
--
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 manage
** Changed in: juju-core
Milestone: 2.0-beta6 => 2.0-beta7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570660
Title:
Plugins not included in juju manpages
To manage notifications about this
** Changed in: juju-core
Milestone: 2.0-beta6 => 2.0-beta7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657
Title:
Bash completion needed for versioned juju commands
To manage
** Changed in: juju-core
Milestone: 2.0-beta6 => 2.0-beta7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570651
Title:
Manpages for juju aliases drop version
To manage notifications about
** Changed in: juju-core
Status: Triaged => 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/1492088
Title:
juju bootstrap fails inside a wily container
To manage notifications
** Changed in: juju-core
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1340836
Title:
error: error executing "lxc-start" when juju client runs inside kvm
To manage
** 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:
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570651
Title:
Manpages for juju aliases drop version
To manage notifications about this
** Changed in: juju-core
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/1570654
Title:
Manpage still refers to 1.X config for 2.0
To manage
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
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 manage
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564670
Title:
After dist upgrade Juju 1.X should still be the default
To manage
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570660
Title:
Plugins not included in juju manpages
To manage notifications about this
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570657
Title:
Bash completion needed for versioned juju commands
To manage notifications
** Changed in: juju-core
Status: Triaged => 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/1290920
Title:
non-default lxc-dir breaks local provider
To manage notifications about
** Tags added: jujuqa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571082
Title:
autopkgtest lxd provider tests fail for 2.0
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: 2.0-beta4 => 2.0-rc1
--
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 manage
Hi Doko and Michael.
mwhudson, sinzui: juju-mongodb-tools: and vendor/src/golang.org/x/ reference a
LICENSE file which doesn't exist in the sources. Please add it
mwhudson, sinzui: rejected for now. afaics the other license information, and
the packaging seem to be okish
I apologise. I was
Hi Steve. Continuing with the conversation on the wrong bug...I prepared
the Juju2 specific packages to be 64 bit only. Neither Juju or upstream
support 32-bit servers.
But there was a change in plan that I was not privy to. Since 1.25 does
want juju-mongodb2.6, I think we could make the i386 and
Thank you Michael for improving the rules for this package. The Juju
team agreed that a universal mongo-tools is ideal, but too risky to
assume is true. That is why this package has the 3.2 in its name.
I think this package needs to be in main because "main" means supported.
Juju is supported and
** Changed in: juju-core/1.25
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To
** Tags added: packaging
** Summary changed:
- After upgrade Juju 1.X should still be the default
+ After dist upgrade Juju 1.X should still be the default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch is good. arm64 passes just like amd64 and ppc64el
https://launchpadlibrarian.net/251720877/buildlog_ubuntu-xenial-arm64.juju-mongodb3.2_3.2.0-0ubuntu1~juju9_BUILDING.txt.gz
I have pushed the changes to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
--
You
I am testing the patch now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557852
Title:
[needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty
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/1564662
Title:
Juju binaries should be stripped
To manage notifications about this bug go to:
Hi Robie
Attached are my changes. that I pushed to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
> Thank you for the update. I've reviewed the patches now they have
> headers so I can follow what's going on. Most look OK. I'm unhappy
> with two: 1.
Hi Robie
Attached are my changes. that I pushed to
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
> Thank you for the update. I've reviewed the patches now they have
> headers so I can follow what's going on. Most look OK. I'm unhappy
> with two: 1.
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Robie.
> In override_dh_clean, rm -rf /tmp/go-build* will interfere with other
Thank you for calling this out. I have removed it. It is not needed.
> Other notes (I can fix up):
The rules were written to work for wily and trusty. I look forward
to removing the work arounds or using a better
Hi Robie.
> In override_dh_clean, rm -rf /tmp/go-build* will interfere with other
Thank you for calling this out. I have removed it. It is not needed.
> Other notes (I can fix up):
The rules were written to work for wily and trusty. I look forward
to removing the work arounds or using a better
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Triaged => 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/1184457
Title:
** Changed in: juju-core
Status: Triaged => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Ouch
> For completeness this is the lintian output in all its glory:
> E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
I certainly could have put "xenial-amd64" in the changelog, but i do not
see in debian. my find also fails
>E: juju2: embedded-library
Ouch
> For completeness this is the lintian output in all its glory:
> E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
I certainly could have put "xenial-amd64" in the changelog, but i do not
see in debian. my find also fails
>E: juju2: embedded-library
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
- bzr push lp:~sinzui/ubuntu/xenial/juju2/xenial-2.0-beta2
+
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
- bzr push lp:~sinzui/ubuntu/xenial/juju2/xenial-2.0-beta2
+
Attached is a gz diff of the changes in src/ from juju 1.25.4 to
2.0-beta2. Sorry. This is hell to read.
** Patch added: "All changes to juju and embedded deps"
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+attachment/4607608/+files/xenial-2.0-beta2.diff.gz
** Description
Attached is a gz diff of the changes in src/ from juju 1.25.4 to
2.0-beta2. Sorry. This is hell to read.
** Patch added: "All changes to juju and embedded deps"
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1560315/+attachment/4607608/+files/xenial-2.0-beta2.diff.gz
** Description
The attaches diff shows the changes to the juju embedded dependencies.
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
- Juju 2.0 uses a new package name, juju2. This package is co-installable
-
The attached diff shows the changes to debian/ from the 1.25.4 branch
(lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4). The 1.25.4 branch
is stalled. We are waiting on a 1.25.5 to fix a regressions. We do not
expect any other changes to the debian dir other than the changelog.
** Patch added:
The attached diff shows the changes to debian/ from the 1.25.4 branch
(lp:~sinzui/ubuntu/xenial/juju-core/xenial-1.25.4). The 1.25.4 branch
is stalled. We are waiting on a 1.25.5 to fix a regressions. We do not
expect any other changes to the debian dir other than the changelog.
** Patch added:
The attaches diff shows the changes to the juju embedded dependencies.
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
- Juju 2.0 uses a new package name, juju2. This package is co-installable
-
Public bug reported:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
Juju 2.0 uses a new package name, juju2. This package is co-installable
with juju-core.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Public bug reported:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
Juju 2.0 uses a new package name, juju2. This package is co-installable
with juju-core.
** Affects: juju-core (Ubuntu)
Importance: Undecided
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
# juju-mongo-tools3.2
The Juju team wants juju-mongo-tools3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongo-tools3.2/xenial-mongo-tools3.2
This package is new. Upstream replaced the mongo tools included in
MongoDB 2.x with new tools from the mongo-tools
Public bug reported:
# juju-mongo-tools3.2
The Juju team wants juju-mongo-tools3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongo-tools3.2/xenial-mongo-tools3.2
This package is new. Upstream replaced the mongo tools included in
MongoDB 2.x with new tools from the mongo-tools
A diff of the missing sources added to debian/.
** Patch added: "juju-mongo-tools3.2-missing-sources.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+attachment/4601655/+files/juju-mongo-tools3.2-missing-sources.diff
--
You received this bug notification because
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
Thank you for the feedback Robie. Attached is a diff of my dep-3
changes. I also updated the control arch to any per Dimitri's desire to
build every where possible
** Patch added: "dep-3 and arch any"
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed to
This is the error
jenkins@wily-slave:~$ sudo lxc-start -n curtis -F
ln: failed to create symbolic link
‘/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct’: Read-only file
system
lxc-start: conf.c: run_buffer: 347 Script exited with status 1
lxc-start: conf.c: lxc_setup: 3750 failed to
A diff of the missing sources added to debian/.
** Patch added: "juju-mongo-tools3.2-missing-sources.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+attachment/4601655/+files/juju-mongo-tools3.2-missing-sources.diff
--
You received this bug notification because
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
This was also seen by the in Juju CI on the wily hosts that pull lxd/lxc
packages from the lxd ppa. We downgrades the wily machines to packages
from wily-updates to get lxc working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for the feedback Robie. Attached is a diff of my dep-3
changes. I also updated the control arch to any per Dimitri's desire to
build every where possible
** Patch added: "dep-3 and arch any"
A diff of the patch changes for juju-mongodb3.2. It is easier to read
the actual patches then to read this diff of a patch.
** Patch added: "juju-mongodb3.2-patches.diff"
** Tags added: lxc xenial
--
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this
Public bug reported:
# juju-mongodb3.2
The Juju team wants juju-mongodb3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
This package is an fork and upgrade of the juju-mongodb2.6 package
that will be used in upgrades. There is a lot of change in this
A diff of the patch changes for juju-mongodb3.2. It is easier to read
the actual patches then to read this diff of a patch.
** Patch added: "juju-mongodb3.2-patches.diff"
Public bug reported:
# juju-mongodb3.2
The Juju team wants juju-mongodb3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
This package is an fork and upgrade of the juju-mongodb2.6 package
that will be used in upgrades. There is a lot of change in this
** Tags added: lxc xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this bug go to:
Public bug reported:
# juju-mongodb2.6
The Juju team wants juju-mongodb2.6 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6
This packaged in is a fork of juju-mongodb upgraded to version 2.6.
This package is only used to upgrade from juju-mongodb to
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
Public bug reported:
# juju-mongodb2.6
The Juju team wants juju-mongodb2.6 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6
This packaged in is a fork of juju-mongodb upgraded to version 2.6.
This package is only used to upgrade from juju-mongodb to
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
Public bug reported:
Juju 1.25.4 enabled maas 1.9 and fixes many bugs reported against 1.25.0
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
Since there are multiple
Public bug reported:
Juju 1.25.4 enabled maas 1.9 and fixes many bugs reported against 1.25.0
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
Since there are multiple
** Changed in: juju-core
Milestone: 2.0-alpha1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: 2.0-alpha1 => None
--
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/1516989
Title:
juju status broken
To manage notifications about this
** Changed in: juju-core/1.25
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.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage
** Changed in: juju-core/1.25
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/1516989
Title:
juju status broken
To manage notifications about this bug
With the new package installed we see to correct GOARCH
gccgo-go env
GOARCH="ppc64le"
GOBIN=""
GOCHAR=""
GOEXE=""
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr"
GOTOOLDIR="/usr/lib/gccgo/tool"
TERM="dumb"
CC="gcc"
GOGCCFLAGS="-g -O2 -fPIC"
CXX="g++"
With the new package installed we see to correct GOARCH
gccgo-go env
GOARCH="ppc64le"
GOBIN=""
GOCHAR=""
GOEXE=""
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr"
GOTOOLDIR="/usr/lib/gccgo/tool"
TERM="dumb"
CC="gcc"
GOGCCFLAGS="-g -O2 -fPIC"
CXX="g++"
** Changed in: juju-core
Importance: Critical => High
** Summary changed:
- cannot build trusty ppc64el juju
+ cannot build trusty ppc64el juju without forcing GOARCH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core
Milestone: 1.23-beta1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's "Option interface-mtu 9000" is being ignored on bridge
interface br0
@Robie
The Juju QA team listed ubuntu proposed testing as a gap we would fix. I
think we can setup daily build using using proposed for each supported
series and arch to prevent regressions getting into updates
@Michael
gccgo-go env shows this on stillson-09 (which means the host that runs unit
Public bug reported:
The juju-core package cannot be built. Go thinks it is cross-compiling.
Go install native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it tries to use
the juju/jujud in bin/, and does not find it.
The last successful
Public bug reported:
The juju-core package cannot be built. Go thinks it is cross-compiling.
Go install native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it tries to use
the juju/jujud in bin/, and does not find it.
The last successful
This bug blocks Juju's CI testing and releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1527020
Title:
cannot build trusty ppc64el juju
To manage notifications about this bug go to:
** Description changed:
The juju-core package cannot be built. Go thinks it is cross-compiling.
- Go install native binaries to $GOPATH/bin, and non-native binaries to
+ Go installs native binaries to $GOPATH/bin, and non-native binaries to
$GOPATH/bin/. The juju core packaging fails when it
** Changed in: juju-core
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/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
** Changed in: juju-core/1.25
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/1496972
Title:
juju bootstrap fails to successfully configure the bridge
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
101 - 200 of 3430 matches
Mail list logo
