Bug#1070862: poppler: possibly unintended revert of t64 renames for non-main library in 24.x

[Simon McVittie]

Source: poppler
Version: 24.02.0-1
Severity: important
X-Debbugs-Cc: pochu at debian.org, jeremy.bicha at canonical.com

Attempting to summarize recent discussion with _rene_ on #debian-devel:

poppler in trixie builds these libraries:

- libpoppler126t64
- libpoppler-glib8t64
- libpoppler-qt5-1t64
- libpoppler-qt6-3t64
- libpoppler-cpp0t64

It is not obvious to me whether the -glib, -qt, -cpp libraries genuinely
broke their ABIs during the time64 transition, or whether they were only
renamed out of an abundance of caution.

poppler in experimental and (since today) unstable builds these libraries:

- libpoppler134
- libpoppler-glib8
- libpoppler-qt5-1
- libpoppler-qt6-3
- libpoppler-cpp0v5

In other words, it correctly drops the t64 suffix from the main libpoppler
across a SONAME bump, but it also reverts the renaming of the -glib,
-qt, -cpp libraries.

Was this intentional?

If the higher-level libraries never actually broke their ABI, then renaming
them back to their Debian 12 names might be OK, but they're probably going
to need versioned Breaks/Replaces on their ...t64 names.

If the higher-level libraries *did* break their ABI, then they need to
keep the new t64 names.

Please bump this up to RC if analysis shows that it is a genuine problem,
or close it if analysis shows that I'm being overly cautious.

    smcv