Source: octave-jnifti
Version: 0.6-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir inst
> cp lib/matlab/DESCRIPTION .
> cp lib/matlab/INDEX .
> cp lib/matlab/*.m inst
> cp lib/octave/*.m inst
> cp lib/matlab/LICENSE_GPLv3.txt COPYING
> sed -i -e 's/^%!.*$//g' inst/niftiread.m inst/niftiwrite.m inst/niftiinfo.m
> rm -rf inst/gzip*.m
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    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_installdirs -O--buildsystem=octave
>    dh_auto_install -O--buildsystem=octave
>       octave --no-gui --no-history --silent --no-init-file --no-window-system 
> /usr/share/dh-octave/install-pkg.m 
> /<<PKGBUILDDIR>>/debian/tmp/usr/share/octave/packages 
> /<<PKGBUILDDIR>>/debian/tmp/usr/lib/x86_64-linux-gnu/octave/packages
> warning: creating installation directory 
> /<<PKGBUILDDIR>>/debian/tmp/usr/share/octave/packages
> warning: called from
>     install at line 36 column 5
>     pkg at line 603 column 9
>     /usr/share/dh-octave/install-pkg.m at line 38 column 1
> 
>    dh_octave_check -O--buildsystem=octave
> Checking package...
> Checking m files ...
> Checking C++ files ...
> Summary: 0 tests, 0 passed, 0 known failures, 0 skipped
>    dh_install -O--buildsystem=octave
>    dh_installdocs -O--buildsystem=octave
>    dh_installchangelogs -O--buildsystem=octave
>    dh_octave_changelogs -O--buildsystem=octave
>    dh_installexamples -O--buildsystem=octave
>    dh_octave_examples -O--buildsystem=octave
> dh_octave_examples: warning: skipping link from 
> usr/share/doc/jnifti-demos/examples to self
>    dh_installsystemduser -O--buildsystem=octave
>    dh_perl -O--buildsystem=octave
>    dh_link -O--buildsystem=octave
>    dh_strip_nondeterminism -O--buildsystem=octave
>    dh_compress -O--buildsystem=octave
>    dh_fixperms -O--buildsystem=octave
>    dh_missing -O--buildsystem=octave
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/doc-cache exists 
> in debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/jnifticreate.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/jnifticreate.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/jnii2nii.m exists 
> in debian/tmp but is not installed to anywhere (related file: 
> "inst/jnii2nii.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/loadjnifti.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/loadjnifti.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/loadnifti.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/loadnifti.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/memmapstream.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/memmapstream.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/nifticreate.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/nifticreate.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/niftiinfo.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/niftiinfo.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/niftiread.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/niftiread.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/niftiwrite.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/niftiwrite.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/nii2jnii.m exists 
> in debian/tmp but is not installed to anywhere (related file: 
> "inst/nii2jnii.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/niicodemap.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/niicodemap.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/niiformat.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/niiformat.m")
> dh_missing: warning: 
> usr/share/octave/packages/jnifti-0.6.1/packinfo/DESCRIPTION exists in 
> debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/packinfo/INDEX 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/savebnii.m exists 
> in debian/tmp but is not installed to anywhere (related file: 
> "inst/savebnii.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/savejnifti.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/savejnifti.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/savejnii.m exists 
> in debian/tmp but is not installed to anywhere (related file: 
> "inst/savejnii.m")
> dh_missing: warning: usr/share/octave/packages/jnifti-0.6.1/savenifti.m 
> exists in debian/tmp but is not installed to anywhere (related file: 
> "inst/savenifti.m")
> dh_missing: error: missing files, aborting
> 
>       While detecting missing files, dh_missing noted some files with a 
> similar name to those
>       that were missing.  This error /might/ be resolved by replacing 
> references to the
>       missing files with the similarly named ones that dh_missing found - 
> assuming the content
>       is identical.
> 
>       As an example, you might want to replace:
>        * inst/jnifticreate.m
>       with:
>        * usr/share/octave/packages/jnifti-0.6.1/jnifticreate.m
>       in a file in debian/ or as argument to one of the dh_* tools called 
> from debian/rules.
>       (Note it is possible the paths are not used verbatim but instead 
> directories 
>       containing or globs matching them are used instead)
> 
>       Alternatively, add the missing file to debian/not-installed if it 
> cannot and should not
>       be used.
> 
>       The following debhelper tools have reported what they installed (with 
> files per package)
>        * dh_install: jnifti-demos (0), matlab-jnifti (16), octave-jnifti (0)
>        * dh_installdocs: jnifti-demos (0), matlab-jnifti (0), octave-jnifti 
> (3)
>        * dh_installexamples: jnifti-demos (4), matlab-jnifti (0), 
> octave-jnifti (0)
>       If the missing files are installed by another tool, please file a bug 
> against it.
>       When filing the report, if the tool is not part of debhelper itself, 
> please reference the
>       "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
> for debhelper (10.6.3+).
>         (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
>       Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
> when only a subset is built
>       If the omission is intentional or no other helper can take care of this 
> consider adding the
>       paths to debian/not-installed.
> make: *** [debian/rules:5: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/octave-jnifti_0.6-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&[email protected]&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 marking 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.

Reply via email to