• Bug#1098585: octave-ncarray: FTBFS: NetCDF: Not a valid data type or _F

    From Santiago Vila@21:1/5 to All on Sat Feb 22 00:40:12 2025
    Package: src:octave-ncarray
    Version: 1.0.6-1
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

    During a rebuild of all packages in unstable, your package failed to build:

    --------------------------------------------------------------------------------
    [...]
    debian/rules clean
    dh clean --buildsystem=octave
    dh_auto_clean -O--buildsystem=octave
    dh_octave_clean
    make[1]: Entering directory '/<<PKGBUILDDIR>>'
    ## Cleaning release tarballs (package + html)...
    rm -f target/ncarray-1.0.6.tar.gz target/ncarray-html.tar.gz

    ## Cleaning unpacked release tarballs (package + html)...
    rm -f -r target/ncarray-1.0.6 target/ncarray-html

    ## Cleaning installation under /<<PKGBUILDDIR>>/target/.installation ...
    rm -f -r /<<PKGBUILDDIR>>/target/.installation

    ## Removing fntests.log...
    rm -f target/fntests.log

    ## Removing target directory (if empty)...
    if [ -d target ]; then rmdir target; fi

    ## Cleaning done

    make[1]: *** No rule to make target 'distclean'.
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make[1]: Entering directory '/<<PKGBUILDDIR>>'
    make[1]: *** src: No such file or directory. Stop.
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    dh_autoreconf_clean -O--buildsystem=octave
    dh_clean -O--buildsystem=octave
    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-ncarray/ -O--buildsystem=octave
    octave --no-gui --no-history --silent --no-init-file --no-window-system /usr/share/dh-octave/install-pkg.m /<<PKGBUILDDIR>>/debian/octave-ncarray/usr/share/octave/packages /<<PKGBUILDDIR>>/debian/octave-ncarray/usr/lib/x86_64-linux-gnu/octave/packages
    For information about changes from previous versions of the ncarray package, run 'news ncarray'.
    dh_octave_check -O--buildsystem=octave
    Checking package...
    Run the unit tests...
    Checking m files ...
    [inst/test_ncarray.m]
    /<<PKGBUILDDIR>>/inst/test_ncarray.m
    ***** test
    test_ncarray()
    !!!!! test failed
    NetCDF: Not a valid data type or _FillValue type mismatch
    1 test, 0 passed, 0 known failure, 0 skipped
    [inst/test_ncarray_nan.m]
    /<<PKGBUILDDIR>>/inst/test_ncarray_nan.m
    ***** test
    test_ncarray_nan ()
    !!!!! test failed
    NetCDF: Not a valid data type or _FillValue type mismatch
    1 test, 0 passed, 0 known failure, 0 skipped
    Checking C++ files ...
    Done running the unit tests.
    Summary: 2 tests, 0 passed, 0 known failures, 0 skipped
    Some tests failed. Giving up...
    make: *** [debian/rules:5: binary] Error 1
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/202502/

    About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:octave-ncarray, so that this is still visible in the BTS web page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Mar 11 07:40:01 2025
    Processing control commands:

    tag -1 pending
    Bug #1098585 [src:octave-ncarray] octave-ncarray: FTBFS: NetCDF: Not a valid data type or _FillValue type mismatch
    Added tag(s) pending.

    --
    1098585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098585
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?UmFmYWVsIExhYm9pc3Npw6hyZ@21:1/5 to All on Tue Mar 11 07:40:02 2025
    Control: tag -1 pending

    Hello,

    Bug #1098585 in octave-ncarray reported by you has been fixed in the
    Git repository and is awaiting an upload. You can see the commit
    message below and you can check the diff of the fix at:

    https://salsa.debian.org/pkg-octave-team/octave-ncarray/-/commit/c9a631d5cefba3d6b0e9450782b104ee94cfb599

    ------------------------------------------------------------------------ d/p/fillvalue-type.patch: New patch

    Closes: #1098585 ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1098585

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Mar 11 08:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Tue, 11 Mar 2025 06:51:28 +0000
    with message-id <E1trtSa-003Lz8-1M@fasolo.debian.org>
    and subject line Bug#1098585: fixed in octave-ncarray 1.0.6-2
    has caused the Debian Bug report #1098585,
    regarding octave-ncarray: FTBFS: NetCDF: Not a valid data type or _FillValue type mismatch
    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.)


    --
    1098585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098585
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 21 Feb 2025 23:28:10 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-121.6 required=4.0 tests=ALL_TRUSTED,BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_PASS,
    SPF_NONE,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 42; hammy, 150; neutral, 132; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--sk:dh_auto, 0.000-+--H*F:U*sanvila Return-path: <sanvila@debian.org>
    Received: from mailly.debian.org ([2001:41b8:202:deb:6564:a62:52c3:4b72