[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-octave-devel] Bug#760271: marked as done (octave: Random FTBFS on armhf: panic: Segmentation fault -- stopping myself...)

Your message dated Mon, 24 Nov 2014 14:10:23 +0100
with message-id <1416834623.26202.43.camel@krishna.villemot.name>
and subject line Re: [Pkg-octave-devel] Bug#760271: octave: Random FTBFS on armhf: panic: Segmentation fault -- stopping myself...
has caused the Debian Bug report #760271,
regarding octave: Random FTBFS on armhf: panic: Segmentation fault -- stopping myself...
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
760271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: octave
Version: 3.8.2-2
Severity: important

Gilles Filippini a écrit , Le 01/09/2014 01:18:
> Sébastien Villemot a écrit , Le 01/09/2014 00:19:
>> As you may have noted, the HDF5 transition is now almost finished for
>> packages maintained by the Debian Octave Group. There however remains
>> one last blocker: octave FTBFS on armhf (with a segfault). I have not
>> been able to reproduce the segfault on the porterbox (harris). And it
>> looks like a give back may solve the problem (version 3.8.2-1+b1 first
>> failed, then compiled), even though this is not a real fix.
> 
> An option would be to build the armhf binNMU on a porter box and upload
> that. I can take care of that if nobody objects.

It did that and it went fine.
Filing a bug Severity: important to keep track of this random FTBFS
problem.

Related build logs at:
https://buildd.debian.org/status/logs.php?pkg=octave&ver=3.8.2-2&arch=armhf

Thanks,

_g.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Le mardi 02 septembre 2014 à 12:26 +0200, Gilles Filippini a écrit :
> Source: octave
> Version: 3.8.2-2
> Severity: important
> 
> Gilles Filippini a écrit , Le 01/09/2014 01:18:
> > Sébastien Villemot a écrit , Le 01/09/2014 00:19:
> >> As you may have noted, the HDF5 transition is now almost finished for
> >> packages maintained by the Debian Octave Group. There however remains
> >> one last blocker: octave FTBFS on armhf (with a segfault). I have not
> >> been able to reproduce the segfault on the porterbox (harris). And it
> >> looks like a give back may solve the problem (version 3.8.2-1+b1 first
> >> failed, then compiled), even though this is not a real fix.
> > 
> > An option would be to build the armhf binNMU on a porter box and upload
> > that. I can take care of that if nobody objects.
> 
> It did that and it went fine.
> Filing a bug Severity: important to keep track of this random FTBFS
> problem.
> 
> Related build logs at:
> https://buildd.debian.org/status/logs.php?pkg=octave&ver=3.8.2-2&arch=armhf

This FTBFS was caused by a bug in fftw3 (#767138), which is now fixed.

I could verify that octave now compiles successfully on armhf on both
machines with NEON support (asachi.d.o) and without (abel.d.o). Hence
closing.

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://sebastien.villemot.name
  `-      GPG Key: 4096R/381A7594

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: