[needs-packaging] 1.22.6 is not packaged in trusty

Bug #1469744 reported by Curtis Hovey
30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

We're now in a position to have 1.22.6 enter trusty-proposed.

[SRU Information]

juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.

[Devel Fix]

[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. The long-term plan for wily is to put 1.24.x in the release pocket because it supported systemd.

[Stable Fix]

[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review. Will remove the block-proposed tag when verification has passed, and then this update should migrate to vivid.

[Pre-QA tasks]

[rbasak] Upload to the development release (wily-proposed): DONE
[rbasak] Upload to the current LTS release (trusty-proposed): DONE

[QA Status]

Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.

[sinzui] Upstream QA test against Wily: DONE
[sinzui] Upstream QA test against Trusty: DONE
[sinzui] Upstream release process complete: DONE

Manual tests required:

[sinzui] Test juju-quickstart against wily-proposed: DONE
[sinzui] Test juju-deployer against wily-proposed: DONE
[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE

The following stakeholders have expressed an interest in performing their own tests and we will wait for a (timely) acknowledgement from them before removing the -proposed blocks. If you also have an interest in testing new Juju releases before they land in an SRU, then please comment in this bug.

[Beret] Landscape team QA: not-needed

Revision history for this message
Curtis Hovey (sinzui) wrote :

Hi Robie.

I opened a new bug to track the specific request of placing 1.22.6 into trusty. I have prepared a new source package branch using the trusty 1.22.5 branch I proposed for bug 1462001.

We can see src/github.com/juju/txn changed; review the change for copyright issues. The only change is two files were updated to LGPL to match the txn project's licence. This change is in response to our audit for 1.22.5.

Revision history for this message
Curtis Hovey (sinzui) wrote :

This is the diff from 1.22.5 to 1.22.6 http://pastebin.ubuntu.com/11793455/

Curtis Hovey (sinzui)
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core (Ubuntu Trusty):
status: New → Confirmed
Changed in juju-core (Ubuntu):
status: New → Confirmed
Revision history for this message
Felipe Reyes (freyes) wrote :

Curtis, is this version going to be proposed for vivid as well to make sure there is a proper upgrade path across series?

Revision history for this message
Curtis Hovey (sinzui) wrote :

I am preparing a branch for 1.22.6 for wily. the local test did not pass and I am looking into why lxc-br0 is missing after the adt image is rebooted with upstart installed.

Revision history for this message
Curtis Hovey (sinzui) wrote :

I prepared a source package for juju 1.22.6 in wily
    lp:~sinzui/ubuntu/wily/juju-core/wily-1.22.6

Like the trusty package, I used the 1.22.5 as the base. The diff contains the expected copyright correct that we reported was an issue when reviewing 1.22.5
    http://pastebin.ubuntu.com/11811316/

This package is is verified to work on a working wily, but the autopkgtest fails at this hour with "--apt-pocket proposed -U" because lxc is broken in wily. The machine fails to provide lxcbr0. I have verified that the fix for wily is to set
    LXC_DHCP_CONFILE="/dev/null"
in
    /usr/lib/x86_64-linux-gnu/lxc/lxc-net

Revision history for this message
Curtis Hovey (sinzui) wrote :

Is there anything blocking 1.22.6 going into wily and trusty. I believe I provided two SPB that I believe are good.

Curtis Hovey (sinzui)
description: updated
Robie Basak (racb)
description: updated
Revision history for this message
Robie Basak (racb) wrote :

Uploaded to wily-proposed (held by block-proposed) and to trusty-proposed (in unapproved).

Changed in juju-core (Ubuntu):
status: Confirmed → Fix Committed
Changed in juju-core (Ubuntu Trusty):
status: Confirmed → In Progress
Curtis Hovey (sinzui)
description: updated
Curtis Hovey (sinzui)
description: updated
Revision history for this message
Curtis Hovey (sinzui) wrote :

Ubuntu juju 1.22.6 on wily is compatible with 1.22.x from upstream Juju. It is suitable deploying and maintaining environments in public and private clouds. Juju is compatible with the versions of quickstart (and deployer) provide by Ubuntu main.

Note that 1.22.6 does not support systemd, so the case of using local-provider for testing and charm development is not supported. For this case, we recommend development using a kvm trusty vm.

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

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

Changed in juju-core (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Curtis Hovey (sinzui) wrote :

I certify Juju 1.22.6 is compatible with trusty previous jujus and with the Juju ecosystem at large.

Ubuntu juju 1.22.6 on trusty is compatible with 1.22.x from upstream Juju. It is suitable deploying and maintaining environments in public and private clouds. Juju is compatible with the versions of quickstart (and deployer) provide by Ubuntu main. Upgrades from 1.18.4 and 1.20.11 work fine. The version is suitable for local testing and charm development.

This version addresses the aws, azure, and joyent degradations that trusty users have experienced as public clouds introduced new regions, AZs, and networks. For example. Deploying the landscape-scalable bundle will likely fail using 1.20.11 un AWS because of the high probability of getting an unsupported AZ. Juju 1.22.6 handle the situation.

Curtis Hovey (sinzui)
description: updated
Curtis Hovey (sinzui)
tags: removed: block-proposed
Robie Basak (racb)
description: updated
Curtis Hovey (sinzui)
description: updated
description: updated
tags: added: verification-done
removed: verification-needed
Curtis Hovey (sinzui)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 1.22.6-0ubuntu1~14.04.1

---------------
juju-core (1.22.6-0ubuntu1~14.04.1) trusty; urgency=medium

  * No change backport to 14.04 (LP: #1469744). This results in the
    following packaging delta from the previous 1.20.11-0ubuntu0.14.04.1
    in trusty-updates:
    - distro-info added and libgo5 removed from Build-Depends.
    - Standards-Version bumped.
    - cloud-image-utils | cloud-utils added to juju-local Depends.
    - d/copyright updated.
    - dep8 tests updated.

 -- Robie Basak <email address hidden> Wed, 15 Jul 2015 13:09:07 +0000

Changed in juju-core (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

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.

Revision history for this message
Robie Basak (racb) wrote :

Fixed in Wily in1.22.6-0ubuntu1 - changelog message didn't mention this bug.

Changed in juju-core (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.