Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix logic around grml_sources handling no longer being bind-mounted
In commit 87524f9 we adjusted the grml_sources handling, as bind mounts are not allowed in (unprivileged) docker. Now when running grml-live with SOURCES class enabled multiple times in a row (e.g. via grml-live's `-b` or `-u` options), one ends up with the $OUTPUT/grml_sources *and* $OUTPUT/grml_chroot/grml-live/grml_sources directories. grml-live then complains: mv: cannot overwrite '$OUTPUT/grml_sources': Directory not empty rmdir: failed to remove '$OUTPUT/grml_chroot/grml-live': Directory not empty As of commit 8b0a6fa we generate a source package tarball when using the SOURCES class, so one might want to remove the "${OUTPUT}/grml_sources" directory anyway (similar to what we're doing in commit 6486c84 in our CI runs). But let's also fix the underlying logic and move grml_sources around as expected.
- Loading branch information