Hi, On Thu, Jun 27, 2024 at 4:21 AM Paul Gevers <elb...@debian.org> wrote: > > Source: libxml2 > Version: 2.9.14+dfsg-1.3 > Severity: serious > Control: close -1 2.12.7+dfsg-3 > Tags: sid trixie > User: release.debian....@packages.debian.org > Usertags: out-of-sync > Control: block -1 by 1073508 > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:libxml2 has been trying to migrate for 32 > days [2]. Hence, I am filing this bug. The version in unstable broke ABI > without a SONAME bump as reported in bug 1073508. >
I would like to seek for your advice on how to handle this issue, the stuff looks a bit complicated: - upstream is responsive and helpful, but the current handling of API/ABI could be problematic - there is no plan to bump SONAME at this moment - need time to do in-depth check of API/ABI breakages Would like to know if such steps would help resolve the issue better: - revert to a previous version which does not have API/ABI breakage - apply/port security patches on a best effort basis - help upstream to check and fix API/ABI changes Or do you have any recommendations? Thanks, Aron
