This bug was fixed in the package juju-core - 1.25.0-0ubuntu1~15.10.1
---
juju-core (1.25.0-0ubuntu1~15.10.1) wily; urgency=medium
* No change backport to 15.10 (LP: #1510565).
-- Robie Basak Thu, 29 Oct 2015 11:25:46
+
** Changed in: juju-core (Ubuntu Wily)
Status:
** Changed in: juju-core (Ubuntu Wily)
Importance: Undecided => Wishlist
** Tags removed: needs-packaging
** Changed in: juju-core (Ubuntu)
Importance: Wishlist => Low
** Changed in: juju-core (Ubuntu Wily)
Importance: Wishlist => Low
--
You received this bug notification because you
** 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
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
FWIW: You can also namespace verification using
'verification-(needed|done)-$series'.
--
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 i
Hello Curtis, or anyone else affected,
Accepted juju-core into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/juju-
core/1.25.0-0ubuntu1~15.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
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://
** 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
This bug was fixed in the package juju-core - 1.25.0-0ubuntu1
---
juju-core (1.25.0-0ubuntu1) xenial; urgency=medium
* New upstream release (Lp: #1510565).
* d/copyright updated for Juju 1.25.0 (Last verified commit changes).
* d/tests/* Removed init-system switch because Juju s
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
Uploaded to Xenial. It's making its way through xenial-proposed now but
will then wait on the upstream release and then we can remove the block-
proposed tag.
I made a couple of minor changes to the Xenial upload. There was a
syntax error in debian/copyright that lintian picked up. I also dropped
** Also affects: juju-core (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Wily)
Status: New => Triaged
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubunt
block-proposed needed as 1.25.0 is not yet released upstream and will
break in Ubuntu until it is.
** Tags added: block-proposed
--
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/15105
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have
** 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
19 matches
Mail list logo
