Package: libseafile0 Version: 6.1.5-1 Severity: critical Justification: breaks unrelated software
Dear Maintainer, libseafile0 is marked as Multi-Arch: same but its postinst and preinst scripts call pycompile and pyclean without specifying the package architecture. As a result if libseafile0 is installed for more than one architecture the package name is ambiguous, causing the postinst and prerm scripts fail. This then prevents any package from being installed or removed, thus breaking the packaging system permanently (hence the critical severity). The solution is to replace the following line in /var/lib/dpkg/info/libseafile0:*.postinst pycompile -p libseafile0 with pycompile -p libseafile0:$DPKG_MAINTSCRIPT_ARCH And the following lines in /var/lib/dpkg/info/libseafile0:*.prerm pyclean -p libseafile0 else dpkg -L libseafile0 | grep '\.py$' | while read file with pyclean -p libseafile0:$DPKG_MAINTSCRIPT_ARCH else dpkg -L libseafile0:$DPKG_MAINTSCRIPT_ARCH | grep '\.py$' | while read file Note that this bugs currently affects Debian Testing. See also bug #770625 which shows how this same bug was fixed in gir1.2-ibus-1.0. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libseafile0:amd64 depends on: ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 ii libjansson4 2.11-1 ii libsearpc1 3.0.8-4 ii python 2.7.15~rc1-1 libseafile0:amd64 recommends no packages. libseafile0:amd64 suggests no packages. -- no debconf information