Hi all, [...] > #811841 seqan: FTBFS with GCC 6: no match for > > - refers to v1.4, AFAIK version 2.0 is already in the archive, so this > one should probably me closed.
I don't think it is [1]. Anyway, AFAICS SeqAn 2.0 is intended to go into a separate package seqan2 instead? Some of the recent mails here on this list seem to indicate that? The seqan repo in Git has 2.0 already merged into master but not uploaded yet. Can anybody clarify please? If there is going to be a new repo for seqan2 because of API changes I think it might be worth fixing the GCC6 FTBFS in the 'old' (1.4) seqan package to make sure that important tools depending on 1.4 (such as bowtie, tophat, ...) stay in testing. What do you think? Thanks Sascha [1] https://packages.debian.org/source/unstable/seqan >> >> So anybody with some gcc-6 skills or those who want to ask on Debian >> Mentors list for help which usually receives helpful responses quite >> quickly is invited to work on our bugs. >> >> Kind regards >> >> Andreas. >> >> On Wed, May 04, 2016 at 08:33:08AM +0200, Andreas Tille wrote: >>> >>> Hi, >>> >>> On Mon, Apr 04, 2016 at 09:52:27AM +0100, Sascha Steinbiss wrote: >>>> >>>> >>>> Sure, I will see what I can do. How do you propose we as DMs >>>> communicate >>>> the changes -- just push a new branch in git and ping the list? >>> Sascha, thanks for your good work on several bugs - without >>> counting it >>> was more than one per week. If others might come up with this rate >>> we >>> could be quite safe for the release. But its no time to relax and >>> more >>> bug fixers would be really great. Specifically newcomers could >>> gather >>> some packaging skills by triaging bugs in existing packages. >>> >>> Kind regards >>> >>> Andreas. >>> >>> -- >>> http://fam-tille.de >>> >>> > -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.