Hi josch.
I sorta expected that there was extra complexity here that made
debugging difficult. It's unfortunate.
> mmdebstrap ... --variant=apt --chrooted-customize-hook=bash unstable /dev/null
Would that work, though?
--chrooted-customize-hook isn't in the manpage
--customize-hook runs after everything was installed (so past where
the failure was happening here)
--essential-hook was running at the right time, but the "apt-get"
executable wasn't available
In any case, I figured out my specific problem by creating a similar
scenario on a native arm64 box. I was naming the pinning file xxxx.conf
instead of xxxx.pref which apparently matters. On the arm64 box this
produced a clear error message ("apt" told me to rename the file). But
with mmdebstrap there was no specific error at all, as you saw. Any idea
why?
Thanks for all the help.
