For the record, in case this is revisited later, here are some updates
on the upstream side. All of the following is planned for the short term
(December release or the coming months), except the libzen integration.

> libzen (no new release since 2023)

A new libzen release is planned for December 2026.
In the medium term (likely in 2027), we plan to integrate the libzen features 
used by libmediainfo (mainly the I/O part) directly into libmediainfo, so 
libzen would no longer be a dependency, simplifying the packaging.

About LTO: we are not aware of any LTO-specific issue in libzen, and the
lto-disabled-list entry doesn't reference a bug.

> tinyxml2 (later two are on lto-disabled list)

MediaInfoLib master no longer depends on tinyxml2: it now uses tfsxml,
our own lightweight XML parser
(https://github.com/MediaArea/MediaInfoLib/pull/2848), directly
integrated in libmediainfo source code; this will be in the December
release. A small tinyxml2-compatible API layer is temporarily kept on
top of it, and will be removed soon, once all parsers are ported to the
tfsxml API.

> libmediainfo has no build-time tests

There is a `make check` test suite, run in our CI, but most tests need sample 
files from a separate repository 
(https://github.com/MediaArea/MediaArea-RegressionTestingFiles) and download 
the XML schemas, so it can't run offline during a package build. In the short 
term, we plan to:
- ship the XML schemas and a small set of test files (created by us, so 
license-clean) in the source tarball,
- compare the outputs with reference outputs for this set, in addition to the 
current XML schema checks,
- skip instead of fail the tests needing the full set when it is not present,
so that `make check` will run at package build time (dh_auto_test). The full 
set remains used in our CI.

> no ossfuzz, with various still open upstream fuzzer heap overflows
open

There are no longer open fuzzer-reported heap overflows upstream. Following 
fuzzing and hostile-input audits, a large set of robustness fixes was merged, 
the main ones being:
- https://github.com/MediaArea/MediaInfoLib/pull/2715 (47 fixes, already in 
26.10)
- https://github.com/MediaArea/MediaInfoLib/pull/2730 (65 commits)
- https://github.com/MediaArea/MediaInfoLib/pull/2732
- https://github.com/MediaArea/MediaInfoLib/pull/2865 (100 fixes, one per 
commit)
- https://github.com/MediaArea/MediaInfoLib/pull/2871
- https://github.com/MediaArea/MediaInfoLib/pull/2900
- out-of-bounds read/write fixes: 
https://github.com/MediaArea/MediaInfoLib/pull/2798, 
https://github.com/MediaArea/MediaInfoLib/pull/2911, 
https://github.com/MediaArea/MediaInfoLib/pull/2785, 
https://github.com/MediaArea/MediaInfoLib/pull/2747
All of these will be in the December release.

MediaInfoLib is not in OSS-Fuzz yet. In the short term, we plan to add
libFuzzer harnesses (with a seed corpus) to the repository and to apply
to OSS-Fuzz, so that fuzzing becomes continuous instead of being done in
campaigns as until now.

+1 for having gnome-music Recommend the a/v extractor in the meantime.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154314

Title:
  [MIR] libmediainfo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmediainfo/+bug/2154314/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to