Is the hash right?
On 4.1 branch:
# git cherry-pick 6317f0bd33605c4943dcf472415e9d5c7a443d93
fatal: bad object 6317f0bd33605c4943dcf472415e9d5c7a443d93
On Fri, Mar 01, 2013 at 05:58:34PM -0700, Marcus Sorensen wrote:
It can go under CLOUDSTACK-1201, since it's the same issue, just in
the
On Fri, Mar 01, 2013 at 05:58:34PM -0700, Marcus Sorensen wrote:
It can go under CLOUDSTACK-1201, since it's the same issue, just in
the case of upgrade rather than fresh install.
Done. Thanks Marcus.
On Fri, Mar 1, 2013 at 5:54 PM, Marcus Sorensen shadow...@gmail.com wrote:
I can create
This adds to cloud.spec post installation of cloudstack-management. It
updates the cloud user's home dir to the new location if it finds that
the cloud user's home is set to the old location.
master 6317f0bd33605c4943dcf472415e9d5c7a443d93
applies cleanly to 4.1 as of now.
Bug ID?
On Mar 1, 2013, at 7:51 PM, Marcus Sorensen shadow...@gmail.com wrote:
This adds to cloud.spec post installation of cloudstack-management. It
updates the cloud user's home dir to the new location if it finds that
the cloud user's home is set to the old location.
master
I can create one. I just didn't realize we needed a bug ID for every
time we touch the code. I'll look and see if there's already a general
one about making RPM builds work.
On Fri, Mar 1, 2013 at 5:51 PM, Chip Childers chip.child...@sungard.com wrote:
Bug ID?
On Mar 1, 2013, at 7:51 PM,
It can go under CLOUDSTACK-1201, since it's the same issue, just in
the case of upgrade rather than fresh install.
On Fri, Mar 1, 2013 at 5:54 PM, Marcus Sorensen shadow...@gmail.com wrote:
I can create one. I just didn't realize we needed a bug ID for every
time we touch the code. I'll look
On Fri, Mar 01, 2013 at 05:58:34PM -0700, Marcus Sorensen wrote:
It can go under CLOUDSTACK-1201, since it's the same issue, just in
the case of upgrade rather than fresh install.
I asked what the bug ID was, because we want to limit to blocker fixes or
critical fixes (which have low risk).
