Github user asfgit commented on the issue:
https://github.com/apache/madlib/pull/212
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/301/
---
Github user fmcquillan99 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/212#discussion_r155685205
--- Diff: README.md ---
@@ -11,9 +11,11 @@ Installation and Contribution
==
See the project website [`MADlib
Github user njayaram2 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/212#discussion_r155684500
--- Diff: README.md ---
@@ -11,9 +11,11 @@ Installation and Contribution
==
See the project website [`MADlib
Github user jingyimei commented on a diff in the pull request:
https://github.com/apache/madlib/pull/211#discussion_r155683583
--- Diff: cmake/LinuxUtils.cmake ---
@@ -9,3 +9,14 @@ macro(rh_version OUT_VERSION)
set(${OUT_VERSION} "${OUT_VERSION}-NOTFOUND")
Github user jingyimei commented on the issue:
https://github.com/apache/madlib/pull/211
@fmcquillan99 Yes, the version string is saved in Version.yml file and when
we make the release, we will change the version string from 1.13_dev to 1.13,
and cmake will directly get it from the
Github user asfgit commented on the issue:
https://github.com/apache/madlib/pull/212
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/300/
---
Github user asfgit commented on the issue:
https://github.com/apache/madlib/pull/212
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/299/
---
Github user asfgit commented on the issue:
https://github.com/apache/madlib/pull/209
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/298/
---
GitHub user fmcquillan99 opened a pull request:
https://github.com/apache/madlib/pull/212
update PyXB version in README.md
minor version update for PyXB from 1.2.4 to 1.2.6 in README.md
You can merge this pull request into a Git repository by running:
$ git pull
Yes there was a JIRA/PR to remove GPL components in 1.13:
https://issues.apache.org/jira/browse/MADLIB-1103
https://github.com/apache/madlib/pull/190
Prior to that, the GPL component was removed during build in
src/patch/PyXB.sh,
which is fixed in the above PR.
I will update the README.md
Hi All,
The README page in MADlib's github page lists PyXB-1.2.4
in Third Party Components. Should it be changed to PyXB-1.2.6 now?
NJ
Github user iyerr3 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/211#discussion_r155598266
--- Diff: cmake/LinuxUtils.cmake ---
@@ -9,3 +9,14 @@ macro(rh_version OUT_VERSION)
set(${OUT_VERSION} "${OUT_VERSION}-NOTFOUND")
Github user iyerr3 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/211#discussion_r155597507
--- Diff: CMakeLists.txt ---
@@ -275,4 +275,3 @@ install(CODE "
${CMAKE_MADLIB_ROOT}/doc
)
")
--- End diff --
Github user iyerr3 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/211#discussion_r155599007
--- Diff: src/ports/greenplum/cmake/GreenplumUtils.cmake ---
@@ -17,6 +17,9 @@ function(add_gppkg GPDB_VERSION GPDB_VARIANT
GPDB_VARIANT_SHORT
Github user iyerr3 commented on a diff in the pull request:
https://github.com/apache/madlib/pull/211#discussion_r155598556
--- Diff: deploy/CMakeLists.txt ---
@@ -82,4 +82,4 @@ cpack_add_component_group(ports
file(GLOB PORT_COMPONENTS
Github user fmcquillan99 commented on the issue:
https://github.com/apache/madlib/pull/211
naming convention looks good.
I assume for prod releases there is no "_dev" in the name.
---
GitHub user jingyimei opened a pull request:
https://github.com/apache/madlib/pull/211
Change madlib gppkg version string
This commit changes the naming convention for madlib gppkg,
after renaming, the format of madlib gppkg will look like:
17 matches
Mail list logo