summaryrefslogtreecommitdiff
path: root/doc/forum
diff options
context:
space:
mode:
authorSean Whitton2017-11-19 12:04:26 -0700
committerSean Whitton2017-11-19 12:04:26 -0700
commit05e5308ee7cef99b24b4f9d9755e5488f8d92a39 (patch)
tree256b8f20bddf0f0701a3247228f9c2dd77be6e64 /doc/forum
parent38d039310e4db6ffaf5c8ca51c339421e6865eff (diff)
parent12beba0367d14f9c52adf72dd36e9cf5a8e35761 (diff)
Merge branch 'master' of https://git.joeyh.name/git/propellor into sbuild-overhaul
Diffstat (limited to 'doc/forum')
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn29
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_1_59ac4661a896a514ce953a0069341869._comment24
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_2_579894632e567a08d83e306be5e355b2._comment84
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_3_6aeee8ba74b363d26a49d6773c5d5014._comment12
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_4_f6c386dddf408d522841fd3bde699d15._comment8
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_5_060b3ab57e525669c44192bbfdc730a4._comment17
-rw-r--r--doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_6_9d6536b85cd3fd3ca3b0128aff56d797._comment8
7 files changed, 0 insertions, 182 deletions
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn
deleted file mode 100644
index 8887f438..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn
+++ /dev/null
@@ -1,29 +0,0 @@
-Hello, I am preparing a property in order to setup a debomatic machine
-but when I try to upload a package I get this error from debomatic
-
- DEBUG: Command '['schroot', '-l']' returned non-zero exit status 1
- Traceback (most recent call last):
- File "/usr/share/debomatic/Debomatic/process.py", line 197, in _finish
- raise e
- File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
- result = self.fn(*self.args, **self.kwargs)
- File "/usr/share/debomatic/Debomatic/build.py", line 525, in run
- self._build()
- File "/usr/share/debomatic/Debomatic/build.py", line 133, in _build
- self._setup_chroot()
- File "/usr/share/debomatic/Debomatic/build.py", line 395, in _setup_chroot
- chroots = check_output(['schroot', '-l'], stderr=fd)
- File "/usr/lib/python3.5/subprocess.py", line 316, in check_output
- **kwargs).stdout
- File "/usr/lib/python3.5/subprocess.py", line 398, in run
- output=stdout, stderr=stderr)
- subprocess.CalledProcessError: Command '['schroot', '-l']' returned non-zero exit status 1
-
-so tried on my own
-
- :/etc/debomatic# schroot -l
- E: /etc/schroot/chroot.d/stretch-amd64-sbuild-propellor: [stretch-amd64-sbuild]: Required key ‘directory’ is missing
-
-to my opinion the schroot config file generated by Sbuild property does something wrong.
-
-Cheers
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_1_59ac4661a896a514ce953a0069341869._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_1_59ac4661a896a514ce953a0069341869._comment
deleted file mode 100644
index b4e411b7..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_1_59ac4661a896a514ce953a0069341869._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="picca"
- avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
- subject="comment 1"
- date="2017-08-23T13:00:13Z"
- content="""
-this is strange because the stretch-amd64-sbuild file is wrong.
-
-here the content
-
- [stretch-amd64-sbuild]
- command-prefix=/var/cache/ccache-sbuild/sbuild-setup,eatmydata
-
-to compare with my previous jessie-amd64-sbuild
-
- [jessie-amd64-sbuild]
- type=directory
- description=Debian jessie/amd64 autobuilder
- directory=/srv/chroot/jessie-amd64
- groups=root,sbuild
- root-groups=root,sbuild
- profile=sbuild
- command-prefix=/var/cache/ccache-sbuild/sbuild-setup,eatmydata
-"""]]
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_2_579894632e567a08d83e306be5e355b2._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_2_579894632e567a08d83e306be5e355b2._comment
deleted file mode 100644
index 53595ad2..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_2_579894632e567a08d83e306be5e355b2._comment
+++ /dev/null
@@ -1,84 +0,0 @@
-[[!comment format=mdwn
- username="picca"
- avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
- subject="comment 2"
- date="2017-08-23T13:26:31Z"
- content="""
-Hello, so I try to restart from scratch and ask for a stretch Sbuild
-
-everything went fine until the update
-
-
- I: schroot chroot configuration written to /etc/schroot/chroot.d/stretch-amd64-propellor-VYWULd.
- +------------------------------------------------------------------------
- |[stretch-amd64-propellor]
- |description=Debian stretch/amd64 autobuilder
- |groups=root,sbuild
- |root-groups=root,sbuild
- |profile=sbuild
- |type=directory
- |directory=/srv/chroot/stretch-amd64
- |union-type=overlay
- +------------------------------------------------------------------------
- I: Please rename and modify this file as required.
- W: Not creating symlink /srv/chroot/stretch-amd64 to /etc/sbuild/chroot/stretch-amd64-propellor: file already exists
- perl: warning: Setting locale failed.
- perl: warning: Please check that your locale settings:
- LANGUAGE = (unset),
- LC_ALL = (unset),
- LANG = \"en_GB.UTF-8\"
- are supported and installed on your system.
- perl: warning: Falling back to the standard locale (\"C\").
- I: Setting reference package list.
- I: Updating chroot.
-
-
-On my network, I need a proxy so I setup the host with
-
- ...
- & Apt.proxy myproxy
- & Sbuild.builtFor stretch Sbuild.UseCcache
-
-If I understand correctly the Apt.proxy should propagate the Apt.proxy into the Sbuild
-but when I look inside the chroot, I can not find the
-
- /etc/apt/apt.conf.d/20proxy
-
-file which is on the host
-
-And Indeed after a certain amount of time, the network gives a timeout
-
- Err:1 http://deb.debian.org/debian stretch InRelease
- Cannot initiate the connection to deb.debian.org:80 (2001:41c8:1000:21::21:4). - connect (101: Network is unreachable) [IP: 2001:41c8:1000:21::21:4 80]
- Reading package lists...
- W: Failed to fetch http://deb.debian.org/debian/dists/stretch/InRelease Cannot initiate the connection to deb.debian.org:80 (2001:41c8:1000:21::21:4). - connect (101: Network is unreachable) [IP: 2001:41c8:1000:21::21:4 80]
- W: Some index files failed to download. They have been ignored, or old ones used instead.
- Reading package lists...
- Building dependency tree...
- Calculating upgrade...
- 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
- I: Successfully set up stretch chroot.
- I: Run \"sbuild-adduser\" to add new sbuild users.
- sixs7.exp.synchrotron-soleil.fr sbuild schroot for System (Debian Linux (Stable \"stretch\")) X86_64 ... done
-
-the good news is that now the schroot file contain the right informations
-
- [stretch-amd64-sbuild]
- description=Debian stretch/amd64 autobuilder
- groups=root,sbuild
- root-groups=root,sbuild
- profile=sbuild
- type=directory
- directory=/srv/chroot/stretch-amd64
- union-type=overlay
- command-prefix=/var/cache/ccache-sbuild/sbuild-setup,eatmydata
-
-
-So to summarize, I think that the Apt.proxy propagation does not work.
-
-This propagation should be optional because sometime we prepare images which are not meant to be used behind a proxy (where they were prepare)
-
-thanks for your attention :)
-
-
-"""]]
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_3_6aeee8ba74b363d26a49d6773c5d5014._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_3_6aeee8ba74b363d26a49d6773c5d5014._comment
deleted file mode 100644
index 12d59028..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_3_6aeee8ba74b363d26a49d6773c5d5014._comment
+++ /dev/null
@@ -1,12 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
- subject="comment 3"
- date="2017-09-02T02:47:01Z"
- content="""
-Thank you for the detailed report.
-
-I think the problem is the proxy propagation happens after the sbuild-createchroot command has run, but if the sbuild-createchroot command needs the proxy, it will fail in the way you describe.
-
-After speaking to Joey at DebConf I think I can rework the sbuild module to bypass sbuild-createchroot and run debootstrap itself, without thereby polluting the chroot that is created. That should make it much easier to fix this bug, so I'll do that first.
-"""]]
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_4_f6c386dddf408d522841fd3bde699d15._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_4_f6c386dddf408d522841fd3bde699d15._comment
deleted file mode 100644
index 17c99e16..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_4_f6c386dddf408d522841fd3bde699d15._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
- subject="Blocked"
- date="2017-09-20T17:29:50Z"
- content="""
-Note that this is currently blocked by: https://propellor.branchable.com/todo/unpropelling_a_host/
-"""]]
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.
-"""]]
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_6_9d6536b85cd3fd3ca3b0128aff56d797._comment b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_6_9d6536b85cd3fd3ca3b0128aff56d797._comment
deleted file mode 100644
index 32427cef..00000000
--- a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_6_9d6536b85cd3fd3ca3b0128aff56d797._comment
+++ /dev/null
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spwhitton"
- avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
- subject="comment 6"
- date="2017-10-20T21:47:43Z"
- content="""
-I'd forgotten that detail of our discussion. Thanks. Moving this onto my TODO list; hope to work on it soon.
-"""]]