[jira] [Commented] (TC-85) Should use "dest_ip" instead of "dest_domain" in "parent.config" and "cache.config" when ofqdn is ip

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800300#comment-15800300
 ] 

ASF GitHub Bot commented on TC-85:
--

GitHub user jifyang opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/159

Should use "dest_ip" instead of "dest_domain" in "parent.config" and …

…"cache.config" when ofqdn is ip

Fix the issue #TC-85.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jifyang/incubator-trafficcontrol dest_ip

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/159.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #159


commit 0328fcc2993d834d50bbf9b8cbd76702e9483c1d
Author: Jifeng Yang 
Date:   2017-01-05T16:13:24Z

Should use "dest_ip" instead of "dest_domain" in "parent.config" and 
"cache.config" when ofqdn is ip




> Should use "dest_ip" instead of "dest_domain" in "parent.config" and 
> "cache.config" when ofqdn is ip
> 
>
> Key: TC-85
> URL: https://issues.apache.org/jira/browse/TC-85
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jifeng Yang
>
> Should use "dest_ip" instead of "dest_domain" in "parent.config" and 
> "cache.config" when ofqdn is ip.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol pull request #159: Should use "dest_ip" instead of ...

2017-01-04 Thread jifyang
GitHub user jifyang opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/159

Should use "dest_ip" instead of "dest_domain" in "parent.config" and …

…"cache.config" when ofqdn is ip

Fix the issue #TC-85.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jifyang/incubator-trafficcontrol dest_ip

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/159.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #159


commit 0328fcc2993d834d50bbf9b8cbd76702e9483c1d
Author: Jifeng Yang 
Date:   2017-01-05T16:13:24Z

Should use "dest_ip" instead of "dest_domain" in "parent.config" and 
"cache.config" when ofqdn is ip




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Created] (TC-85) Should use "dest_ip" instead of "dest_domain" in "parent.config" and "cache.config" when ofqdn is ip

2017-01-04 Thread Jifeng Yang (JIRA)
Jifeng Yang created TC-85:
-

 Summary: Should use "dest_ip" instead of "dest_domain" in 
"parent.config" and "cache.config" when ofqdn is ip
 Key: TC-85
 URL: https://issues.apache.org/jira/browse/TC-85
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Reporter: Jifeng Yang


Should use "dest_ip" instead of "dest_domain" in "parent.config" and 
"cache.config" when ofqdn is ip.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol pull request #158: Adds some missing crud api tests

2017-01-04 Thread mitchell852
GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/158

Adds some missing crud api tests



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol api-tests

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/158.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #158


commit 5c477410fb75e9930aa24e4a256389bcc66e3e20
Author: Jeremy Mitchell 
Date:   2017-01-04T21:34:59Z

adds crud tests for asn api

commit 1c6e3c483327d3d5c03b8820685d608786ff2210
Author: Jeremy Mitchell 
Date:   2017-01-04T21:52:08Z

adds missing crud tests for cdn api

commit ca0faff56ba05ad5db66a6329176b3660e9d1008
Author: Jeremy Mitchell 
Date:   2017-01-05T02:22:44Z

adds some more missing api crud tests




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799710#comment-15799710
 ] 

ASF GitHub Bot commented on TC-84:
--

Github user dangogh closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/157


> compile goose from source on traffic_ops install
> 
>
> Key: TC-84
> URL: https://issues.apache.org/jira/browse/TC-84
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 1.8.0
>
>
> Apache TMC wants us to eliminate the goose binary from release.   The rpm 
> install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799709#comment-15799709
 ] 

ASF GitHub Bot commented on TC-84:
--

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
yep -- catch-22..   I'll get build instructions set up that details this 
instead..


> compile goose from source on traffic_ops install
> 
>
> Key: TC-84
> URL: https://issues.apache.org/jira/browse/TC-84
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 1.8.0
>
>
> Apache TMC wants us to eliminate the goose binary from release.   The rpm 
> install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol pull request #157: [TC-84] compiles goose from sour...

2017-01-04 Thread dangogh
Github user dangogh closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/157


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-trafficcontrol issue #157: [TC-84] compiles goose from source; ins...

2017-01-04 Thread dangogh
Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
yep -- catch-22..   I'll get build instructions set up that details this 
instead..


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799619#comment-15799619
 ] 

ASF GitHub Bot commented on TC-84:
--

Github user mtorluemke commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
Yeah, 715 files and almost 390k lines seems excessive. On the other hand, 
"go get" requires more babysitting over time. Feels like we should choose 
either of the two evils in the short-term, and add a longer-term item to 
revisit our schema migration strategy.


> compile goose from source on traffic_ops install
> 
>
> Key: TC-84
> URL: https://issues.apache.org/jira/browse/TC-84
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 1.8.0
>
>
> Apache TMC wants us to eliminate the goose binary from release.   The rpm 
> install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol issue #157: [TC-84] compiles goose from source; ins...

2017-01-04 Thread mtorluemke
Github user mtorluemke commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
Yeah, 715 files and almost 390k lines seems excessive. On the other hand, 
"go get" requires more babysitting over time. Feels like we should choose 
either of the two evils in the short-term, and add a longer-term item to 
revisit our schema migration strategy.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799434#comment-15799434
 ] 

ASF GitHub Bot commented on TC-84:
--

GitHub user dangogh opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/157

[TC-84] compiles goose from source; installs cpan modules during rpm install

This is needed for 1.8 -- apache compliance does not allow release of goose 
binary

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dangogh/incubator-trafficcontrol vendor-goose

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/157.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #157


commit 4bbcffd91b045f5f8da3f0ab8a56f712ad402d12
Author: Dan Kirkwood 
Date:   2017-01-04T20:02:13Z

add goose source to build during install




> compile goose from source on traffic_ops install
> 
>
> Key: TC-84
> URL: https://issues.apache.org/jira/browse/TC-84
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 1.8.0
>
>
> Apache TMC wants us to eliminate the goose binary from release.   The rpm 
> install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799441#comment-15799441
 ] 

ASF GitHub Bot commented on TC-84:
--

Github user knutsel commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
Do we have to add all these to our repo? Can't we just say you have to "go 
get" them before you do the build? And do the same in the installer?


> compile goose from source on traffic_ops install
> 
>
> Key: TC-84
> URL: https://issues.apache.org/jira/browse/TC-84
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 1.8.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
> Fix For: 1.8.0
>
>
> Apache TMC wants us to eliminate the goose binary from release.   The rpm 
> install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol issue #157: [TC-84] compiles goose from source; ins...

2017-01-04 Thread knutsel
Github user knutsel commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/157
  
Do we have to add all these to our repo? Can't we just say you have to "go 
get" them before you do the build? And do the same in the installer?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] incubator-trafficcontrol pull request #157: [TC-84] compiles goose from sour...

2017-01-04 Thread dangogh
GitHub user dangogh opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/157

[TC-84] compiles goose from source; installs cpan modules during rpm install

This is needed for 1.8 -- apache compliance does not allow release of goose 
binary

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dangogh/incubator-trafficcontrol vendor-goose

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/157.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #157


commit 4bbcffd91b045f5f8da3f0ab8a56f712ad402d12
Author: Dan Kirkwood 
Date:   2017-01-04T20:02:13Z

add goose source to build during install




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Created] (TC-84) compile goose from source on traffic_ops install

2017-01-04 Thread Dan Kirkwood (JIRA)
Dan Kirkwood created TC-84:
--

 Summary: compile goose from source on traffic_ops install
 Key: TC-84
 URL: https://issues.apache.org/jira/browse/TC-84
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Affects Versions: 1.8.0
Reporter: Dan Kirkwood
Assignee: Dan Kirkwood
 Fix For: 1.8.0


Apache TMC wants us to eliminate the goose binary from release.   The rpm 
install can install from source,  which should be acceptable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (TC-80) Add api/version/cachegroups/:id/parameters endpoint

2017-01-04 Thread Jeremy Mitchell (JIRA)

 [ 
https://issues.apache.org/jira/browse/TC-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Mitchell resolved TC-80.
---
   Resolution: Fixed
Fix Version/s: 1.9.0

> Add api/version/cachegroups/:id/parameters endpoint
> ---
>
> Key: TC-80
> URL: https://issues.apache.org/jira/browse/TC-80
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Provide the ability to fetch cachegroup parameters through the api such as
> api/version/cachegroups/:id/parameters
> Also, while you're in there, provide the ability to fetch cachegroup asns 
> through the api such as:
> api/version/asns?cachegroup=x
> and filter phys locations by region like:
> api/version/physLocations?region=x



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (TC-81) Add additional filters to collection apis

2017-01-04 Thread Jeremy Mitchell (JIRA)

 [ 
https://issues.apache.org/jira/browse/TC-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Mitchell resolved TC-81.
---
   Resolution: Fixed
Fix Version/s: 1.9.0

> Add additional filters to collection apis
> -
>
> Key: TC-81
> URL: https://issues.apache.org/jira/browse/TC-81
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Add the ability to filter the following collections as follows:
> /api/deliveryservices/:id/servers <-- retrieve all edge servers assigned to a 
> ds
> /api/servers/:id/deliveryservices <-- retrieve all ds's assigend to a server
> /api/parameters/:id/profiles <-- retrieve all profiles assigned to a parameter
> /api/users/:id/deliveryservices <-- retrieve all ds's assigned to a user
> /api/deliveryservices?cdn=x <-- to retrieve a cdn's ds's
> /api/regions?division=x <-- to retrieve a division's regions
> /api/servers?physLocation=x <-- to retrieve a phys location's servers
> /api/cachegroups?type=x <-- to retrieve cachegroups by type
> /api/deliveryservices?type=x <-- to retrieve deliveryservices by type
> The api already provides the ability to:
> - retrieve a cachegroup's asns
> - retrieve a cachegroup's parameters
> - retrieve a cachegroup's servers
> - retrieve a cdn's servers
> - retrieve a profile's parameters
> - retrieve a profile's servers
> - retrieve a region's phys locations
> By adding these additional filters, it provides the ability to navigate the 
> relationships in the database (i.e. provides drill-down capabilities)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (TC-39) LICENSE file is incomplete

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798811#comment-15798811
 ] 

ASF GitHub Bot commented on TC-39:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/156


> LICENSE file is incomplete
> --
>
> Key: TC-39
> URL: https://issues.apache.org/jira/browse/TC-39
> Project: Traffic Control
>  Issue Type: Bug
>Reporter: Eric Friedrich
>Priority: Minor
> Fix For: 1.8.0
>
>
> Our LICENSE file only includes Apache License, but not the licenses of all 
> our bundled dependencies. 
> From 
> https://incubator.apache.org/guides/releasemanagement.html#best-practice-license:
> bq. "All the licenses on all the files to be included within a package should 
> be included in the LICENSE document. This LICENSE (courtesy of Apache HTTPD) 
> is a good example. The Apache License is at the top of the LICENSE document. 
> After that, the license for each non-Apache licensed component is included, 
> along with a clear explanation of which files that license applies to."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol pull request #156: [TC-39] More apache compliance

2017-01-04 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/156


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (TC-39) LICENSE file is incomplete

2017-01-04 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/TC-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798711#comment-15798711
 ] 

ASF GitHub Bot commented on TC-39:
--

GitHub user dangogh opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/156

[TC-39] More apache compliance

Remove goose binary and Perl modules -- now installed by the rpm spec file 
and not delivered with traffic_ops.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
apache-compliance

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/156.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #156


commit 568bf3e598d1bd5f1022d638eb78b58a230d499e
Author: Dan Kirkwood 
Date:   2017-01-03T17:38:07Z

remove goose binary

commit 32f5ff6dbfd48bb478b7aa5077dc70596100e4d1
Author: Dan Kirkwood 
Date:   2017-01-03T20:15:42Z

remove Perl-licensed files

commit 9994222ccb1268c23768a3523391d90d1f2e0d80
Author: Dan Kirkwood 
Date:   2017-01-04T05:02:29Z

adds perl modules needed for postinstall to rpm install

commit 1a7516a90be2b76a7338fe0c2cb9aeed510f221c
Author: Dan Kirkwood 
Date:   2017-01-04T05:10:14Z

run cpanm with tests turned off

commit 8d6735153187636dc175e264b5b89d66482f2672
Author: Dan Kirkwood 
Date:   2017-01-04T15:06:05Z

install goose from rpm spec

commit f41eb9b8dcd03be63912f70cbf44714a5585ded2
Author: Dan Kirkwood 
Date:   2017-01-04T15:17:57Z

add go to rpm requirements

commit 1372bd2ad8ed5c2b04695d70d6b4f17873e9b53b
Author: Dan Kirkwood 
Date:   2017-01-04T16:05:00Z

add git to rpm install




> LICENSE file is incomplete
> --
>
> Key: TC-39
> URL: https://issues.apache.org/jira/browse/TC-39
> Project: Traffic Control
>  Issue Type: Bug
>Reporter: Eric Friedrich
>Priority: Minor
> Fix For: 1.8.0
>
>
> Our LICENSE file only includes Apache License, but not the licenses of all 
> our bundled dependencies. 
> From 
> https://incubator.apache.org/guides/releasemanagement.html#best-practice-license:
> bq. "All the licenses on all the files to be included within a package should 
> be included in the LICENSE document. This LICENSE (courtesy of Apache HTTPD) 
> is a good example. The Apache License is at the top of the LICENSE document. 
> After that, the license for each non-Apache licensed component is included, 
> along with a clear explanation of which files that license applies to."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] incubator-trafficcontrol pull request #156: [TC-39] More apache compliance

2017-01-04 Thread dangogh
GitHub user dangogh opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/156

[TC-39] More apache compliance

Remove goose binary and Perl modules -- now installed by the rpm spec file 
and not delivered with traffic_ops.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
apache-compliance

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/156.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #156


commit 568bf3e598d1bd5f1022d638eb78b58a230d499e
Author: Dan Kirkwood 
Date:   2017-01-03T17:38:07Z

remove goose binary

commit 32f5ff6dbfd48bb478b7aa5077dc70596100e4d1
Author: Dan Kirkwood 
Date:   2017-01-03T20:15:42Z

remove Perl-licensed files

commit 9994222ccb1268c23768a3523391d90d1f2e0d80
Author: Dan Kirkwood 
Date:   2017-01-04T05:02:29Z

adds perl modules needed for postinstall to rpm install

commit 1a7516a90be2b76a7338fe0c2cb9aeed510f221c
Author: Dan Kirkwood 
Date:   2017-01-04T05:10:14Z

run cpanm with tests turned off

commit 8d6735153187636dc175e264b5b89d66482f2672
Author: Dan Kirkwood 
Date:   2017-01-04T15:06:05Z

install goose from rpm spec

commit f41eb9b8dcd03be63912f70cbf44714a5585ded2
Author: Dan Kirkwood 
Date:   2017-01-04T15:17:57Z

add go to rpm requirements

commit 1372bd2ad8ed5c2b04695d70d6b4f17873e9b53b
Author: Dan Kirkwood 
Date:   2017-01-04T16:05:00Z

add git to rpm install




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---