1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1108716: octave-biosig: Package octave-biosig can not be loaded in

    From =?utf-8?q?Alois_Schl=C3=B6gl?=@1:229/2 to All on Thu Jul 3 21:30:01 2025
    From: [email protected]

    Package: octave-biosig
    Version: 3.9.0-1
    Severity: important
    X-Debbugs-Cc: [email protected]

    Dear Maintainer,


    * What led up to the situation?

    I recently upgraded to trixie, and tried reinstalling octave-biosig with
    apt-get install octave-biosig
    does run and the package is installed, however
    when starting Octave, the package is not shown and can not be loaded with
    pkg list
    pkg load biosig

    * What exactly did you do (or not do) that was effective (or
    ineffective)?

    apt-file list octave-biosig
    shows the files are installed in
    octave-biosig: /usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu/biosig/mexSSAVE.mex
    ...
    octave-biosig: /usr/share/octave/site/m/biosig/...
    ...
    * What was the outcome of this action?

    and when adding these directories, octave-biosig is usable.

    also when using the method from upstream, installing from source
    pkg install "https://sourceforge.net/projects/biosig/files/Biosig%20for%20Octave/biosig4octave-3.9.0.src.tar.gz"
    the octave-biosig package is installed (in my home directory) and usable.

    * What outcome did you expect instead?

    pkg list
    should list biosig
    pkg load biosig
    should provide the functions in each path, e.g.
    which sload
    which mexSLOAD
    should show the location of these functions.


    -- System Information:
    Debian Release: 13.0
    APT prefers testing
    APT policy: (990, 'testing'), (500, 'testing-security')
    Architecture: amd64 (x86_64)
    Foreign Architectures: i386

    Kernel: Linux 6.12.33+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
    Kernel taint flags: TAINT_WARN
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    Versions of packages octave-biosig depends on:
    ii libbiosig3 3.9.0-1
    ii libc6 2.41-9
    ii octave [octave-abi-59] 9.4.0-1

    octave-biosig recommends no packages.

    octave-biosig suggests no packages.

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From =?utf-8?Q?=C3=89tienne?= Mollier@1:229/2 to All on Thu Jul 3 22:50:01 2025
    From: [email protected]

    Control: tag -1 moreinfo

    Hi Alois,

    I probably should leave that issue to someone fluent with octave
    and probably won't be in position to put useful packaging work
    to resolve the situation (help from someone having some
    experience with octave would be welcome, thanks:), but let's see
    if I can contribute something useful to the bug entry anyway…

    Alois Schlögl, on 2025-07-03:
    * What led up to the situation?

    I recently upgraded to trixie, and tried reinstalling octave-biosig with
    apt-get install octave-biosig
    does run and the package is installed, however
    when starting Octave, the package is not shown and can not be loaded with
    pkg list
    pkg load biosig

    I'm under the impression that the dh-octave scripting is
    supposed to capture and convert the scripting to something
    compatible with octave's integrated package management system.
    However the package is deployed in such manner that it end up
    flat:

    apt-file list octave-biosig
    shows the files are installed in
    octave-biosig: /usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu/biosig/mexSSAVE.mex
    ...
    octave-biosig: /usr/share/octave/site/m/biosig/...
    ...
    * What was the outcome of this action?

    and when adding these directories, octave-biosig is usable.

    The sentence is unclear to me, when adding which directories
    where?

    pkg list
    should list biosig
    pkg load biosig
    should provide the functions in each path, e.g.

    Indeed:

    octave:1> pkg list
    no packages installed.
    octave:2> pkg load biosig
    error: package biosig is not installed
    error: called from
    load_packages at line 47 column 7
    pkg at line 639 column 7

    which sload
    which mexSLOAD
    should show the location of these functions.

    On my end I have something different from what you describre:
    the symbols are identified without loading the packages at all,
    as if they are loaded immediately in the octave namespace:

    octave:1> which sload
    'sload' is a function from the file /usr/share/octave/site/m/biosig/t200_FileAccess/sload.m
    octave:2> which mexSLOAD
    'mexSLOAD' is a function from the file /usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu/biosig/mexSLOAD.mex

    Does that match your observation?

    My current impression is that the package might simply need a
    nudge to get octave-biosig shipped as an octave package, but as
    I mentioned first, I'm not litterate with octave and it's
    packaging at the moment, so I probably won't fix anything any
    time soon. I'm just trying to triage the bug.

    Have a nice day, :)
    --
    .''`. Étienne Mollier <[email protected]>
    : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
    `. `' sent from /dev/pts/1, please excuse my verbosity
    `-

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmhm6/gACgkQeTz2fo8N Edo4uA//SSqaEjSt1wA/xMCciQobmcIcXyWNbAZBHaj1YoKd2+r/8Wj0oIOQ/ziQ AfgloC4HqBQNEnHeLqOP2S1Iklocm8AjDAJR869sJxhJVqKNivpxYvx/oKvMJEOV JaloQeTFZOlRbIXtVxUAVgLKc8HZl//nGnGgL332dcevXTGtVD76l7t6V2CdFAul akvLjESWeY0RLSV0/5NbeveAUpOH6f6ZFKOzM2+esISTVy/ZoLa9JjaGxwTScNm+ UZ1RPQxzlnT0kb+3/sAjeEGX+U31VgLjgCZUKo9Y+zV5rbveWW1R/6EhGPhZZAnx TlyZceEKFqO+avmJ4l+FDrR1Gqqja+1IEogC5Oc5g1LVENSHcWydtlmLc6lEUYtY MkdmTrZyhJxiid1JwLFRvqH8e15T+yZEx69uMwn2lq86q28NABvruKamIAZ+ZRMy puHnlomA8ClWd9geVJpqHNK5lFO2GvVCQOjQzSRtN9VS+8eOGiqrvz0dcq+SUwGQ WN3Ujn6UMPUqyJABJ6ZXWe8BmKSfHulQI32R8TELmAfp3x9tCCy3ZWAo43aBr7e5 tN0ZbrVBlvWfg61ajgoZ/mOmOL1Eh/zbrESsIMFQ0S13b+QzOKPdroTtDBsmfgNo Sjmq5iJHDx+2+9ZPirav4eFRjFiS5FX6dxNF1AOfHYiOyXpSE+0=
    =0+6n
    -----END PGP SIG