Hello,
On September 12, 2018 5:30:59 AM EDT, Andreas Tille wrote:
>Hi Alex,
>
>On Wed, Sep 12, 2018 at 10:55:20AM +0200, Alex Mestiashvili wrote:
>> Well, according upstream, current repository is not active anymore:
>>
>>
>> Oh, sorry. We are no longer mirroring our internal FALCON repo here.
Hi Alex,
On Wed, Sep 12, 2018 at 10:55:20AM +0200, Alex Mestiashvili wrote:
> Well, according upstream, current repository is not active anymore:
>
>
> Oh, sorry. We are no longer mirroring our internal FALCON repo here. In
> fact, I think this Issues board will disappear soon too, in favor of
Well, according upstream, current repository is not active anymore:
Oh, sorry. We are no longer mirroring our internal FALCON repo here. In
fact, I think this Issues board will disappear soon too, in favor of
pbbioconda. So I think your source-code is way out of date.
Unfortunately, my hands are
Hi Andreas,
I've pushed some commits and opened upstream issue[0].
Also it seems that falcon depends on python-future >=0.16.0 which is not
yet available - #863215.
[0] https://github.com/PacificBiosciences/FALCON/issues/672
Best regards,
Alex
Source: falcon
Version: 1.8.8-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
User: debian...@lists.debian.org
Usertags: needs-update
Dear Afif,
Follow-up from the thread starting here:
https://alioth-lists.debian.net/pipermail/debian-med-packaging/2018-June/063209.html
falcon FTBFS since
5 matches
Mail list logo
