This bug was fixed in the package juju-core - 1.24.7-0ubuntu1~14.04.1
---
juju-core (1.24.7-0ubuntu1~14.04.1) trusty; urgency=medium
[ Curtis C. Hovey ]
* Backport of 1.24.7 from vivid. (Lp: #1506652)
[ Robie Basak ]
* This upload results in the following packaging delta from
This bug was fixed in the package juju-core - 1.24.7-0ubuntu1~15.04.1
---
juju-core (1.24.7-0ubuntu1~15.04.1) vivid; urgency=medium
* New upstream microrelease. (Lp: #1506652)
* Update dep8 tests from Xenial.
-- curtis.ho...@canonical.com (Curtis C. Hovey) Fri, 16 Oct 2015
17:5
** Changed in: juju-core (Ubuntu)
Importance: Undecided => Low
** Changed in: juju-core (Ubuntu Trusty)
Importance: Undecided => Low
** Changed in: juju-core (Ubuntu Vivid)
Importance: Undecided => Low
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
Y
** Tags removed: 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://bugs.launchpad.net/bugs/1506652
Title:
[needs-packaging] Juju 1.24.7 is not in Ubuntu
To manage notifications about th
** 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
Hello Curtis, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.24.7-0ubuntu1~14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** 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
Hello Curtis, or anyone else affected,
Accepted juju-core into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.24.7-0ubuntu1~15.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Uploaded 1.24.7 to Trusty now that 1.22.8-0ubuntu1~14.04.1 is in trusty-
updates. I'm not sure why it is still in trusty-proposed but that
doesn't matter as it should be superceded by this new upload once
accepted.
I added a changelog note to explain the packaging difference from the
previous pack
Uploaded 1.24.7 to Wily, with only minor changes. See
https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-
core/+git/packaging/log/?h=basak/vivid and please pull them in for any
future uploads.
Good to upload to Trusty with only minor changes again but I'm holding
until 1.22.8-0ubuntu1~14
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Status: New => Triaged
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member
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
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
Please could you rebase on 1.24.6-0ubuntu2? I'm not sure whether the MIR
changes have any implications for our process either - eg. for Vivid..
--
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.
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
** Also affects: juju-core (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Triaged
** Changed in: juju-core (Ubuntu Vivid)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubu
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:
** Branch linked: lp:~sinzui/ubuntu/vivid/juju-core/vivid-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 m
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
** Branch linked: 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 man
31 matches
Mail list logo
