It seems that in a Crowbar installation, the nodes will only have access to
Crowbar's package repo.  Crowbar's package repo wont have updated packages
from upstream.  The Crowbar repo will only have what was on the ISO.  So,
"upgrade" makes no sense.. unless the packages themselves have responses to
"upgrade" which are so different from "install" as to make the product non
functional.
I wrote the swift recipes with "update" because of such an error.  But
that's ancient and probably should be changed to "install."



On Mon, Jun 17, 2013 at 5:22 PM, <arkady_kanev...@dell.com> wrote:

> Vincent,****
>
> I apologize for delaying the merge of your fixed across the board for all
> BC to install but it is not clear what was agreed to at the last week
> design call.****
>
> We do not have minutes so it is hard to find out what was an agreement.***
> *
>
> ** **
>
> Can we review it on Thursday community call?****
>
> Thanks,****
>
> Arkady****
>
> ** **
>
> [image: Description: Description: Description: dell]****
>
> *Arkady Kanevsky, Ph.D.*****
>
> Director of SW Development****
>
> Enterprise Solution Group****
>
> +1 512 723 5264 | arkady_kanev...@dell.com****
>
> ** **
>
> ** **
>
> _______________________________________________
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/
>



-- 
Judd Maltin
T: 917-882-1270
F: 501-694-7809
what could possibly go wrong?

<<image001.jpg>>

_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Reply via email to