From jclift at redhat.com Wed Aug 19 15:15:51 2015 Content-Type: multipart/mixed; boundary="===============4095880779552336752==" MIME-Version: 1.0 From: Justin Clift To: aeolus-devel at lists.fedorahosted.org Subject: Re: rubygem-right_aws dependency problem Date: Mon, 27 Jun 2011 21:15:47 +1000 Message-ID: <920C163F-1FB5-48CD-8987-29CB6221B4F2@redhat.com> In-Reply-To: 1309171406.5419.16.camel@melon.watzmann.net --===============4095880779552336752== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 re= quires 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 check= s specifically for the presence of the older package. It barfs if the new one is used ins= tead: err: /Stage[main]/Aeolus::Deltacloud::Core/Package[rubygem-deltacloud-c= ore]/ensure: change from absent to present failed: RPMs must specify a = package source at /usr/share/aeolus-configure/modules/aeolus_recipe/manifes= ts/deltacloud.pp:8 Which then seems to have follow on probs. But, this is actually pretty minor, because we have an easy workaround in p= lace using --exclude, already on the website. We're releasing the new 0.3.0 version of Aeolus soon anyway, so none of thi= s is worth putting further time into. :) Regards and best wishes, Justin Clift -- Aeolus Community Manager http://www.aeolusproject.org --===============4095880779552336752==--