Open kgilmer opened 6 months ago
Hello Ken,
debootstick
does not handle arm64 environments mainly because of the lack of a standard apt-installable bootloader.
We could imagine supporting 64-bit OS on raspberry pi boards. For now it's only 32-bit because at the time we developed it, "raspbian" was 32-bit only.
If you think --help-os-support
could be more precise, a pull request is welcome. We could explicitely specify x86 PCs
and 32-bit
in the case of the Raspberry Pi.
Hi Etienne! Yes, to me the message when running debootstick
left me wondering if there was something I did wrong. Perhaps it's just me, and if so no worries. Here is my suggestion for maybe a more direct way of conveying the intent. If you agree this is an improvement, I'd be happy to write a PR, but don't feel that you have to :)
E: debootstick does not know how to handle your chroot environment. ->
E: Run 'debootstick --help-os-support' for more info.
->
E: This chroot environment is not supported by debootstick. Aborting."
E: Run 'debootstick --help-os-support' for a list of supported chroot environments.
I see, yes of course this could be better.
Ok so I let you write the PR, it is important that contributions are credited to the correct author.
The message you quoted is in scripts/create-image/os-detect
.
The text of --help-os-support
option itself is in scripts/create-image/cmdline
, if you want to improve it too (wrt. the fact we support only the 32bit OS for raspberry pi boards).
Please also add something in debian/changelog. This will be the first entry for next version 2.9.
In follwing the instructions here: https://github.com/drakkar-lig/debootstick/wiki/Usual-Workflow I got to the part of running
debootstick
but the error does not provide info as to how to resolve the problem. Would hope that the--help-os-support
option would provide more concrete info on how to move forward, or explicitly state that the operating environment is incompatible and cannot work: