public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marcin Cieslak <[email protected]>
To: [email protected]
Subject: postgresql13-devel vs libpq-devel
Date: Mon, 14 Apr 2025 16:24:28 +0000
Message-ID: <[email protected]> (raw)
Hello and big thanks for keeping this running. I've been a long time user of PGDG
packages and after many years I have run into my first problem:
The RHEL 9 machine I have has postgresql13, -libs, -server and -devel
installed from the PGDG repository (all at the 13.20-1PGDG revision).
Today I have tried to rebuild a package provided by Red Hat (rsyslog)
and it has a build time dependency on libpq-devel [1].
dnf --enablerepo pgdg-common --enablerepo pgdg13 install libpq-devel
does nothing since "postgresql13-devel" already "obsoletes" libpq-devel
but it does not full replace it (it does not "provide" libpq-devel).
This is kind of expected, I could install postgresql13-devel, postgresdql14-devel
up to the 18 if I really like in parallel. I can't do this with libpq-devel.
However, the RPM packages obviously want to have it Red Hat way, no the Postgres way.
Today, as it happens, RHEL 9 has 13.20 in their base, and I have 13.20-1PGDG
installed, but this is just a nice coincidene - I have simply done
dnf erase --noautoremove postgresql13-devel
dbf install libpq-devel
Is there any elegant solution to this problem? For example, is there
any clean way to say "please using my postgresql13-devel and instead of libpq-devel?"
to rpmbuild? That would require telling PATH and pkgconf to go somewhere else...
Or maybe postgresql13-devel and libpq-devel should get along with each other?
I think postgresql13-libs and RHEL's libpq do, and both provide "libpq.so.5()".
All the best,
Marcin
[1] https://src.fedoraproject.org/rpms/rsyslog/blob/b80cab473af65b2e3b503fc5b5cb115162065857/f/rsyslog.s...
Attachments:
[application/pkcs7-signature] smime.p7s (3.6K, 2-smime.p7s)
download
view thread (2+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: postgresql13-devel vs libpq-devel
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox