Hi, I had a quick look into lambda-align since I became aware of bug #1113092. A fix is (as probably for all CMake 4 related bugs easiy and a NMU to delayed=12 pending - thanks as always to Adrian for his great QA work).
I had a look anyway and realised that we have an updated package in experimental which is using some newer seqan2 version. I wonder whether this experiment was successfully and can be moved to unstable. If not we probably should apply the same fix to the branch in experimental to make sure it keeps on building. I admit I would love to see this sorted out before the NMU hits unstable. Its a bit hard to adjust the history in changelog otherwise. As a general question: There is lambda-align (featuring the latest version of the 1.x series), lambda-align2 (featuring the latest version of the 2.x series) and upstream has also issued lamda-align version 3. Do we really need both old versions but not the latest one? The *real* usage stats of lamda-align (1.x) https://qa.debian.org/popcon-graph.php?packages=lambda-align&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 is less than from lambda-align2 https://qa.debian.org/popcon-graph.php?packages=lambda-align2&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 BTW, its really interesting that starting with the Trixie release the installed popcon of both made a big jump ... and I guess from other Debian Med packages as well. My guess is that the installer featuring Blends might have some influence here. Kind regards Andreas. -- https://fam-tille.de
