| 2012-11-28 16:55:50 |
Andres Rodriguez |
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. |
[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 |
|
