summaryrefslogtreecommitdiff
path: root/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment')
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment17
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment
deleted file mode 100644
index 2578ef8e..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 5"""
- date="2017-10-04T17:12:59Z"
- content="""
-Not sure why unpropelling blocks this. IIRC we discussed using a regular
-propellor chroot to set up the sbuild chroot. And I pointed out that when
-propellor runs inside a chroot, it does it without installing any
-dependencies into the chroot; everything propellor needs to run is
-bind mounted into /usr/local/propellor in the chroot.
-
-So, the most an "unpropell" property would need to do in a chroot is to
-unmount below /usr/local/propellor and remove that directory, which should
-then be empty. This might be desirable to be sure that the sbuild
-environment is 100% clean, in the unlikely chance that something
-builds differently when /usr/local/propellor exists.
-"""]]