summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/DiskImage_creation_does_not_work_on_my_system.mdwn36
-rw-r--r--doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_1_2daa4574bce2179bfd7e9e505de3f7b0._comment8
-rw-r--r--doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_2_98fb34d4e76bab6ef7a981c87533f395._comment14
-rw-r--r--doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_3_047bca6e0676f0d93338d4eff20825bf._comment18
-rw-r--r--doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_4_fc50b46606eacf59e5db227760ce38ab._comment24
-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/creating_Bind9_configuration.mdwn9
-rw-r--r--doc/forum/creating_Bind9_configuration/comment_1_0798f44e1f5a91fbc91c0b472ad92bfa._comment29
-rw-r--r--doc/forum/propellor_4.7.6_does_not_compile_on_jessie.mdwn32
11 files changed, 307 insertions, 0 deletions
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system.mdwn b/doc/forum/DiskImage_creation_does_not_work_on_my_system.mdwn
new file mode 100644
index 00000000..f7f56889
--- /dev/null
+++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system.mdwn
@@ -0,0 +1,36 @@
+Hello, I am trying to create a virtualbox image from my stretch system.
+
+But I hve two problems :)
+
+I took your example from the DiskImage property, but in the end, I got this
+
+/srv/diskimages/soleil.img.chroot no services started ... ok
+/srv/diskimages/soleil.img.chroot has Operating System (Debian Linux Unstable) X86_32 ... ok
+/srv/diskimages/soleil.img.chroot apt installed linux-image-i686 ... ok
+/srv/diskimages/soleil.img.chroot grub package installed ... ok
+/srv/diskimages/soleil.img.chroot root has insecure password ... done
+/srv/diskimages/soleil.img.chroot account for soleil ... ok
+/srv/diskimages/soleil.img.chroot soleil has insecure password ... done
+/srv/diskimages/soleil.img.chroot user soleil in group audio ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group cdrom ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group dip ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group floppy ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group video ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group plugdev ... ok
+/srv/diskimages/soleil.img.chroot user soleil in group netdev ... ok
+/srv/diskimages/soleil.img.chroot user soleil is in standard desktop groups ... ok
+/srv/diskimages/soleil.img.chroot cache cleaned ... ok
+ 0 0% 0.00kB/s 0:00:00 (xfr#0, to-chk=0/3)
+ 930 0% 1.77kB/s 0:00:00 (xfr#3, to-chk=0/11069)
+chroot: impossible d'exécuter la commande « update-initramfs »: No such file or directory
+loop deleted : /dev/loop0
+
+I will try to add the pacakge which contain update-initramfs and report back
+
+
+the second problem is thaht virtualbox is no more part of stretch.
+So it is not possible to create a virtualbox image.
+
+Cheers
+
+Frederic
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_1_2daa4574bce2179bfd7e9e505de3f7b0._comment b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_1_2daa4574bce2179bfd7e9e505de3f7b0._comment
new file mode 100644
index 00000000..90283031
--- /dev/null
+++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_1_2daa4574bce2179bfd7e9e505de3f7b0._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="picca"
+ avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
+ subject="comment 1"
+ date="2017-08-22T07:02:51Z"
+ content="""
+Haaaaaaa the format of the post is ugly. Is it possible to change this ?
+"""]]
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_2_98fb34d4e76bab6ef7a981c87533f395._comment b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_2_98fb34d4e76bab6ef7a981c87533f395._comment
new file mode 100644
index 00000000..e8898a96
--- /dev/null
+++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_2_98fb34d4e76bab6ef7a981c87533f395._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="picca"
+ avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
+ subject="comment 2"
+ date="2017-08-22T07:12:13Z"
+ content="""
+OK, I tryed to install the wrong kernel so the initramfs was not installed.
+
+So now the only real problem is the virtualbox one ;)
+
+Cheers
+
+Frederic
+"""]]
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_3_047bca6e0676f0d93338d4eff20825bf._comment b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_3_047bca6e0676f0d93338d4eff20825bf._comment
new file mode 100644
index 00000000..aeeaf724
--- /dev/null
+++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_3_047bca6e0676f0d93338d4eff20825bf._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="picca"
+ avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
+ subject="comment 3"
+ date="2017-08-22T07:36:06Z"
+ content="""
+It seems that we do not need virtualbox in order to generate a vmdk image
+
+I installed *qemu-utils* and then
+
+ # qemu-img convert -O vmdk soleil.img soleil.vmdk
+ # file soleil.vmdk
+ soleil.vmdk: VMware4 disk image
+
+what about using this solution instead of the virtualbox one ?
+
+Cheers
+"""]]
diff --git a/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_4_fc50b46606eacf59e5db227760ce38ab._comment b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_4_fc50b46606eacf59e5db227760ce38ab._comment
new file mode 100644
index 00000000..27b70a57
--- /dev/null
+++ b/doc/forum/DiskImage_creation_does_not_work_on_my_system/comment_4_fc50b46606eacf59e5db227760ce38ab._comment
@@ -0,0 +1,24 @@
+[[!comment format=mdwn
+ username="picca"
+ avatar="http://cdn.libravatar.org/avatar/7e61c80d28018b10d31f6db7dddb864c"
+ subject="comment 4"
+ date="2017-08-22T08:42:35Z"
+ content="""
+ vmdkBuiltFor :: FilePath -> RevertableProperty DebianLike UnixLike
+ vmdkBuiltFor diskimage = (setup <!> cleanup)
+ `describe` (vmdkfile ++ \" built\")
+ where
+ vmdkfile = diskimage ++ \".vmdk\"
+ setup = cmdProperty \"qemu-img\"
+ [ \"convert\"
+ , \"-O\", \"vmdk\"
+ , diskimage, vmdkfile
+ ]
+ `changesFile` vmdkfile
+ `onChange` File.mode vmdkfile (combineModes (ownerWriteMode : readModes))
+ `requires` Apt.installed [\"qemu-utils\"]
+ `requires` File.notPresent vmdkfile
+ cleanup = File.notPresent vmdkfile
+
+seems to work :))
+"""]]
diff --git a/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn
new file mode 100644
index 00000000..8887f438
--- /dev/null
+++ b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot.mdwn
@@ -0,0 +1,29 @@
+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
new file mode 100644
index 00000000..b4e411b7
--- /dev/null
+++ b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_1_59ac4661a896a514ce953a0069341869._comment
@@ -0,0 +1,24 @@
+[[!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
new file mode 100644
index 00000000..53595ad2
--- /dev/null
+++ b/doc/forum/Sbuild_chroot_are_not_compatible_with_schroot/comment_2_579894632e567a08d83e306be5e355b2._comment
@@ -0,0 +1,84 @@
+[[!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/creating_Bind9_configuration.mdwn b/doc/forum/creating_Bind9_configuration.mdwn
new file mode 100644
index 00000000..5e281394
--- /dev/null
+++ b/doc/forum/creating_Bind9_configuration.mdwn
@@ -0,0 +1,9 @@
+I try to use propellor to deploy a secondary DNS server.
+
+In your configuration, I see nothing to change the `listen-on { 127.0.0.1; };` option, did I miss something?
+
+Also, in `Dns.secondaryFor`, I do not know how to set `confLines` to something else, should I use this function and peel the result until I can change this or shoud I add a `Dns.secondaryFor'` version with an extra argument?
+
+By the way, is it really advisable to use a "minimal config" instead of a full clone?
+
+Thanks!
diff --git a/doc/forum/creating_Bind9_configuration/comment_1_0798f44e1f5a91fbc91c0b472ad92bfa._comment b/doc/forum/creating_Bind9_configuration/comment_1_0798f44e1f5a91fbc91c0b472ad92bfa._comment
new file mode 100644
index 00000000..d1387a22
--- /dev/null
+++ b/doc/forum/creating_Bind9_configuration/comment_1_0798f44e1f5a91fbc91c0b472ad92bfa._comment
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="Nicolas.Schodet"
+ avatar="http://cdn.libravatar.org/avatar/0d7ec808ec329d04ee9a93c0da3c0089"
+ subject="comment 1"
+ date="2017-08-03T20:52:22Z"
+ content="""
+For the moment I use:
+
+```
+namedOptions :: Property DebianLike
+namedOptions =
+ File.hasContent \"/etc/bind/named.conf.options\" namedOptionsStanza
+ `onChange` Service.reloaded \"bind9\"
+ where
+ namedOptionsStanza =
+ [ \"// automatically generated by propellor\"
+ , \"options {\"
+ , \"\tdirectory \\"/var/cache/bind\\";\"
+ , \"\tdnssec-validation auto;\"
+ , \"\tlisten-on-v6 { any; };\"
+ , \"\tlisten-on { any; };\"
+ , \"\tallow-query { any; };\"
+ , \"\tallow-recursion { localhost; };\"
+ , \"\tallow-transfer { none; };\"
+ , \"\tallow-notify { none; };\"
+ , \"};\"
+ ]
+```
+"""]]
diff --git a/doc/forum/propellor_4.7.6_does_not_compile_on_jessie.mdwn b/doc/forum/propellor_4.7.6_does_not_compile_on_jessie.mdwn
new file mode 100644
index 00000000..b3e6f7c7
--- /dev/null
+++ b/doc/forum/propellor_4.7.6_does_not_compile_on_jessie.mdwn
@@ -0,0 +1,32 @@
+Hello here the error message I got while trying to compile on jessie
+
+ [ 91 of 113] Compiling Propellor.Bootstrap ( src/Propellor/Bootstrap.hs, dist/build/propellor-config/propellor-config-tmp/Propellor/Bootstrap.o ) src/Propellor/Bootstrap.hs:239:22:
+ No instance for (Typeable Bootstrapper)
+ arising from a use of `fromInfo'
+ Possible fix:
+ add an instance declaration for (Typeable Bootstrapper)
+ In the expression: fromInfo (maybe mempty hostInfo mh)
+ In a stmt of a 'do' block:
+ case fromInfo (maybe mempty hostInfo mh) of {
+ NoInfoVal
+ -> do { bs <- getGitConfigValue "propellor.buildsystem";
+ case bs of {
+ Just "stack" -> ...
+ _ -> ... } }
+ InfoVal bs
+ -> case getBuilder bs of {
+ Cabal -> cabalBuild msys
+ Stack -> stackBuild msys } }
+ In the second argument of `($)', namely
+ `do { case fromInfo (maybe mempty hostInfo mh) of {
+ NoInfoVal -> do { ... }
+ InfoVal bs
+ -> case getBuilder bs of {
+ Cabal -> ...
+ Stack -> ... } } }'
+ Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal
+ update' to download it.
+ Resolving dependencies...
+ Configuring propellor-4.7.6...
+
+Cheers