Thread: PgBouncer RPMs Seem to be Missing
Hi, We noticed PgBouncer builds for CentOS 6, 7, and 8 all appear to have gone MIA. Heads up. Regards, -- Shaun M Thomas - 2ndQuadrant PostgreSQL Training, Services and Support shaun.thomas@2ndquadrant.com | www.2ndQuadrant.com
Hi Shaun, On Thu, 2020-08-06 at 16:01 -0500, Shaun Thomas wrote: > We noticed PgBouncer builds for CentOS 6, 7, and 8 all appear to have > gone MIA. https://yum.postgresql.org/news/new-repo-rpms-released/ Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
> https://yum.postgresql.org/news/new-repo-rpms-released/ Yeah, I knew about that. I missed the detail that the PgBouncer RPMs themselves were in the -common section, which is why I didn't see them when I looked. Oddly enough the whole reason this got prompted is because EPEL posted pgbouncer-1.14.0-2 while PGDG only had a pgbouncer-1.14.0-1 package. And the EPEL version is broken because it still depends on python-psycopg2 (rather than python3-psycopg2, or python2-psycopg2). I guess the real lesson here is to not use EPEL, or if you do, blacklist any packages you might want from PGDG. I wasn't subscribed to this ML, so I had to wait for someone to reply before I could correct myself. ;) Thanks Devrim! -- Shaun M Thomas - 2ndQuadrant PostgreSQL Training, Services and Support shaun.thomas@2ndquadrant.com | www.2ndQuadrant.com
Hi, On Thu, 2020-08-13 at 08:05 -0500, Shaun Thomas wrote: > Oddly enough the whole reason this got prompted is because EPEL > posted pgbouncer-1.14.0-2 while PGDG only had a pgbouncer-1.14.0-1 > package. > > And the EPEL version is broken because it still depends on python- > psycopg2 (rather than python3-psycopg2, or python2-psycopg2). No worries, I pushed 1.14.0-3 today, for proper systemd support. :) Next time, I'll bump it to -42, to avoid such conflicts. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR