@juliank Well, I have to agree in this particular case. If the package archive was available u-u could try to fix it by even calling dpkg to reinstall it, but the archive was not available.
At least u-u logs this error and includes it in the email now and only after that it raises it again for apport to get it reported.
The error has also been reported with piper broken, maybe there was an issue running the maintainer scripts which calls py3compile:
#!/bin/sh
set -e
# Automatically added by dh_python3:
if which py3compile >/dev/null 2>&1; then
py3compile -p piper
fi
if which pypy3compile >/dev/null 2>&1; then pypy3compile -p piper || true
fi
@juliank Well, I have to agree in this particular case. If the package archive was available u-u could try to fix it by even calling dpkg to reinstall it, but the archive was not available.
At least u-u logs this error and includes it in the email now and only after that it raises it again for apport to get it reported.
The error has also been reported with piper broken, maybe there was an issue running the maintainer scripts which calls py3compile:
#!/bin/sh
set -e
# Automatically added by dh_python3:
pypy3compile -p piper || true
if which py3compile >/dev/null 2>&1; then
py3compile -p piper
fi
if which pypy3compile >/dev/null 2>&1; then
fi
# End automatically added section