[SRU] raphael new upstream release (2.1.0)

Bug #1084146 reported by Andres Rodriguez
This bug affects 1 person
Affects Status Importance Assigned to Milestone
raphael (Ubuntu)

Bug Description

As part of the MAAS Next Steps bluepring [1], raphael 2.1.0 is a required dependency for MAAS. In Precise, the 'raphael' library is being shipped with 'maas' source. This was done because the library version required wasn't in the archives. However, now that it is, it is imperative for us to be able to separate these from the 'maas' source and SRU it to Precise.

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

[Regression potential]
Minimal. The library only has one build-depends other than debhelper and have no Depends. This package has been tested in Precise and was built against its build-depends in precise.

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

description: updated
Changed in raphael (Ubuntu):
status: New → Fix Released
Changed in raphael (Ubuntu Precise):
importance: Undecided → High
summary: - [SRU] raphael 2.1.0 to precise
+ [SRU] raphael new upstream release (2.1.0)
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Hello! This upload is not appropriate as per the normal SRU policy. If we're going to ship a new upstream release in an SRU without any bug fixes enumerated, it will need an exception from the Tech Board.

Revision history for this message
Steve Langasek (vorlon) wrote :

As Clint says, this doesn't fit the SRU policy. If the raphael source is already bundled in the maas source package in precise, we should keep it this way; I don't see any reason that it's worth splitting this out, clobbering the existing raphael package in precise, in an SRU when keeping it in the maas source requires much less verification effort.

Rejecting from the queue and marking this 'wontfix'.

Changed in raphael (Ubuntu Precise):
status: New → 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