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'.
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'.