Hello, On Sat 06 Apr 2024 at 03:24pm +02, Salvatore Bonaccorso wrote:
> As it is a regression caused by libssl3 3.0.11 based to 3.0.13, why is > it reassigned to yapet? (the regression is as well present in > unstable). I was just thinking that it may be a flaw in how YAPET calls into openssl, and we don't have evidence either way atm. > That said: You are right, opening 1.0 format databases should still > work that said, but is regressing with the openssl update. And as per > manpage: YAPET 2.0 will read and write pre YAPET 2.0 files. Pre YAPET > 2.0 files are converted to YAPET 2.0 files when changing the master > password. Once converted, the files can no longer be read by pre YAPET > 2.0 versions. > > I can ask upstream, but currently yapet will FTBFS with problems in > the testsuite anyway, and the problems are related. > > And yapet FTBFS with the new openssl in bookworm-pu in same way as in > unstable (but not with the old version). > > Thus I believe #1068045 and #1064724 are actually related. Thanks for the info. -- Sean Whitton
signature.asc
Description: PGP signature
