[needs-packaging] Juju 1.25.0 is not in xenial and wily

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 and revised the tests to not switch init systems, nor attempt to claim
a non-systemd releases is a future release.

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 go package.
  Juju can still use the -dev package in Ubuntu, but everyone will benefit
  if the race-condition fix were packaged. Martin Packman is working on a new
  package for Debian that we can update in Ubuntu as needed.

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.

*** 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 Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

block-proposed needed as 1.25.0 is not yet released upstream and will break in Ubuntu until it is.

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 the changelog entry for .pc as that gets removed by dpkg-source before upload anyway.

You can see these at https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-core/+git/packaging/ - please pull them in for future uploads.

Also uploaded to Wily and that is now pending SRU team review.

I made one minor change to the Wily upload. The changelog needed to be based on the Xenial branch's changelog with just one additional entry to cover the backport, so I added that. I presume this got confused/became necessary when Xenial was opened after you prepared the Wily branch.

I've put my Wily branch in https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-core/+git/packaging/log/?h=basak/wily pending SRU team acceptance.

I removed block-proposed because Juju 1.25.0 is relesed upstream now.

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 supports upstart
    and systemd. Do not test future on non-systemd releases.

 -- <email address hidden> (Curtis C. Hovey) Fri, 23 Oct 2015 18:30:04 +0000

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 currently has).
Upgrades of clients and environments from juju 1.24.7 to 1.25.0 work without
need of configuration changes. Xenial juju 1.25.0 can manually provision
environments and add-machines.

I restored verification-needed. This package is not in wily yet and needs verification.

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. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

FWIW: You can also namespace verification using 'verification-(needed|done)-$series'.

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 has).
Upgrades of clients and environments from juju 1.24.7 to 1.25.0 work without
need of configuration changes. wily juju 1.25.0 can manually provision
environments and add-machines.

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 <email address hidden> Thu, 29 Oct 2015 11:25:46 +0000

The verification of the Stable Release Update for juju-core has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.