Package: mini-dinstall Version: 0.7.0 Severity: important Dear Maintainer,
TL;DR: On line 1133 mini-dinstall opens a process for apt-ftparchive, setting stderr to pipe but never actually reading it. This causes mini-dinstall to hang when there is lots of output on stderr as the process never completes. Setting stderr to None instead of PIPE on line 1133 resolves the issue. Long version: I'm using mini-dinstall to add packages to a internal repository. Some of these packages cause apt-ftparchive to complain on stderr when generating the Sources file for the repository. Since lots of packages are generated (by a build server) there is lots of stderr output too. Today this started to cause mini-dinstall -b to hang when adding new packages. A quick check seems to suggest the amount of output on stderr just exceeds 64K at the moment wich is probably where this issue is triggered. I can work around it locally by ignoring stderr instead of piping it which in the subprocess.Popen() call. This may not be a desirable solution (although stderr output is ignored as it is as well), but works for me. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mini-dinstall depends on: ii apt-utils 2.2.4 ii python3 3.9.2-3 ii python3-apt 2.2.0 Versions of packages mini-dinstall recommends: ii gpgv 2.2.27-2 Versions of packages mini-dinstall suggests: pn debian-keyring <none> -- no debconf information