[needs-packaging] 1.24.6 is not packaged in 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-core/vivid

Don't need block-proposed tag as this is only for the development release which won't be touched by the fix for this bug.

Uploaded to vivid-proposed with just adjustments to debian/changelog. See https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-core/+git/packaging/log/?h=69fd354a52e8df483aef3a5b18885ad50bf09427. Now awaiting SRU team review.

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.6-0ubuntu1~15.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!

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

This bug was fixed in the package juju-core - 1.24.6-0ubuntu1~15.04.1

---------------
juju-core (1.24.6-0ubuntu1~15.04.1) vivid; urgency=medium

  * Backport of 1.24.6 from wily. (LP: #1500916, #1497087)

 -- <email address hidden> (Curtis C. Hovey) Tue, 29 Sep 2015 19:43:29 +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.