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

[Michael Stapelberg]

Thanks for your mail. Answers inline:

On Thu, Apr 26, 2018 at 3:53 PM, Ludovic Brenta <ludovic at ludovic-brenta.org>
wrote:

> Hello,
>
> First of all thank you for the pioneering work you've done
> for Debian on the Raspberry Pi 3.  I am myself a Debian Developer
> and I just purchased a Pi and I wanted to install Debian on it.
> Not wanting to be just a "passenger" and downloading your image,
> I tried to make my own with a few changes:
>
> - 5% instead of 20% for the vfat partition (the firmware blob is
>   only 20 MiB installed, so a 75 MiB partition is more than enough)
> - ext2 instead of ext4 for the root partition (SD cards are slow
>   and do not need a journalling file system which would only slow
>   them down even more, I think).
>

Do you have any benchmarks/measurements supporting this claim? This is the
first time I hear about it.


>
> The other change is that python3.6-minimal has been upgraded from
> 3.6.4-3 in your latest image to 3.6.5~rc1-1 (testing) and 3.6.5-3
> (unstable).  And this package is giving me the following headache:
>
> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>
> while executing the post-installation script of python3.6-minimal.
> As a consequence, all subsequent invocations of apt install will
> also fail as they notice the package is unconfigured and re-execute
> the postinst script.
>
> I think this may be due to the lack of support for threading in
> qemu, combined with the use of pipes in the postinst script.
>

I would be surprised if qemu did not support threading. Have you searched
for bug reports about this symptom?


>
> Have you encountered this before?
>

No. It might be good to open an issue on
https://github.com/Debian/raspi3-image-spec/issues, so that interested
people can chime in with additional details/ideas. I’ve also cc'ed the
pkg-raspi-maintainers@ list in case anyone else knows anything about this.


>
> My plan is to:
> - apt install python3.6-minimal
> - let it fail
> - sed 's/set +e/exit 0/' the postinst script so it does nothing
> - continue with the other packages
> - after booting the raspberry pi, restore the postinst script
>   and dpkg-reconfigure python3.6-minimal outside of qemu
>
> Is that sensible?


I’d say any approach that works is sensible as a workaround :).

-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-raspi-maintainers/attachments/20180426/c96126de/attachment.html>