Skip to content

Conversation

@gamename
Copy link
Contributor

Description

<Please fill in the description of your pull request here. Thank you for your contribution!>
From a slack conversation with "@AtnNn"

tennis [1:34 PM]
Hi Guys. I’ve compiled the rethink rpm package on CentOS 7.3 successfully (using this script: https://github.com/rethinkdb/rethinkdb/blob/next/scripts/build-rpm.sh). Everything compiles fine. But when I go to use the rpm to install on exactly the same machine, I get this error:

Error: Package: rethinkdb-2.3.5_11_ga3b90f-29875.x86_64 (/rethinkdb)
           Requires: glibc >= 2.172.17
           Installed: glibc-2.17-157.el7_3.1.i686 (@updates)
               glibc = 2.17-157.el7_3.1
           Available: glibc-2.17-157.el7.i686 (base)
               glibc = 2.17-157.el7

Any ideas?

atnnn [2:19 PM]
@tennis what is the result of rpm -qa --queryformat '%{VERSION}' glibc?

[2:19]
@tennis Did you build an x86_64 rethinkdb for your i686 system?

tennis [2:21 PM]
@AtnNn I Got it figured out.. There are multiple glibc libs on my machine (i.e. 32 and 64 bit). So the output of rpm -qa --queryformat '%{VERSION}\n' glibc (note the newline) is:

2.17

[2:21]
Without the \n, the output is:
2.172.17

atnnn [2:22 PM]
Oh, that's a sneaky bug.

tennis [2:23 PM]
yup. I have to confess I didn’t figure it out on my own. But either way, we know the problem now. I’m happy to issue a pull request against the rethinkdb repo. Which branch should I request a pull into?

atnnn [2:25 PM]
Either v2.3.x (future 2.3.6) or next (future 2.4)

tennis [2:26 PM]
ok. Thanks

@AtnNn AtnNn added this to the 2.4 milestone Jan 15, 2017
@AtnNn AtnNn self-assigned this Jan 15, 2017
@gamename
Copy link
Contributor Author

@marshall007 FYI. This fixes the RPM issue I mentioned.

@AtnNn AtnNn merged commit 0a174b2 into rethinkdb:next Jan 29, 2017
@AtnNn AtnNn modified the milestones: 2.3.6, 2.4 Jan 29, 2017
@AtnNn
Copy link
Member

AtnNn commented Jan 29, 2017

LGTM

Thanks!

Also cherry-picked into v2.3.x as 4c55843

@AtnNn
Copy link
Member

AtnNn commented Jul 23, 2017

This fix has been released in RethinkDB 2.3.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants