Package Details: rethinkdb 2.4.2-1

Git Clone URL: (read-only, click to copy)
Package Base: rethinkdb
Description: Distributed NoSQL database for realtime applications
Upstream URL:
Licenses: Apache
Submitter: anatolik
Maintainer: celogeek
Last Packager: celogeek
Votes: 9
Popularity: 0.000083
First Submitted: 2019-03-07 12:58 (UTC)
Last Updated: 2022-06-01 20:47 (UTC)

Latest Comments

celogeek commented on 2022-06-01 20:49 (UTC)

This version include a mistake from the release itself, which has the wrong admin version (2.4.1-24 instead of 2.4.2) I report the issue, the server is properly on version 2.4.2. I will update this when the fix will be done by rethinkdb team.

celogeek commented on 2021-09-08 18:14 (UTC)

The fix seems to works. can you install this version and check if it works properly ?

celogeek commented on 2021-09-08 16:16 (UTC)

I'm trying with your patch. If it pass, I will push the fix

celogeek commented on 2021-09-08 16:07 (UTC)

I try again, and yeah, I've got the same issue.

besworks commented on 2021-09-08 14:48 (UTC)

Sorry I can't right now, I've already installed the package with my fixes and am using it for work.

The issue with Node's v8_inspector dep was related to the GCC version. There were changes made in v11 that caused this (see the link at the end of my previous comment).

Maybe you have GCC < v11 installed and that's why it works for you? I have 11.1.0-1

celogeek commented on 2021-09-08 12:12 (UTC)

I don't have issues with node. can you try again ?

celogeek commented on 2021-09-08 11:50 (UTC)

Oh, I see, I will try it and push a fix

besworks commented on 2021-09-07 20:43 (UTC) (edited on 2021-09-07 20:46 (UTC) by besworks)

I ran into a couple problems building this today.

First, I had to run makepkg -g >> PKGBUILD to update the SHA for v8_g++7_build_fix.patch. I compared the file contents against the upstream patch source first and there are no differences.

Also, the build of Node failed with this error (and 2 more like it): .../v8_inspector/String16STL.cpp:375:23: error: no member named 'numeric_limits' in namespace 'std'

I fixed this by adding #import <limits> to src/rethinkdb/external/node_6.11.0/deps/v8_inspector/third_party/v8_inspector/platform/v8_inspector/String16STL.cpp as described here

celogeek commented on 2021-02-08 12:04 (UTC)

Hi, I remove the fix of the assets I have made to improve the version of the UI. It seems to break now the UI.

I've check, it works, but the version is RethinkDB 2.4.0-8-g07da06-dirty

This is from the package version.

Some fixes are in progress in the master branch, but no release yet.

Can you test again ?

celogeek commented on 2021-02-07 17:58 (UTC)

what errors did you see ?

Kodehawa commented on 2021-02-07 17:39 (UTC)

Is the web UI broken for anyone else? According to srh it looks like the assets weren't properly regenerated?

MrSelfDestruct commented on 2020-12-27 03:13 (UTC)

It compiles now. can you try again please?

Seems to be fixed for me too! Good fix.

celogeek commented on 2020-12-26 11:55 (UTC)

It compiles now. can you try again please?

celogeek commented on 2020-12-26 10:48 (UTC)

I see that a fetch boost exists as an option !

Ok let me add this.

celogeek commented on 2020-12-24 10:20 (UTC)

We have to report the problem on their github. I don't see anything about this there.

I'm not sure I can fix it with a patch, or may be if we can fetch boost 1.72 during the build and statically link the deps there.

I check if a fetch boost exists, and not.

celogeek commented on 2020-12-23 09:42 (UTC)

Ok, see mirrors index are out of sync. I have to way tomorrow.

celogeek commented on 2020-12-23 09:41 (UTC)

Thanks for the report. I can see boost 1.75 in the repos. Having issue to install them (mirror have rel1 in the index, but rel2 file is in the repos ...)

I try to figure out if some mirror are partially sync.

I will see if I can figure out a way to fix it.

MrSelfDestruct commented on 2020-12-23 04:52 (UTC) (edited on 2020-12-23 05:02 (UTC) by MrSelfDestruct)

In response to the error I was getting below, this seems to be an upstream issue with rethinkdb, and you need to explicitly install boost and boost-libs 1.72 for it to work. 1.74 and above do not work. You can use the ALA to download the previous versions of the libraries.

MrSelfDestruct commented on 2020-12-20 01:47 (UTC)

I'm suddenly having a compile error I haven't seen before.

'boost/detail/endian.hpp' file not found

With very limited research (I don't use boost often), perhaps that header is depreciated and maybe not in the boost package anymore?

celogeek commented on 2020-08-17 16:43 (UTC)

ok done, let me know if everything fine.

celogeek commented on 2020-08-17 16:40 (UTC)

This release has a bug on the web ui:

It still indicate 2.4.0, and ask to update even we are on 2.4.1.

They have rollback the version check to 2.4.0 because this release is not fully properly done.

Hopefully a new version will come out soon.

In the mean time I'm testing 2.4.1 with asset fixed by myself.

celogeek commented on 2020-08-17 11:21 (UTC)

This release contains a bug with the generated asset. When I open the interface, it indicate I'm on a version 2.4.0-8-gxxxxx-dirty. And ask to update ...

I have report the bug. I try to fix it myself.

my first try was to fix the version but my patch take 18m, which was not accepted in this repos. I try to make it smaller.

celogeek commented on 2020-08-16 09:10 (UTC)

fixed. thanks.

MrSelfDestruct commented on 2020-08-16 02:09 (UTC)

jemalloc needs to be made a regular dependency and not just a make dependency, as rethinkdb requires it on runtime

celogeek commented on 2020-06-06 10:06 (UTC)

if you upgrade protobuf you need to reinstall rethinkdb. I change the deps to fetch protobuf lib, so this problem won't appear anymore.

testing it right now, I will push an update if all works.

snowkeep commented on 2020-05-22 15:15 (UTC)

@celogeek - I can confirm it now works as of this morning.

celogeek commented on 2020-05-21 21:23 (UTC)

I have tested it, it works now. Can anyone confirm this work for you?

celogeek commented on 2020-05-21 20:29 (UTC)

Wow, there was serious problem with the build.

I pickup 3 patches from git branch (2.4.x), and also apply my own patch to make it work. I will submit this to the official repos.

celogeek commented on 2020-05-21 12:56 (UTC)

I fix it. Also I have install it, it works fine.

I will submit python-rethinkdb wit:

python-rethinkdb /usr/bin/rethinkdb-dump
python-rethinkdb /usr/bin/rethinkdb-export
python-rethinkdb /usr/bin/rethinkdb-import
python-rethinkdb /usr/bin/rethinkdb-index-rebuild
python-rethinkdb /usr/bin/rethinkdb-repl
python-rethinkdb /usr/bin/rethinkdb-restore

hokkqido commented on 2020-05-02 20:14 (UTC) (edited on 2020-05-02 20:15 (UTC) by hokkqido)

v8_g++7_build_fix.patch still has wrong checksums!

shivamgly commented on 2020-04-14 11:42 (UTC) (edited on 2020-04-14 11:44 (UTC) by shivamgly)

The file v8_g++7_build_fix.patch has wrong checksums, Please fix it!

==> Validating source files with sha512sums...
rethinkdb-2.4.0.tgz ... Passed
node-v6.11.0.tar.gz ... Passed
rethinkdb@.service ... Passed
rethinkdb.sysusers.d ... Passed
rethinkdb.tmpfiles.d ... Passed
mksnapshot_crash_fix.patch ... Passed
v8_g++7_build_fix.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!

sain801028 commented on 2020-03-27 07:27 (UTC)

v8_g++7_build_fix.patch failure One or more files did not pass the validity check!

sain801028 commented on 2020-03-27 07:26 (UTC)

I use manjaro 19.0.2

sain801028 commented on 2020-03-27 07:25 (UTC)

v8_g++7_build_fix.patch failure

flacks commented on 2020-01-24 01:32 (UTC)

You're welcome! Took long enough, heh.

loumray commented on 2020-01-23 22:24 (UTC)

Build 2.4.0-1 works now. Great job flacks, Thank you!

anatolik commented on 2019-11-19 18:27 (UTC)

Not much progress at my side unfortunately. I just disowned the package just in case if someone wants to driver this project forward.

Cirelli94 commented on 2019-11-19 16:03 (UTC)

Hi @flacks, are there any news? Thanks in advance

flacks commented on 2019-08-02 02:06 (UTC)

I will look into this. Sorry for the delay.

anatolik commented on 2019-03-21 17:30 (UTC)

could you please report the issue upstream?

flacks commented on 2019-03-21 04:50 (UTC)

FYI, package fails to build with boost 1.69.0-1, but successfully builds with 1.68.0-2.