On 2026-09-08 02:50, astian wrote:
On 28 Aug 2026 20:41 +0900, Luke Yasuda wrote:Upstream had a SONAME change and libanthy1t64 was renamed to libanthy2. Impacted packages are here: https://release.debian.org/transitions/html/auto-anthy.htmlkasumi will need a sourceful upload to unstable (now in experimental). uim FTBFS, but I'm ready to do an NMU if the current maintainer is not responsive, see #1145951. All other packages built fine and will onlyneed binNMUs (fcitx5-anthy, gcin, hime, ibus-anthy, m17n-lib, scim-anthy).Sorry, but is that about ibus-anthy correct?According to the buildd log it does seem to have built successfully, butthe binary +b1 ibus-anthy is not showing up in the mirrors and the tracker shows an error about dependencies. The rest of the binary +b1 packages from src:ibus-anthy did get pushed to the mirrors. I noticed this because apt was holding back some anthy-related packageswhen trying to upgrade. With some handholding I can actually get apt toupgrade to all available new versions, so long as I remove the binary ibus-anthy (because the other binary packages in the +b1 version break it). This seems odd so I'm guessing something is wrong.
The binary package ibus-anthy is Architecture: all, so naturally it wouldn't be a part of binNMU. But src:ibus-anthy should be binNMU-able, as I don't see any of its binary package depends on ibus-anthy ( = {binary:Version}).
However I do see the binary package ibus-anthy depends on gir1.2-anthy-9000 (>= 1.5.18-3), gir1.2-anthy-9000 (<< 1.5.18-3.1~), libanthygobject-1.0-5 (>= 1.5.18-3), libanthygobject-1.0-5 (<< 1.5.18-3.1~). So maybe this is why.
I'll do an team upload of src:ibus-anthy soon. Cheers, -- Luke Yasuda GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC
signature.asc
Description: OpenPGP digital signature
