Your message dated Sun, 21 Feb 2021 15:58:32 +0000
with message-id <[email protected]>
and subject line Fixed in upstream 10.34
has caused the Debian Bug report #920290,
regarding libpcre2-dev: libpcre2-posix is not usable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
920290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920290
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpcre2-dev
Version: 10.32-3
Severity: important
The header exports the standard libc names, but debian/rules
overrides them at build time to use PCRE2Posix and friends.
This does not help applications wanting to link against
pcreposix - including the header and calling the functions
regcomp() and friends just makes it use the libc ones.
You have to do the #define dance in the header for things
to work.
-- System Information:
Debian Release: buster/sid
APT prefers disco
APT policy: (500, 'disco'), (500, 'cosmic-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpcre2-dev depends on:
ii libc6-dev 2.28-0ubuntu1
ii libpcre2-16-0 10.32-3
ii libpcre2-32-0 10.32-3
ii libpcre2-8-0 10.32-3
ii libpcre2-posix0 10.32-3
libpcre2-dev recommends no packages.
libpcre2-dev suggests no packages.
-- no debconf information
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
--- End Message ---
--- Begin Message ---
version: 10.34-1
Hi,
As previously mentioned, this bug was fixed in upstream 10.34.
Regards,
Matthew
--- End Message ---
