Package: aoflagger Severity: normal X-Debbugs-Cc: offri...@gmail.com Dear Maintainer,
The AOFlagger software provides a Python interface that users can use to flag data from Python. However, the Debian AOFlagger package does not include the Python library for AOFlagger. I get quite some questions about people that would like to use the Python interface and get confused that they can't do `import aoflagger` after having installed the Debian package, so it would be great if this could be fixed. If changes are needed upstream I'm happy to make these, but I suspect it's just a packaging issue. Thanks, André -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_NL.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aoflagger depends on: pn libaoflagger0 <none> ii libatkmm-1.6-1v5 2.28.3-1 ii libboost-filesystem1.74.0 1.74.0+ds1-22 ii libc6 2.37-7 ii libcairomm-1.0-1v5 1.14.4-2 pn libcasa-casa7 <none> pn libcasa-ms7 <none> pn libcasa-tables7 <none> ii libgcc-s1 13.2.0-3 ii libglibmm-2.4-1v5 2.66.6-2 ii libgtkmm-3.0-1v5 3.24.8-2 ii libpangomm-1.4-1v5 2.46.3-1 ii libsigc++-2.0-0v5 2.12.0-1 ii libstdc++6 13.2.0-3 aoflagger recommends no packages. Versions of packages aoflagger suggests: pn aoflagger-dev <none>
