| From: | Shaun Thomas <shaun(dot)thomas(at)2ndquadrant(dot)com> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | pgsql-pkg-yum(at)postgresql(dot)org |
| Subject: | Re: PgBouncer RPMs Seem to be Missing |
| Date: | 2020-08-13 13:05:29 |
| Message-ID: | CAG1YDPfY7Z_k3Dj1RN6mMSZUgFGOKZ9GtCQnm7xdcd1j7DP9RA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-yum |
> 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(dot)thomas(at)2ndquadrant(dot)com | www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2020-08-13 14:13:03 | Re: PgBouncer RPMs Seem to be Missing |
| Previous Message | Devrim Gündüz | 2020-08-13 08:54:53 | Re: PgBouncer RPMs Seem to be Missing |