[SRU] yui3 to precise

Bug #1084141 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yui3 (Ubuntu)
High
Unassigned
Precise
High
Unassigned

Bug Description

[Impact]
As part of the MAAS Next Steps bluepring [1], YUI3 is a required dependency for MAAS. In Precise, the 'yui3' libraries are being shipped with 'maas' source. This was done because such libraries weren't in the archives. How that they are, it is imperative for us to be able to separate these from the 'maas' source and SRU these to Precise.

[Test Case]
1. Install maas (ppa:maas-maintainers/experimental)
2. Make sure it pulls yui3 libraries
3. Run MAAS
4. Check that no WebUI issues appear.

[Regression potential]
Minimal. The libraries don't pull any build-deps other than debhelper and have no Depends (other than between the yui3 libraries). This has been tested in quantal as well as precise extensively.

[1]: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-maas-next-steps

Changed in yui3 (Ubuntu):
importance: Undecided → High
description: updated
Changed in yui3 (Ubuntu):
status: New → Fix Released
Changed in yui3 (Ubuntu Precise):
importance: Undecided → High
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Based on the feedback from the Technical Board discussion, we are no longer going to SRU yui3 to Precise, but continue to ship it with the maas package.

Changed in yui3 (Ubuntu Precise):
status: New → Invalid
status: Invalid → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers