[question] Release to add ppc64le support
amitsadaphule opened this issue · comments
With the merge of #13 which resolves #12, ppc64le support is enabled in master branch. I'd like to request for info on the ETA for next release (including upload of jars to maven central). I'll raise PRs on the prestodb/presto repo once this release is available.
I have same question for https://github.com/prestodb/testing-postgresql-server repo since the PR prestodb/testing-postgresql-server#3 has been merged. I could not raise the issue/question there, since the issues tab is disabled there.
@rschlussel do you have any updates on the plan to upload the jars to maven central?
@rschlussel do you have any information on this? Or can you maybe point me to someone who handles the releases for these repos?
I'm very sorry. I lost track of this issue. Let me do the release now.
I can't release because the directories below (e.g. usr/bin/mysqldb) do not exist for me when I build locally on my mac. Is there a way to make this more general?
testing-mysql-server/testing-mysql-server-5/repack-mysql-5.sh
Lines 75 to 80 in 4946a61
That's odd. Can you please check if there were any errors returned by this line (i.e. rpm2cpio or cpio command)?
You're right:
+ cpio -idm
/Users/rschlussel/testing-mysql-server/testing-mysql-server-5/repack-mysql-5.sh: line 73: rpm2cpio: command not found
0 blocks
We should make sure that throws an error.
got around that issue by installing rpm2cpio. Then encountered another issue that turns out was caused by the url for the mariadb rpm not existing anymore (so didn't download a proper rpm). Have a fix here to update to a more recent version #18.
Created the release in github, but haven't uploaded the artifacts to nexus yet because to do that I need to update the system we use to deploy them, and we have a freeze this week on making any changes. I'll do it right after the new year.
Thanks @rschlussel! Can you please also create the release for https://github.com/prestodb/testing-postgresql-server. I couldn't add an issue there, since the issues tab is not accessible.