Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

Hello, على الأربعاء 7 حزيران 2017 ‫08:40، كتب Andreas Tille: > Hi Adrian, > > On Wed, Jun 07, 2017 at 03:26:49PM +0300, Adrian Bunk wrote: >> >>> NMUs are in any case OK for any Debian Med package. I would have >>> uploaded as well if I would know the best solution. So please apply >>> what

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

Hi Adrian, On Wed, Jun 07, 2017 at 03:26:49PM +0300, Adrian Bunk wrote: > > > NMUs are in any case OK for any Debian Med package. I would have > > uploaded as well if I would know the best solution. So please apply > > what you consider best and upload as soon as possible. Alternatively > >

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

On Wed, Jun 07, 2017 at 01:02:02PM +0200, Andreas Tille wrote: > Hi, Hi Andreas, > NMUs are in any case OK for any Debian Med package. I would have > uploaded as well if I would know the best solution. So please apply > what you consider best and upload as soon as possible. Alternatively >

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

Hi, NMUs are in any case OK for any Debian Med package. I would have uploaded as well if I would know the best solution. So please apply what you consider best and upload as soon as possible. Alternatively send a patch and I'll hurry up. Thanks a lot Andreas. On Wed, Jun 07, 2017 at

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

On Wed, 7 Jun 2017 12:28:41 +0300 Adrian Bunk wrote: > > What about explicitly stating all 64bit architectures? > > Is it OK if I do an NMU to get this into stretch? I would say: do it, don't ask. Time is running out. Just take care of the fallout, and the ANAIS RM bug. (I'm

Bug#863929: Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

On Tue, Jun 06, 2017 at 09:54:38AM +0200, Andreas Tille wrote: > Hi Afif, > > On Tue, Jun 06, 2017 at 03:10:46AM -0400, Afif Elghraoui wrote: > > > > It actually does not even make sense to have this package available for > > a 32-bit architecture since, for any actual use (de novo genome > >

Bug#863929: Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

Hi Afif, On Tue, Jun 06, 2017 at 03:10:46AM -0400, Afif Elghraoui wrote: > > It actually does not even make sense to have this package available for > a 32-bit architecture since, for any actual use (de novo genome > assembly), it will require more memory than would be addressable on a > 32-bit

Bug#863929: [Debian-med-packaging] Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

على الجمعـة 2 حزيران 2017 ‫15:40، كتب Adrian Bunk: > On Fri, Jun 02, 2017 at 03:52:51PM +0200, Graham Inggs wrote: >> According to the reproducible build history [1], this package has FTBFS on >> i386 for a long time. >> >> It also never successfully built on i386 in Ubuntu [2]. >> >> If there

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

On Fri, Jun 02, 2017 at 03:52:51PM +0200, Graham Inggs wrote: > According to the reproducible build history [1], this package has FTBFS on > i386 for a long time. > > It also never successfully built on i386 in Ubuntu [2]. > > If there are no objections, I will file a bug requesting removal of

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

According to the reproducible build history [1], this package has FTBFS on i386 for a long time. It also never successfully built on i386 in Ubuntu [2]. If there are no objections, I will file a bug requesting removal of the i386 binary package. [1]

Bug#863929: falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001) failed with exit-code=256")

tags 863929 help thanks Hi, just to let you know: I'm basically offline until Tuesday and thus can not do anything quickly, neither do I have the slightest idea what might cause this issue after having just a quick look. Kind regards Andreas. -- http://fam-tille.de