propellor config for hosts.
git clone git://
Log | Files | Refs | LICENSE

comment_3_4466bc58fd3e69938c184c817ddbb3e6._comment (1498B)

      1 [[!comment format=mdwn
      2  username="spwhitton"
      3  subject="comment 3"
      4  date="2016-06-14T03:16:18Z"
      5  content="""
      6 Thanks for taking a look at my branch, and especially for fixing my inadequately-tested `readVersionMaybe`.
      8 `Sbuild.built` does not *require* a particular version of the kernel.  It is just that the file that it generates in `/etc/schroot/chroot.d` can vary depending on the kernel version running at the time that `Sbuild.built` is first ensured.  In particular, if the running kernel does not support overlayfs (as jessie's kernel doesn't), the line `union-type=overlay` will be omitted from the file in `/etc/schroot/chroot.d`.  This renders `Schroot.overlaysInTmpfs` useless.
     10 I think it should be up to the user to apply a property like
     12     & Sbuild.built foo `requires` Reboot.toKernelNewerThan bar
     14 to individual hosts, because it depends on whether they actually care about using an overlay chroot.  Perhaps on an old machine they don't intend to use overlays.  In my config, I do something like this:
     16     & osDebian Testing \"i386\"
     17     & Apt.stdSourcesList `onChange` (Apt.upgraded `before` Apt.cacheCleaned `before` Reboot.toKernelNewerThan \"4\")
     18     & Sbuilt.builtFor ...
     20 The idea is that if I reinstall my machine from a jessie installation CD, propellor will upgrade to testing and boot to the new kernel before it builds the chroot, so I get the `union-type=overlay` line in my config.
     22 I could prepare a patch to add this information to the haddock of Sbuild.hs?
     23 """]]