bootstrap sections

multistrap configuration files organise repositories into
sections. To include this repository in the calculation of packages
to download for unpacking into the base system, specify the section
name in the bootstrap option:

This method works best when the explicitsuite option is set
to "true" and when one or both sections specify individual
packages to install from that suite. apt will bring in the
base system (Priority: required packages) using the most
recent versions available when the suites are combined.

There can be problems mixing rapidly changing suites with stable
suites, especially if you want reproducible results. Unstable is
constantly changing, frequently includes packages which are not
installable and the dependency chain of unchanged packages can still
be affected by transitions in other packages. Multistrap depends on
apt for dependency resolution and if apt is not able to resolve the
entire dependency chain, it will fail the entire chain, leaving
multistrap with no option but to fail the bootstrap process. One method
to avoid such problems is to insulate yourself from the changes in unstable,
either by choosing to use testing instead of unstable or by taking a
partial copy of the bits of unstable which you need as a partial
mirror. reprepro is
recommended, see also
the Multistrap wiki pages.

For an example, check the cross-chroot support in multistrap
which combines a base system from testing but installs
cross-building toolchains from stable.

In any one configuration, section names must be unique even if
configuration files are cascaded.