current next bash in buildchroot problem

[Henning Schild <henning.schild@siemens.com>]

Hi,

i rebased a few patches on top of current next and now the buildchroot
rootfs will not build anymore.

/builder/build/tmp/work/debian-stretch-amd64/buildchroot/temp/log.do_build:

> dpkg: dependency problems prevent configuration of bash:
> bash depends on base-files (>= 2.1.12); however:
>  Package base-files is not installed.
>
>dpkg: error processing package bash (--configure):
> dependency problems - leaving unconfigured
...
> Setting up docbook (4.5-6) ...
> Setting up docbook-to-man (1:2.0.0-35) ...
> Processing triggers for libc-bin (2.24-11+deb9u1) ...
> Errors were encountered while processing:
>  bash
> WARNING: exit code 1 from a shell command.

Looking further base-files has been installed but does not seem to like
the environment it is being installed in. That is probably connected
with the changes in how and what we mount.

> I: Extracting base-files_9.9+deb9u3_amd64.deb...
> tar: ./sys: Cannot utime: Read-only file system
> tar: ./sys: Cannot change ownership to uid 0, gid 0: Read-only file
> system tar: ./sys: Cannot change mode to rwxr-xr-x: Read-only file
> system tar: Exiting with failure status due to previous errors
> dpkg-deb: error: subprocess tar returned error exit status 2
> dpkg -X failed with error code 512
> Skipping...

But i wonder why nobody else has reported/seen that before me ...

Henning