Hi, Thank you for tracing problem. https://bugs.debian.org/889053
On Mon, Mar 19, 2018 at 10:35:51AM +0300, Philip Blagoveschensky wrote: > Here's how I resolved the broken removal script. However I am not 100% sure > that this cleans up all files. > > --- /var/lib/dpkg/info/gir1.2-ibus-1.0:i386.prerm.BACKUP > +++ /var/lib/dpkg/info/gir1.2-ibus-1.0:i386.prerm > @@ -3,9 +3,9 @@ > > # Automatically added by dh_python3: > if which py3clean >/dev/null 2>&1; then > - py3clean -p gir1.2-ibus-1.0 > + py3clean -p gir1.2-ibus-1.0:i386 > else > - dpkg -L gir1.2-ibus-1.0 | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, > or next; unlink $_ or die $! foreach glob($_)' > + dpkg -L gir1.2-ibus-1.0:i386 | perl -ne > 's,/([^/]*)\.py$,/__pycache__/\1.*, or next; unlink $_ or die $! foreach > glob($_)' > find /usr/lib/python3/dist-packages/ -type d -name __pycache__ -empty > -print0 | xargs --null --no-run-if-empty rmdir > fi So this is multiarch problem. py3clean from python3-minimal should be aware of arch. OK. If this is true, what is the right way for the package which works under any combination of multiarch. Should I change postinst to something like... ----- ARCH=`dpkg-architecture -q DEB_TARGET_ARCH` py3clean -p gir1.2-ibus-1.0:$ARCH ----- Wait, I shouldn't make arbitrary changes here. This is automatically added by dh_python3. So dh-python package should fix it. The root cause looks like there. Piotr Ożarowski, what do you think about this bug report. Regards, Osamu
