FS#73656 - [postfix] postfix-prce 3.7.0-1 not properly linked

Attached to Project: Arch Linux
Opened by Geert Hendrickx (ghen) - Sunday, 06 February 2022, 21:01 GMT
Last edited by David Runge (dvzrv) - Monday, 07 February 2022, 08:46 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

postfix-pcre 3.7.0-1 in [testing] is broken:

postfix/cleanup[21001]: fatal: load_library_symbols: dlopen failure loading /usr/lib/postfix/postfix-pcre.so: /usr/lib/postfix/postfix-pcre.so: undefined symbol: pcre2_get_ovector_pointer_8


From Postfix 3.7 release notes:

[Feature 20211127] Support for the pcre2 library (the legacy pcre
library is no longer maintained). The Postfix build procedure
automatically detects if the pcre2 library is installed, and if it
is unavailable, the Postfix build procedure will detect if the
legacy pcre library is installed. See PCRE_README if you need to
build Postfix with a specific library.



However the postfix-prce.so in [testing] seems to link to neither libpcre or libpcre2:

$ ldd /usr/lib/postfix/postfix-pcre.so
linux-vdso.so.1 (0x00007ffd4e2db000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007ff545df4000)
/usr/lib64/ld-linux-x86-64.so.2 (0x00007ff545fd0000)


(so file from 3.6.4 linked with libpcre.so.1)
This task depends upon

Closed by  David Runge (dvzrv)
Monday, 07 February 2022, 08:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with postfix-pcre 3.7.0-2
Comment by Geert Hendrickx (ghen) - Sunday, 06 February 2022, 21:08 GMT
Comment by Geert Hendrickx (ghen) - Sunday, 06 February 2022, 21:32 GMT
Looks like we need pcre2-config --libs8 instead of --libs32. It contains the referenced symbols, and rebuilding postfix with -lpcre2-8 makes it work.
Comment by David Runge (dvzrv) - Monday, 07 February 2022, 00:00 GMT
@ghen: Thanks for the report!

I guess I chose the wrong one :S
3.7.0-2 should be alright
Comment by Geert Hendrickx (ghen) - Monday, 07 February 2022, 07:28 GMT
3.7.0-2 confirmed (and signed off), thanks!