#1121324 pinot: depends on superseded libxml++2.6

Package:
src:pinot
Source:
src:pinot
Submitter:
Simon McVittie
Date:
2026-03-15 20:11:00 UTC
Severity:
normal
Tags:
#1121324#5
Date:
2025-11-24 13:13:14 UTC
From:
To:
Binaries produced by this source package depend on libxml++2.6, a C++
wrapper around libxml2.

libxml++2.6 is no longer maintained upstream (#1038804). It has been
superseded by libxml++-3.0, which was itself superseded by libxml++-4.0
(RFP: #819562) and libxml++-5.0 (RFP: #1121304).

If this package is ported to one of the newer libraries, packaging the new
version will require packaging the new library first. I haven't marked
#819562 and #1121304 as blockers for this bug, because I don't know which
one would be more appropriate.

Alternatively, it could be ported to use libxml2's C interface directly,
or to use some unrelated XML library.

    smcv

#1121324#12
Date:
2025-11-24 18:20:05 UTC
From:
To:
Unfortunately I don't have the spare cycles currently to contemplate
packaging a newer libxml++.

Pinot's upstream README lists the oldest tested libxml++ as 3.2.0 and
changing to that would at least be a step towards being able to remove
libxml++2.6.

The use of libxml++ seems extensive so that would really need to be
something for upstream to decide to do rather than something we could
sensibly patch in Debian.

Cheers,
    Olly

#1121324#17
Date:
2025-11-27 00:54:19 UTC
From:
To:
I think I had misunderstood here as libxml++-3.0 doesn't seem to be
packaged either.

Cheers,
    Olly

#1121324#22
Date:
2026-03-15 20:09:38 UTC
From:
To:
I see the two RFPs have now been completed.

I took a look, but the code doesn't compile if we just update
build-depends.

Upstream seems to be currently working on modernising dependencies
(despite the 2024 in the branch name it seems the branch was actually
started late in 2025 and there are commits from earlier this month):

https://github.com/FabriceColin/pinot/tree/FabriceColin/modernizing-202412

This includes using libxml++-5.0:

https://github.com/FabriceColin/pinot/commit/810fe33ae33c98125f99edb68602e5b5c88834ad

I think it makes most sense to let this work make it into a new stable
upstream release, but if that drags out too long we can potentially
package this branch, or cherry-pick from it.

Cheers,
    Olly