Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-17 Thread Sébastien Villemot
Control: block -1 by 1061049

Le mardi 16 janvier 2024 à 20:43 +0100, Lucas Nussbaum a écrit :
> Source: octave-divand
> Version: 1.1.2+dfsg-6
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240115 ftbfs-trixie
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> >  debian/rules binary
> > dh binary --buildsystem=octave
> >dh_update_autotools_config -O--buildsystem=octave
> >dh_autoreconf -O--buildsystem=octave
> >dh_octave_version -O--buildsystem=octave
> > Checking the Octave version... ok
> >dh_auto_configure -O--buildsystem=octave
> >dh_auto_build -O--buildsystem=octave
> >dh_auto_test -O--buildsystem=octave
> >create-stamp debian/debhelper-build-stamp
> >dh_testroot -O--buildsystem=octave
> >dh_prep -O--buildsystem=octave
> >dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave
> > octave --no-gui --no-history --silent --no-init-file --no-window-system 
> > /usr/share/dh-octave/install-pkg.m 
> > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages
> >  
> > /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages
> > For information about changes from previous versions of the divand package, 
> > run 'news divand'.
> >dh_octave_check -O--buildsystem=octave
> > Checking package...
> > Run the unit tests...
> > Checking m files ...
> > [inst/statevector_init.m]
> > > > > > > /<>/inst/statevector_init.m
> > * test
> >  mask = rand(10,10) > .5;
> >  mask_u = rand(9,10) > .5;
> >  mask_v = rand(10,9) > .5;
> >  sv = statevector_init(mask,mask_u,mask_v);
> >  var = rand(10,10); 
> >  var(mask==0) = 0;
> >  var_u = rand(9,10);
> >  var_u(mask_u==0) = 0;
> >  var(mask==0) = 0;
> >  var_v = rand(10,9);
> >  var_v(mask_v==0) = 0;
> >  [E] = statevector_pack(sv,var,var_u,var_v);
> >  [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E);
> >  assert(Ezeta2,var)
> >  assert(Eu2,var_u)
> >  assert(Ev2,var_v)
> > 1 test, 1 passed, 0 known failure, 0 skipped
> > Checking C++ files ...
> > Run tests in debian/check.m
> > [test_divand]
> > run test_interp_1d: (max difference=2.77556e-16)   OK  
> > run test_interp_2d: (max difference=2.22045e-16)   OK  
> > run test_interp_regular: (max difference=2.22045e-16)   OK  
> > run test_sparse_diff: (max difference=0)   OK  
> > run test_1dvar: malloc(): invalid size (unsorted)
> > fatal: caught signal Aborted -- stopping myself...
> > Aborted
> > make: *** [debian/rules:5: binary] Error 134

Thanks. This is a consequence of the ABI break in libcholmod5. Tagging
accordingly.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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


Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134

2024-01-16 Thread Lucas Nussbaum
Source: octave-divand
Version: 1.1.2+dfsg-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=octave
>dh_update_autotools_config -O--buildsystem=octave
>dh_autoreconf -O--buildsystem=octave
>dh_octave_version -O--buildsystem=octave
> Checking the Octave version... ok
>dh_auto_configure -O--buildsystem=octave
>dh_auto_build -O--buildsystem=octave
>dh_auto_test -O--buildsystem=octave
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=octave
>dh_prep -O--buildsystem=octave
>dh_auto_install --destdir=debian/octave-divand/ -O--buildsystem=octave
>   octave --no-gui --no-history --silent --no-init-file --no-window-system 
> /usr/share/dh-octave/install-pkg.m 
> /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages
>  
> /<>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/lib/x86_64-linux-gnu/octave/packages
> For information about changes from previous versions of the divand package, 
> run 'news divand'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Run the unit tests...
> Checking m files ...
> [inst/statevector_init.m]
> > /<>/inst/statevector_init.m
> * test
>  mask = rand(10,10) > .5;
>  mask_u = rand(9,10) > .5;
>  mask_v = rand(10,9) > .5;
>  sv = statevector_init(mask,mask_u,mask_v);
>  var = rand(10,10); 
>  var(mask==0) = 0;
>  var_u = rand(9,10);
>  var_u(mask_u==0) = 0;
>  var(mask==0) = 0;
>  var_v = rand(10,9);
>  var_v(mask_v==0) = 0;
>  [E] = statevector_pack(sv,var,var_u,var_v);
>  [Ezeta2,Eu2,Ev2] = statevector_unpack(sv,E);
>  assert(Ezeta2,var)
>  assert(Eu2,var_u)
>  assert(Ev2,var_v)
> 1 test, 1 passed, 0 known failure, 0 skipped
> Checking C++ files ...
> Run tests in debian/check.m
> [test_divand]
> run test_interp_1d: (max difference=2.77556e-16)   OK  
> run test_interp_2d: (max difference=2.22045e-16)   OK  
> run test_interp_regular: (max difference=2.22045e-16)   OK  
> run test_sparse_diff: (max difference=0)   OK  
> run test_1dvar: malloc(): invalid size (unsorted)
> fatal: caught signal Aborted -- stopping myself...
> Aborted
> make: *** [debian/rules:5: binary] Error 134


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/octave-divand_1.1.2+dfsg-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240115;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240115=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.