On 27/06/2011, at 8:43 PM, David Lutterkort wrote:
On Mon, 2011-06-27 at 19:08 +1000, Justin Clift wrote:
> Which we need to keep using, as the 0.2.0 version of aeolus-configure requires it.
(it fails
> is we use the newer deltacloud-core package).
What exactly goes wrong with newer deltacloud-core ?
Heh, it's not a problem with deltacloud-core itself.
It's just that the (really old now) 0.2.0 release of aeolus-configure checks
specifically
for the presence of the older package. It barfs if the new one is used instead:
err: /Stage[main]/<a
href="Aeolus::Deltacloud::Core/Package[rubygem-deltacloud-core]/ensure">Aeolus::Deltacloud::Core/Package[rubygem-deltacloud-core]/ensure</a>:
change from absent to present failed: RPMs must specify a package source at
/usr/share/aeolus-configure/modules/aeolus_recipe/manifests/deltacloud.pp:8
Which then seems to have follow on probs.
But, this is actually pretty minor, because we have an easy workaround in place using
--exclude,
already on the website.
We're releasing the new 0.3.0 version of Aeolus soon anyway, so none of this is worth
putting
further time into. :)
Regards and best wishes,
Justin Clift
--
Aeolus Community Manager
http://www.aeolusproject.org