Bug#1071237: python3-pyunitsystem: the homepage of the project requires login to be accessed
Package: python3-pyunitsystem Version: 1.1.1-2 Severity: normal Tags: upstream Dear Maintainer, the UL to the homepage of the pyunitsystem project: https://gitlab.esrf.fr/tomotools/pyunitsystem leads to a login page, so the source is only available after subscription to gitla.esrf.fr Since the package isa lso available via pypi, wehre the same URL is given as the homepage, I surmise this to be an oversight in the repository configuration, that the authors intended make fully public like others under tomotools. Note that, at the moment of writing, the version avaialble in pypi is only 1.1.1-1. -- System Information: Debian Release: trixie/sid APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pyunitsystem depends on: ii python3 3.11.8-1 python3-pyunitsystem recommends no packages. python3-pyunitsystem suggests no packages.
Bug#1065876: texlive-extra-utils: The shebang of script de-macro invokes 'python' rather than 'python3'
Package: texlive-extra-utils Version: 2023.20240207-1 Severity: normal Dear Maintainer, I have a paper written in LaTeX that the publisher required to not contain any user macro, so I used de-macro to produce a distributable version with a Makefile target. Today I tried to recreate the distributable paper, and when de-macro was called, as: de-macro Paer.tex I received the error: bash: /usr/bin/de-macro: cannot execute: required file not found however, using: python3 $(which de-macro) Paper.tex works. inspecting the installed de-macro script i found that the cause is the shebang, that is set as: #!/usr/bin/python -O which fails unless package python-is-python3 is installed (I didn't bother checking if it works with python2). The shebang should be changed to use a versioned python executable, since python-is-python3 should not be a dependency of any other package. Thank you for your precious work maintaining the texlive ecosystem. -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files -rw-r--r-- 1 root root 2944 Mar 3 23:28 /var/lib/texmf/ls-R lrwxrwxrwx 1 root root 29 Oct 12 2022 /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN lrwxrwxrwx 1 root root 31 Feb 14 09:08 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST lrwxrwxrwx 1 root root 31 Feb 14 09:08 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files -rw-r--r-- 1 root root 475 Nov 1 02:41 /etc/texmf/web2c/texmf.cnf lrwxrwxrwx 1 root root 33 Feb 14 09:08 /usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN lrwxrwxrwx 1 root root 32 Feb 14 09:08 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN -rw-r--r-- 1 root root 5334 Mar 3 23:22 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Apr 1 2019 mktex.cnf -rw-r--r-- 1 root root 475 Nov 1 02:41 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf -- System Information: Debian Release: trixie/sid APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages texlive-extra-utils depends on: ii libfile-homedir-perl 1.006-2 ii libunicode-linebreak-perl 0.0.20190101-1+b6 ii libyaml-tiny-perl 1.74-1 ii python33.11.6-1 ii tex-common 6.18 ii texlive-base 2023.20240207-1 ii texlive-binaries 2023.20230311.66589-9 ii texlive-latex-base 2023.20240207-1 ii texlive-luatex 2023.20240207-1 ii texlive-plain-generic 2023.20240207-1 Versions of packages texlive-extra-utils recommends: ii ghostscript10.02.1~dfsg-3 ii liblog-log4perl-perl 1.57-1 ii ruby
Bug#1000457: virtualbox: Outdated dependency on libgsoap-2.8.104
Package: virtualbox Version: 6.1.28-dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to upgrade virtualbox to Version: 6.1.28-dfsg-1 aptitude was not able to resolve dependencies. I uninstalled the previous version and then tryed to install again, but foud that virtualbox depends on libgsoap-2.8.104, that is not available in unstable. Proposed solution: depend on libgsoap-2.8.117 Thank you for maintaining the package. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox depends on: ii adduser 3.118 ii iproute2 5.15.0-1 ii libc6 2.32-4 ii libcurl3-gnutls 7.79.1-2 ii libdevmapper1.02.12:1.02.175-2.1 ii libgcc-s1 11.2.0-10 ii libgl11.3.4-2+b1 pn libgsoap-2.8.104 ii liblzf1 3.6-3 ii libopus0 1.3.1-0.1 ii libpng16-16 1.6.37-3 ii libpython3.9 3.9.9-1 ii libsdl1.2debian 1.2.15+dfsg2-6 ii libssl1.1 1.1.1l-1 ii libstdc++611.2.0-10 ii libvncserver1 0.9.13+dfsg-3 ii libvpx6 1.10.0-2 ii libx11-6 2:1.7.2-2+b1 ii libxcursor1 1:1.2.0-2 ii libxml2 2.9.12+dfsg-5+b1 ii libxt61:1.2.0-1 ii procps2:3.3.17-5 ii python3 3.9.7-1 ii python3.9 3.9.9-1 ii virtualbox-dkms [virtualbox-modules] 6.1.28-dfsg-1~fto11+1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages virtualbox recommends: ii libqt5core5a5.15.2+dfsg-13 ii libqt5gui5 5.15.2+dfsg-13 ii libqt5opengl5 5.15.2+dfsg-13 ii libqt5widgets5 5.15.2+dfsg-13 ii libxcb1 1.14-3 ii libxext62:1.3.4-1 pn virtualbox-qt Versions of packages virtualbox suggests: pn vde2 pn virtualbox-guest-additions-iso
Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.
Package: gimp Version: 2.10.8-2+b1 Severity: grave Justification: renders package unusable Dear Maintainer, I currently use testing (bullseye), amd since the last upgrade, GIMP keeps crashing whwnever I open am image or even create new one. The images in question were edited minutes before the upgrade, so they should adhere to the latest format specification. The issue was noticed while using gimp-console and python-fu to convert the images to pdf as part of the compilation of a latex document, and later veriied to happen within the GUI. This makes GIMP unusable. The debug information is after the System information -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.8-2 ii libaa1 1.4p5-46+b1 ii libbabl-0.1-00.1.62-1 ii libbz2-1.0 1.0.6-9.2 ii libc62.28-10 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2+b1 ii libfreetype6 2.9.1-4 ii libgcc1 1:9.2.1-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgegl-0.4-00.4.12-2 ii libgexiv2-2 0.10.9-1 ii libgimp2.0 2.10.8-2+b1 ii libglib2.0-0 2.60.6-2 ii libgs9 9.27~dfsg-3.1 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b2.6.1-2 ii libheif1 1.5.1-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3+b1 ii liblzma5 5.2.4-1+b1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2.1+b1 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.0-2 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpangoft2-1.0-01.42.4-7 ii libpng16-16 1.6.37-1 ii libpoppler-glib8 0.71.0-5+b1 ii librsvg2-2 2.44.14-1 ii libstdc++6 9.2.1-4 ii libtiff5 4.0.10+git190818-1 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libwmf0.2-7 0.2.8.4-14 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.2.0-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages gimp recommends: ii ghostscript 9.27~dfsg-3.1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help ii gimp-python 2.10.8-2+b1 ii gvfs-backends 1.38.1-5 ii libasound21.1.8-1 -- no debconf information -- Debug information: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo versio
Bug#930525: xcftools: files created with gimp-2.10 are not supported
Package: xcftools Version: 1.0.7-6 Severity: important Dear Maintainer, The current version of xfctools prints the following message: Warning: XCF version 11 not supported (trying anyway...) when converting an image created with the suggested version of gimp. The resulting image (example command: xcf2png test.xcf -o test.png) consists of a transparent layer only. This makes the tool unusable with all xcf files that are modified using the latest (and suggested)d version of gimp. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xcftools depends on: ii libc62.28-10 ii libpng16-16 1.6.36-6 ii xdg-utils1.1.3-1 Versions of packages xcftools recommends: ii mime-support 3.62 Versions of packages xcftools suggests: ii gimp2.10.8-2 ii x11-common 1:7.7+19 -- no debconf information
Bug#928521: rmlint-gui: File size limits lower than 1 Mb are treated as 0 Mb
Package: rmlint-gui
Version: 2.8.0-3
Severity: normal
Tags: patch
Dear Maintainer,
In an attempt to only delete duplicates fo non-empty files, I set a lower size
limit on the duplicate file size of a few bytes, in the Settings view of the
gui, but shredder kept reporting them.
Clicking on the 'Generate script' button I saw in the script that the rmlint
command line that run by shredder contained the option:
"--size 0M-17179869184M"
This was observed to happen with lower limit up to 999 kb, and causes files
smaller than the set limit to be listed anyways and worse, if the upper limit
is also lower than 1 Mb, then only empty files are listed.
The observed result is that any file size limit lower than 1 Mb (both lower and
upper) is forced to 0 Mb before it is passed to the command line scanner with
incorrect value.
The expected result is that file size limits are passed correctly to the
command line scanner and no manual selection is needed to exclude unwanted
matches from deletion.
The issue can be tracked down to lines 177--181 of file
'/usr/lib/python3/dist-packages/shredder/runner.py'
%<--
extra_options += [
'--size', '{a}M-{b}M'.format(
a=min_size // (1024 ** 2),
b=max_size // (1024 ** 2)
)
%<--
where all file size limits are converted to Mb, truncating to an integer.
The issue has already been reported and fixed upstream:
https://github.com/sahib/rmlint/commit/5a5cf895df405ae4eb3d4d9dd87d5c76de66dbbc
Please incorporate the fix at your leisure.
PS. I am not certain that adding the patch tag because I provide a link to the
commit that fixes
the bug upstream is the correct thing to do, do in case it is not,
remove it.
Best regards,
Diego
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT:it (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rmlint-gui depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii gir1.2-gtksource-3.0 3.24.9-2
ii gir1.2-polkit-1.00.105-25
ii gir1.2-rsvg-2.0 2.44.10-2.1
ii python3 3.7.2-1
ii python3-cairo1.16.2-1+b1
ii python3-gi 3.30.4-1
ii rmlint 2.8.0-3
Versions of packages rmlint-gui recommends:
ii python3-colorlog 4.0.1-1
rmlint-gui suggests no packages.
-- no debconf information
Bug#872814: sakura: terminal window closes when pressing any key
Thanks, I imagined as much, but I figured that an actual bug report could help track the resolution of the issue. --- Diego Caraffini Anar caluva tielyanna (The Sun shall shine on your path) from Unfinished Tales by JRR Tolkien On Mon, Aug 21, 2017 at 10:41 AM, Andreas Ronnquist wrote: > Control: forwarded -1 https://bugs.launchpad.net/sakura/+bug/1658413 > Control: tag -1 + pending > > > > > Dear Maintainer, > > > > I used "aptitude safe-update" to transition from Stretch to Buster a > > couple of weeks ago; since then I run aptitude update a few times. > > Over the last few days, the sakura temninal window closes on its own > > as soon as I try to type a command. > > > > Yeah, this is due to the bug you mentioned, and you running Wayland. > I'll provide an updated Debian package, either with patches fixing it, > or a new upstream release fixing this if it released soon. There's a > patch provided in the upstream report. > > I am waiting and hoping for a new upstream release, but since it's > vacation times, it could be some time. > > -- Andreas Rönnquist > gus...@debian.org >
