You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Amogh Vasekar <am...@citrix.com> on 2014/01/03 20:46:11 UTC

vhd-util on git

Hi,

I encountered a conflict while pulling in a branch, and noticed vhd-util
in the CS code base :
https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor/xens
erver/vhd-util

Wasn't there a licensing issue with vhd-util being in the code base?

Thanks,
Amogh


Re: vhd-util on git

Posted by Daan Hoogland <da...@gmail.com>.
On Fri, Jan 3, 2014 at 8:46 PM, Amogh Vasekar <am...@citrix.com> wrote:
> https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor/xens
> erver/vhd-util


github is not the authoritive source for acs. This is a mirror someone
made and forgot to sync. So that is probably the reason vhd-util is
still in there.

Re: vhd-util on git

Posted by David Nalley <da...@gnsa.us>.
On Fri, Jan 3, 2014 at 4:05 PM, Alex Huang <Al...@citrix.com> wrote:
> I was in Cambridge before the ccceu13 and worked with the XS team on this.  They're working on a patch release to 6.2 that will include everything we need in vhd-util, which will remove this dependency.  It's expected end of Jan/start of feb.  Unfortunately, it's too big an effort for them to backport it to all previous releases but at least going forward, we will be rid of this problem.
>


That's outstanding news to hear.

Thanks Alex,

--David

RE: vhd-util on git

Posted by Alex Huang <Al...@citrix.com>.
I was in Cambridge before the ccceu13 and worked with the XS team on this.  They're working on a patch release to 6.2 that will include everything we need in vhd-util, which will remove this dependency.  It's expected end of Jan/start of feb.  Unfortunately, it's too big an effort for them to backport it to all previous releases but at least going forward, we will be rid of this problem.

--Alex

> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Friday, January 3, 2014 12:26 PM
> To: dev@cloudstack.apache.org; Nguyen Anh Tu
> Subject: Re: vhd-util on git
> 
> On Fri, Jan 3, 2014 at 2:46 PM, Amogh Vasekar <am...@citrix.com>
> wrote:
> > Hi,
> >
> > I encountered a conflict while pulling in a branch, and noticed
> > vhd-util in the CS code base :
> >
> https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor
> > /xens
> > erver/vhd-util
> >
> > Wasn't there a licensing issue with vhd-util being in the code base?
> >
> > Thanks,
> > Amogh
> >
> 
> There is indeed a licensing issue. It was in the codebase in 2011 and removed
> in 2012 as we readied for the first ASF release.
> 
> For a history, see:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=history;f=scripts/vm/hypervisor
> /xenserver/vhd-
> util;h=46d62dd44d9224b9b8c5c11f05bb789473ddc1a4;hb=HEAD
> 
> Tuna:
> 
> Please revert this commit. vhd-util is both a binary and licensed in a manner
> that makes it impossible from an ASF policy perspective to retain in our
> version control or ship in a release - both of which are problematic.
> 
> --David

Re: vhd-util on git

Posted by Nguyen Anh Tu <tu...@apache.org>.
Okie, so I just made a new commit ecale97b to remove vhd-util.

Thanks David,

--Tuna

Sent from my GT-N7000
On Jan 15, 2014 1:24 AM, "David Nalley" <da...@gnsa.us> wrote:

> You can always git revert, but it will revert the entire commit. Aside
> from that you can't change history (ASF git repos are set up to not
> permit it)
>
> --David
>
> On Tue, Jan 14, 2014 at 1:00 PM, Nguyen Anh Tu <tu...@apache.org> wrote:
> >
> > On Wed, Jan 15, 2014 at 12:58 AM, David Nalley <da...@gnsa.us> wrote:
> >>
> >> Easiest way is probably git rm vhd-util and then commit that.
> >
> >
> > Yes, sure. But I don't want to make some noise with that. You know, add
> > vhd-util in a commit and then remove in another commit. Edit the previous
> > commit should be better.
> >
> > --Tuna
>

Re: vhd-util on git

Posted by Nguyen Anh Tu <tu...@apache.org>.
Opps... I thought I removed vhd-util from the commit. Will do in next
monday, David. I'm travelling and the internet connection is terrible here.

Thanks,

--Tuna

Sent from my GT-N7000
On Jan 4, 2014 3:26 AM, "David Nalley" <da...@gnsa.us> wrote:

> On Fri, Jan 3, 2014 at 2:46 PM, Amogh Vasekar <am...@citrix.com>
> wrote:
> > Hi,
> >
> > I encountered a conflict while pulling in a branch, and noticed vhd-util
> > in the CS code base :
> >
> https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor/xens
> > erver/vhd-util
> >
> > Wasn't there a licensing issue with vhd-util being in the code base?
> >
> > Thanks,
> > Amogh
> >
>
> There is indeed a licensing issue. It was in the codebase in 2011 and
> removed in 2012 as we readied for the first ASF release.
>
> For a history, see:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=history;f=scripts/vm/hypervisor/xenserver/vhd-util;h=46d62dd44d9224b9b8c5c11f05bb789473ddc1a4;hb=HEAD
>
> Tuna:
>
> Please revert this commit. vhd-util is both a binary and licensed in a
> manner that makes it impossible from an ASF policy perspective to
> retain in our version control or ship in a release - both of which are
> problematic.
>
> --David
>

Re: vhd-util on git

Posted by David Nalley <da...@gnsa.us>.
On Fri, Jan 3, 2014 at 2:46 PM, Amogh Vasekar <am...@citrix.com> wrote:
> Hi,
>
> I encountered a conflict while pulling in a branch, and noticed vhd-util
> in the CS code base :
> https://github.com/apache/cloudstack/blob/master/scripts/vm/hypervisor/xens
> erver/vhd-util
>
> Wasn't there a licensing issue with vhd-util being in the code base?
>
> Thanks,
> Amogh
>

There is indeed a licensing issue. It was in the codebase in 2011 and
removed in 2012 as we readied for the first ASF release.

For a history, see:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=history;f=scripts/vm/hypervisor/xenserver/vhd-util;h=46d62dd44d9224b9b8c5c11f05bb789473ddc1a4;hb=HEAD

Tuna:

Please revert this commit. vhd-util is both a binary and licensed in a
manner that makes it impossible from an ASF policy perspective to
retain in our version control or ship in a release - both of which are
problematic.

--David