Your message dated Fri, 19 Jan 2024 20:24:41 +0100 with message-id <dd62f1e781b31bb55536235787617f39533f2c53.ca...@debian.org> and subject line Re: Bug#1061017: octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 has caused the Debian Bug report #1061017, regarding octave-divand: FTBFS: make: *** [debian/rules:5: binary] Error 134 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 ow...@bugs.debian.org immediately.) -- 1061017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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 > /<<BUILDDIR>>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages > > /<<BUILDDIR>>/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] > >>>>> /<<PKGBUILDDIR>>/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) [42m OK [0m > run test_interp_2d: (max difference=2.22045e-16) [42m OK [0m > run test_interp_regular: (max difference=2.22045e-16) [42m OK [0m > run test_sparse_diff: (max difference=0) [42m OK [0m > 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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240115&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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.
--- End Message ---
--- Begin Message ---Le mercredi 17 janvier 2024 à 12:42 +0100, Sébastien Villemot a écrit : > 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 > > > /<<BUILDDIR>>/octave-divand-1.1.2\+dfsg/debian/octave-divand/usr/share/octave/packages > > > > > > /<<BUILDDIR>>/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] > > > > > > > > /<<PKGBUILDDIR>>/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) [42m OK [0m > > > run test_interp_2d: (max difference=2.22045e-16) [42m OK [0m > > > run test_interp_regular: (max difference=2.22045e-16) [42m OK [0m > > > run test_sparse_diff: (max difference=0) [42m OK [0m > > > 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. The ABI breakage has been fixed. Closing. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.orgsignature.asc
Description: This is a digitally signed message part
--- End Message ---