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. arm64-immediate-delete-shoul
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.
https://bugs.la
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: !i38
** 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.
https://bugs.launchpad.net/bu
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 usr/lib/juju-2.0-beta2/bin
** 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
+ lp:~juju-qa/ubuntu/xenial/juju2/xen
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 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
- wit
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
Stat
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 projec
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 1.2
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"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+attachment/4603773/+file
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 r
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 you
** 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 b
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"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+attachment/4600708/+files/juju-mongodb3.2-patches.di
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 packa
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
juju-mongo
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"
https://bugs.launchpad.net/ub
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 verifica
** 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 bu
** 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 notificatio
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++"
CGO_ENABLED
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 bui
** 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 wo
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 en
** 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 in
** 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
T
** 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 m
** 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 wo
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 curren
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 curren
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
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.
https://bugs.launchpad.net/
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.
https://
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.
https://bugs.launchpad.
** 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
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 cu
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 relea
** 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 w
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"
https://bugs.launchpad.net/ubuntu/+sou
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
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 g
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 w
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 update
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 types
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
** 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
Ti
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/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 *
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 fu
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 sy
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:
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 w
** 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 wo
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"
https://bugs.launchpad.net/ubuntu/+source/juju-cor
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 a
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
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 MAA
** 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.
ht
** 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 up
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
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 curren
** 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.
http
** 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 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 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 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 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 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 Vivid
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 -test.timeout=1
** Tags added: mongodb
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Milestone: None => 1.26-alpha1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
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/1500916
Title:
[needs-packaging] 1.24.6 is not packaged in 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 Vivid
I reported https://bugs.launchpad.net/ubuntu/+source/juju-
core/+bug/1500916 to address bug 1497087. While the Juju team has always
provided backports for its community, we don't have the privileges to
provide backports quickly. The Juju QA team has dedicated staff for
release and backport, and in
@seth
I reported https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1500916 to
address bug 1497087. While the Juju team has always provided backports for its
community, we don't have the privileges to provide backports quickly. The Juju
QA team has dedicated staff for release and backport,
** 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 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 Vivid
I prepared a backport of 1.24.6 from wily to vivid. The changelog is the only
difference between the wily and vivid versions. I made the diff like this:
diff -r -u -x *.bzr juju-core/ vivid-1.24.6/
where juju-core came from lp:ubuntu/juju-core and vivid-1.24.6 is a branch from
lp:ubuntu/juju
Public bug reported:
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 Vivid do not get
** Description changed:
Juju 1.24.6 is currently proposed to be the next stable Juju release.
The juju team want this version also proposed for wily. This release
supports systemd for local charm development and testing
[SRU Information]
juju-core has a stable release exception in
I certify that juju 1.22.8 is suitable for local charm development and
testing on trusty. Users of trusty juju 1.22.8 can create new
environments in private and public clouds. trusty juju 1.22.8 can
maintain environments back to 1.18.1 (including 1.22.6 which trusty
currently has). Upgrades of clie
** Changed in: juju-core (Ubuntu)
Status: New => 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/1322302
Title:
local provider is very slow to tranistion from a
I certify that juju 1.24.6 is suitable for local charm development and
testing using both trusty and wily containers. Users of wily juju 1.24.6
can create new environments in private and public clouds. Wily juju
1.24.6 can maintain environments back to 1.18.1 (including 1.22.6 which
wily currently
This was fixed with updates and backports to the gccgo tool-chain.
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: juju-core
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
This was superseded by bug 1481556
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
--
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/1422892
Title:
Exception for Juj
** Description changed:
Juju 1.24.6 is currently proposed to be the next stable Juju release.
The juju team want this version also proposed for wily. This release
supports systemd for local charm development and testing
[SRU Information]
juju-core has a stable release exception in
** Description changed:
Juju 1.24.6 is currently proposed to be the next stable Juju release.
The juju team want this version also proposed for wily. This release
supports systemd for local charm development and testing
[SRU Information]
juju-core has a stable release exception in
** Description changed:
Juju 1.24.6 is currently proposed to be the next stable Juju release.
The juju team want this version also proposed for wily. This release
supports systemd for local charm development and testing
[SRU Information]
juju-core has a stable release exception in
** Description changed:
Juju 1.24.6 is currently proposed to be the next stable Juju release.
The juju team want this version also proposed for wily. This release
supports systemd for local charm development and testing
[SRU Information]
juju-core has a stable release exception in
** Changed in: juju-core/1.25
Milestone: 1.25-beta2 => None
--
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 in sy
** Summary changed:
- [needs-packaging] 1.24.5 is not packaged in wily
+ [needs-packaging] 1.24.6 is not packaged in wily
** Description changed:
- Juju 1.24.5 is currently proposed to be the next stable Juju release.
+ Juju 1.24.6 is currently proposed to be the next stable Juju release.
The
This is the diff between juju-core 1.24.5 and 1.24.6 All the changes are to the
principal
project: src/github.com/juju/juju/. There are 10 new files each with the
expected copyright and license:
+// Copyright 2015 Canonical Ltd.
+// Licensed under the AGPLv3, see LICENCE file for details.
Hi Robie.
I have updated the juju-core source package branch per you suggestions.
I applied your 2 patches. I also added gccgo-5 as the preferred compiler
for wily ppc64el and arm64 to match packaging changes from the juju
stable ppa. I updated the local and manual tests to only install upstart
wh
** Changed in: juju-core
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1494441
Title:
ppc64el: cannot find package "encoding"
To mana
1 - 100 of 419 matches
Mail list logo
