Description of problem: Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Install pgbouncer 2. Enable "pam" authentication 3. Start service Actual results: PgBouncer fails to start. Expected results: PgBouncer starts normally. Additional info: This is just due to missing support for PAM during the build phase. Adding the "pam-devel" to the build requirements (BuildRequires) should fix the issue.
Just a side note on this, it seems like PAM doesn't currently work for distributions with tighter PAM security. Debian-based distributions have lenient policies in /etc/pam.d/other to allow unknown services to authenticate against PAM, whereas Fedora (and openSUSE) do not allow this. PAM authentication currently will not work on Fedora until a proper PAM file is provided, which I assume to be the responsibility of upstream.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
FEDORA-2020-a0f768bef9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a0f768bef9
pgbouncer-1.12.0-3.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a0f768bef9
FEDORA-2020-a0f768bef9 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.