This port will be removed on 2020-12-31 if not fixed
Thanks for the reminder. Python 3 support was added to Cassandra 4 and most work on the project is still on getting the Cassandra 4 GA release out so I don't imagine there will be a lot of effort to backport for Cassandra 3. I will see what can be done on this - whether this is something I can implement on my own or coordinate.
I tried the 3.6+ patch in PR 250005 and, while it compiles cleanly, it still installs a "cqlsh" that depends on 2.7.
% fgrep 'pyver in' /usr/local/bin/cqlsh
for pyver in 2.7; do
Have started gathering info on this now that 4.0-beta2 and 3.11.8 are submitted and awaiting feedback/commit. Will keep everyone informed on progress.
cassandra3 with python3 is available for testing.
The C* source it is based off is HEAD (from a few days ago) of the 3.11 branch. I'm planning on merging in any newer commits when the upstream project's 3.11.9 release is final and submitting a patch then for the port.
If anyone can contribute to testing that would be great.
Clone the 'python3' branch as follows (after wiping out databases/cassandra3):
git clone --single-branch --branch python3 https://github.com/polo-language/cassandra3.git <your-ports-tree>/databases/cassandra3
There have been dependency updates since 3.11.8, so please download the latest mvn repo to your distfiles/:
(In reply to Angelo Polo from comment #4)
Will the upcoming 3.11.9 patch include/supersede the patches in PR 2500005 ?
(In reply to Rene Ladan from comment #5)
Yes, it will supersede the update to 3.11.8 in bug #250005.
Created attachment 219455 [details]
Update to version 3.11.9.
Update to version 3.11.9.
SVN files added:
This patch supersedes bug #250005.
Updated maven repo must be manually copied to distfiles for patch testing and uploaded to LOCAL as part of the commit process. It is available at the following link:
(This is different from the mvn repo linked to above!)
I tested this and it works nicely; `pkg autoremove` was finally able to get rid of python2.
The latest patch builds fine on 11.4, 12.1, 12.2 and 13 for amd64 and i386.
Should we use https://downloads.apache.org/cassandra/3.11.9/ instead of a "local" archive?
(In reply to Rene Ladan from comment #11)
Are you referring to the maven repository? There's nothing like that getting published by Apache. The dependencies are intended to be downloaded (and cached) at build-time. Since access to the network is not allowed during a FreeBSD port build, the dependencies must be downloaded, packaged up, and checksummed ahead of time. If there is an alternative to this procedure that would save having to assemble the repository for every new version, but I'm not aware of one. For discussion on this you can check out the following mailing list message: https://lists.freebsd.org/pipermail/freebsd-ports/2016-June/103442.html
(In reply to Angelo Polo from comment #12)
Yes, I was referring to the Maven repository. I guess we will just have to use a "custom" download for now.
Patch committed, thanks
A commit references this bug:
Date: Tue Nov 17 22:06:20 UTC 2020
New revision: 555590
databases/cassandra3: update to 3.11.9
The port now uses Python 3 so unexpire it.
Submitted by: maintainer
Reported by: swills (py27 overview)