[needs-packaging] Juju 1.25.5 is not in wily and trusty

*** 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.

I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for wily.

    https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h=ubuntu-wily

This is *not* a no-change backport because the source package was
renamed to juju-core-1 in xenial. Most the the debian/ changes relate to
the rename. I made the minimal change to wily's debian/ dir for this
backport. plus two small changes:

    * d/copyright: Backported with changes to src
      Updated info for src/gopkg.in/juju/charm.v5/* to now match
      commit 84c8fe478fa1b1e67eb552831de5fd2603085c51
    * d/control: Added juju-1 to conflicts as a courtesy to users
      of alternate packages.

Note that the copyright file was was written by Adam Conrad
for Xenial for readability. Cases where the copyright holders added
their names to common licences were removed as the inline licences.

Attached are both a diff of the minimal debian changes and a larger
diff of between the xenial source tree and the wily source tree. The
later shows the source has not changed and that the majority of debian
differences are because the different package names.

I prepared a backport of juju-core-1 1.25.5-0ubuntu3 for trusty.

    https://git.launchpad.net/~sinzui/ubuntu/+source/juju-core/log/?h=ubuntu-trusty

This is *not* a no-change backport because the source package was
renamed to juju-core-1 in xenial. Most the the debian/ changes relate to
the rename. I made the minimal change to trusty's debian/ dir for this
backport. plus two small changes:

    * d/copyright: Backported with changes to src
      Updated info for src/gopkg.in/juju/charm.v5/* to now match
      commit 84c8fe478fa1b1e67eb552831de5fd2603085c51
    * d/control: Added juju-1 to conflicts as a courtesy to users
      of alternate packages.

Note that the copyright file was was written by Adam Conrad
for Xenial for readability. Cases where the copyright holders added
their names to common licences were removed as the inline licences.

Attached are both a diff of the minimal debian changes and a larger
diff of between the xenial source tree and the trusty source tree. The
later shows the source has not changed and that the majority of debian
differences are because the different package names.

^ Both the wily and trusty packages were verified to pass their respective ADT tests. The repo has the pristine-tar files.

src:juju-core-1 1.25.5-0ubuntu3 is in Yakkety, so notionally Fix Released but there seems little point to have a task just for that. src:juju-core is thus Invalid for the development release and needs tasks for Trusty and Wily.

Uploaded to Trusty and Wily. Nothing to flag on review - thanks Curtis.

I did note that debian/copyright is different (presumably updated, based on your changelog message?) in your backports when compared to debian/copyright in src:juju-core-1 in Yakkety. Not worth blocking an SRU, but please make sure this is also updated in Yakkety in the next upload. Smaller diffs -> happier reviewers :)

Thank you also for the git trees. This saved me a ton of time.

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.5-0ubuntu3~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!

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.25.5-0ubuntu3~14.04.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!

The juju-qa team tests of 1.25.5-0ubuntu3~15.10.1 pass.

The juju is compatible with the agents in streams. It is fit for cloud deployments. It is suitable for devel and testing using the local-provider. the manual-provider can be used in production scenarios. The juju is compatible with the juju-deployer and juju-qquickstart in wily-release/wily-updates

The juju-qa team tests of 1.25.5-0ubuntu3~14.04.1 in trusty-proposed pass.

The juju is compatible with the agents in streams. It is fit for cloud deployments.It is suitable for devel and testing using the local-provider. the manual-provider can be used in production scenarios. The juju is compatible with the juju-deployer and juju-quickstart in trusty-release/trusty-updates

This bug was fixed in the package juju-core - 1.25.5-0ubuntu3~14.04.1

---------------
juju-core (1.25.5-0ubuntu3~14.04.1) trusty; urgency=medium

  * Backport of juju-core-1_1.25.5-0ubuntu3 to 14.04 (Lp: #1556981).
  * As the packages were renamed to juju-core-1 and juju-1, most changes
    to d/ are not backported.
    * d/copyright: Backported with changes to src
      Updated info for src/gopkg.in/juju/charm.v5/* to now match
      commit 84c8fe478fa1b1e67eb552831de5fd2603085c51
    * d/control: Added juju-1 to conflicts as a courtesy to users
      of alternate packages.

 -- <email address hidden> (Curtis C. Hovey) Fri, 13 May 2016 13:34:09 +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.

This bug was fixed in the package juju-core - 1.25.5-0ubuntu3~15.10.1

---------------
juju-core (1.25.5-0ubuntu3~15.10.1) wily; urgency=medium

  * Backport of juju-core-1_1.25.5-0ubuntu3 to 15.10 (Lp: #1556981).
  * As the packages were renamed to juju-core-1 and juju-1, most changes
    to d/ are not backported.
    * d/copyright: Backported with changes to src
      Updated info for src/gopkg.in/juju/charm.v5/* to now match
      commit 84c8fe478fa1b1e67eb552831de5fd2603085c51
    * d/control: Added juju-1 to conflicts as a courtesy to users
      of alternate packages.

 -- <email address hidden> (Curtis C. Hovey) Wed, 11 May 2016 18:21:51 +0000