Hi,

in the last upload postfix was changed to use pkgconf for mongo-c-driver
cflags, which works great in unstable with mongo-c-driver 2.x.

when backporting postfix to stable, this FTBFS, as trixie has only
mongo-c-driver 1.x with no pkgconf support.

It would be nice if postfix rules could handle that, so that we neither
need to change it locally nor to backport mongo-c-driver 2.x too.

Regards,
Daniel

Control: tag -1 + moreinfo

Hi!

What's the reason for this bug report?

Postfix had never been back-ported before, as far as I remember.
It rarely *needs* a backport because it doesn't change much between
releases, - I made backport from trixie to bookworm just to prepare
for packaging changes which were a lot, not because of upstream
changes.

The change in question is trivial to roll back when doing a
backport, it's just 2 consecutive lines.  Inventing some logic here -
I don't think it's a good idea to add complexity here.  It definitely
works in the environment it is intended to work in.

If anything, I'd say it's a bug in mongo-c-driver who broke things
without keeping any sort of backward compatibility, and it's the place
where things should be changed, not in all users of this software.

If I'll decide a backport to trixe is a good idea, it will be me
who'll do such backport, and I'll deal with this for sure.  At this
point I don't plan to do a backport.

So.. I've o idea what should do with this bug report.  Keep it open
forever, to add another item to already existing pile of bug reports
which makes me unwilling to open postfix bts page?  I don't think it
helps..

Thanks,

/mjt