[Pkg-raspi-maintainers] Building an image of Debian for Raspberry Pi 3

[Ludovic Brenta]

I have made some progress on the issue of the python3.6-minimal postinst
script.  My attempt with modifying the postinst script after the first
attempt to configure failed because the problem is in fact deeper than
that.  So I executed the first steps of debootstrap manually, instead of
using raspi3.yaml and vmdb2.  After tinkering with
python3.6-minimal.postinst, I ended up discovering that
/usr/bin/python3.6 itself is the culprit:

# /usr/bin/python3.6
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
# ldd /usr/bin/python3.6
        libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000004000834000)
        libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000004000862000)
        libutil.so.1 => /lib/aarch64-linux-gnu/libutil.so.1 (0x0000004000876000)
        libexpat.so.1 => /lib/aarch64-linux-gnu/libexpat.so.1 (0x0000004000889000)
        libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x00000040008c8000)
        libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x00000040008f0000)
        libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x00000040009aa000)
        /lib/ld-linux-aarch64.so.1 (0x0000004000000000)

At this point I am unsure what to do; the problem might still be in qemu
because I can't believe that /usr/bin/python3.6 is completely broken (at
least on arm64) without anyone noticing.  Should I file a bug report?

--
Ludovic Brenta.