Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides

On mardi, 11 mars 2025 12.03:08 h heure normale d’Europe centrale Laurenz Albe
wrote:
> On Tue, 2025-03-11 at 11:58 +0100, Bruno Friedmann wrote:
> > On mardi, 11 mars 2025 10.11:27 h heure normale d’Europe centrale Álvaro
Herrera wrote:
> > > On 2025-Mar-11, Bruno Friedmann wrote:
> > > > We (Bareos dev's team) build our software on what's distributed by the
> > > > OS
> > > > editor. which means for RHEL9 libpq5-devel 13.20 (rhel)
> > > >
> > > > From time to time people want (for good reasons :-) ) use pgdg
> > > > binaries,
> > > >
> > > > if you go that way libpq from pgdg is installed and as the rpm
> > > > provides
> > > > all RH symbol you will get only this.
> > >
> > > Wouldn't this be solved if you built your software using the PGDG
> > > packages instead? That should be compatible with both the PGDG _and_
> > > the RH packages.
> >
> > And why we would do that ? pgdg is an additional third repository.
> > We have to build binaries that will work out of the box from the software
> > vendor with restricted possibility. which is what we do.
>
> But that is exactly the idea. Build against the PGDG packages, then
> the binaries should work out of the box with the Redhat packages as well.
>
> Are you trying to make things work or is this a matter of principle?
>
> Yours,
> Laurenz Albe

Ha ha that's just the reverse that should happen.

PGDG is claiming 100% ABI compatibility, which has been proved here that's not
the case and all this bug is about this.

If you don't care, me neither, we detected that, we reported it, you decide.

As an editor POV we certainly don't want to build from 3rd parties, except
when customer are paying for that specific.

So for us the situation is clear, before the symbol version was introduced in
Fedora/Rhel our customer were able to use transparently as the software didn't
complain pgdg repository at their convenience.

Now that system libraries are build with symbol version, and our lib depend on
those to be present due the build itself, the pgdg might be usable but without
any warranties. And we advertise people to better stick to module proposed by
the OS editors.

I'm not yet sure what kind of impact those symbol check will have for any
software build against system libs in Fedora/Redhat and then used with pgdg
lib. I guess the same warning will be emitted each time.

Regards.

--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
expertise en open-source

GPG KEY: E4720D8715B696B4
irc: tigerfoot
Computing freedom with openSUSE Tumbleweed - 20250307