Control: tags -1 + trixie-ignore hippotat 1.1.7 FTBFS with rust-base64 0.21. hippotat 1.1.9 build-depends on rust-base64 0.21.
So the plan is for these to migrate together, and ISTM from reading tracker that that is what will happen as soon as the remaining blockers for rust-bsee64 migration are disposed of. In principle hippotat's build-dependencies could have been adjusted to depend on rust-base64 0.13, and then we could have waited for that to enter testing, and then done the update. But thst seems otiose, given that the plan is that trixie should have base64 0.21. Therefore I am tagging this bug trixie-ignore to avoid getting autoremoval warnings etc. I hope I'm not overstepping the mark. PS, with my upstream hat on: It is a shame that the Rust base64 crate has such a cavalier approach to API stability. I am considering my options in this area for hippotat (eg data-encoding or base64ct), but without better tests and test vectors I am reluctant to switch right now. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
