mdadm no arrays found in config file...

[towo]

Try to change libavcodec61 to libavcodec62 in base-media.

[ro_sid]

@towo: Thanks for that information. It seems worthy. But guess what, now it's the 'policycoreutils-dbus', which we discussed in another thread. (The dependency missing is 'policycoreutils-python-utils' (in the required version). One Siduction-Member (@Teriarch iirc) provided a (mock) package that is a recompilation of the 'old' package with the required version number. That works well for me. We shortly discussed, if that package could go in a repo (e.g. 'fixed'), but there is the worry, that this package will not be overwritten by a Debian-provided one - the official package.)

For testing purposes I have now explicitly ('-' at the end) deselected 'policycoreutils-dbus' in 'base-security'. Now the ISO is generated, but I cannot tell, what consequences come of the modification. [And I cannot test that today.]

[towo]

Remove policycoreutils-dbus it's not really needed.

[Teriarch]

Try this one first:
<https://wormhole.app/Q5L3p1#8BpMI2pEh8fFcbHSYLhZqw>
It contains an additional line:
Provides: policycoreutils-python-utils (= 3.10.1)
Don't know if that solves the dependency problem.

PS.:
No it doesn't. Problem is the wrong policycoreutils-python-utils (version 3.10-1) package being fetched from the
server during the build. Is there a possibility to include one's own packages during the build? Once the ISO is built,
the wind of change is gone.