<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all,<div class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">BTW, nice to see progress on seqan2 :) Once that’s through NEW I have a small addition to make that would also get lambda-align in (and probably more seqan2 dependent tools built with their CMake module).</blockquote><br class="">Please make sure to deal with any issues raised by ftpmaster since I<br class="">definitely can't do anything for seqan2 any more the next 2.5 weeks.<br class=""></div></div></blockquote><div><br class=""></div><div>Looks like that wasn’t necessary as seqan2 is now in unstable :)</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">Please also ask removal of seqan-apps coming from seqan (1.x) package<br class="">to enable testing migration.<br class=""></div></div></blockquote><div><br class=""></div><div>Just took a look — I wonder why <a href="https://qa.debian.org/excuses.php?package=seqan" class="">https://qa.debian.org/excuses.php?package=seqan</a> also lists seqan-dev as missing for the archs in question, but in fact was always arch:all. This shouldn’t be RM’d, right?! I can see that seqan-apps is now built by src:seqan2, but AFAICS the old seqan-dev can and should stay?</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">I hope to see seqan 1 and 2 in testing once I'm back. :-)<br class=""></div></div></blockquote><div><br class=""></div><div>So do I, I’ll also make sure to add the seqan2 CMake modules so we can build other stuff depending on seqan2.</div></div><br class=""></div><div class="">Cheers</div><div class="">Sascha</div></body></html>