# The latest libperconaserverclient20-dev seems to break the mysql2 gem

**URL:** <https://forums.percona.com/t/the-latest-libperconaserverclient20-dev-seems-to-break-the-mysql2-gem/7993>\
**Category:** Percona Distribution for MySQL\
**Created:** [September 2, 2020, 10:45am UTC](https://forums.percona.com/t/the-latest-libperconaserverclient20-dev-seems-to-break-the-mysql2-gem/7993 "2020-09-02T10:45:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![danrabinowitz](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/danrabinowitz/32/1386_2.png) [@danrabinowitz](https://forums.percona.com/u/danrabinowitz)\
**Post date:** [September 2, 2020, 10:45am UTC](https://forums.percona.com/t/the-latest-libperconaserverclient20-dev-seems-to-break-the-mysql2-gem/7993/1 "2020-09-02T10:45:25Z")

</div>

The latest libperconaserverclient20-dev seems to break the mysql2 gem. I have a Dockerfile that worked earlier this summer, and now the same Dockerfile fails to compile mysql2. I’m 90% confident that it’s due to a change in libperconaserverclient20-dev.

Downgrading to 18.1 allows mysql2 gem to compile, but then I lose the ability to work with a Percona server that requires secure transport. Any suggestions? Has anyone else observed this?

---

<div class="post-metadata">

**Author:** ![danrabinowitz](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/danrabinowitz/32/1386_2.png) [@danrabinowitz](https://forums.percona.com/u/danrabinowitz)\
**Post date:** [September 7, 2020, 9:28pm UTC](https://forums.percona.com/t/the-latest-libperconaserverclient20-dev-seems-to-break-the-mysql2-gem/7993/2 "2020-09-07T21:28:38Z")

</div>

Never mind.