| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This commit was sponsored by Anthony DeRobertis on Patreon.
|
|
If the running kernel is new enough, there is no need to look at the
kernels installed on the system.
|
|
* Generalized the PartSpec DSL, so it can be used for both
disk image partitioning, and disk device partitioning, with
different partition sizing methods as appropriate for the different
uses. (minor API change)
* Propellor.Property.Parted: Added calcPartTable function which uses
PartSpec DiskPart, and a useDiskSpace combinator.
This commit was sponsored by Thomas Hochstein on Patreon.
|
|
|
|
|
|
* Propellor.Property.LightDM.autoLogin: Made revertable.
(minor API change)
* Propellor.Property.Conffile: Added lacksIniSetting.
This commit was sponsored by Jack Hill on Patreon.
|
|
(minor API change)
This commit was sponsored by Henrik Riomar on Patreon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
New module which allows different versions of a property or host to be
written down in a propellor config file. Has many applications,
including staged upgrades and rollbacks.
Note that it currently only supports RevertableProperty that has the same
metatypes for its setup and cleanup sides. And, each RevertableProperty in
a version definition needs to have the same metatypes as the others too.
I tried a couple of times to add support for differing metatypes, but
it got beyond my avilities to do.
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
|
|
|
This works around an infelicity in stack; it complains when there are
both a toplevel config.hs and a src/config.hs, despite that being fine
with cabal.
|
|
|
|
|
|
The system might have stack installed, so stack --version would succeed,
but need stack setup to be run to get a working ghc.
This will fail if stack is not installed, or if stack setup needs to be
run. It does not fail when haskell libraries are not installed, but
stack build will install those anyway, so that's ok.
|
|
|
|
|
|
My first try with a pipe was the right approach, and was almost right,
except I forgot to close the write end of the pipe, and so it was inherited
by the forked process, leading to deadlock.
|
|
With some small changes, and debugging.
|
|
This reverts commit 632137836b39462883483a621f9dd696ce1d73cc.
Still failing :( Seems that disabling buffering is not the solution.
|
|
The "fatal: Couldn't find remote ref HEAD" persists, and is intermittent
so hard to be sure but it seemed that disabling buffering earlier
avoided it. Now done first thing on start.
I was not able to find anything that reads from stdin other than
getMarked, but perhaps there is something..
|
|
* Hosts can be configured to build propellor using stack, by adding
a property:
& bootstrapWith (Robustly Stack)
* Hosts can be configured to build propellor using cabal, but using
only packages installed from the operating system. This
will work on eg Debian:
& bootstrapWith OSOnly
propellor build its config using stack. (This does not affect
how propellor is bootstrapped on a host by "propellor --spin host".)
This has not yet been tested at all! But should probably work fine.
This is based on earlier work by Arnaud Bailly, who made
Propellor.Bootstrap use stack without parameterization.
In Arnaud's patch, stack was installed using wget, but that
only worked on linux-x86_64 and was insecure. I instead chose
to use the distribution packages of stack, like is done for cabal.
Debian stack has haskell-stack now, and it's getting into many
distributions.
This commit was sponsored by Francois Marier on Patreon.
|
|
|
|
|
|
|
|
|
|
This commit was sponsored by Trenton Cronholm on Patreon.
|
|
|
|
Properties that used to need it as a parameter now look at Info about the
bootloader that is installed in the chroot that the disk image is created
from. (API change)
This is a simplication, and avoids the user needing to repeat themselves
in the propellor config, thus avoiding mistakes.
When no boot loader is installed, or multiple different ones are,
disk image creation will fail, which seems reasonable.
This commit was sponsored by Jake Vosloo on Patreon.
|
|
* DiskImage.grubBooted no longer takes a BIOS parameter,
and no longer implicitly adds Grub.installed to the properties of
the disk image. If you used DiskImage.grubBooted, you'll need to update
your propellor configuration, removing the BIOS parameter from
grubBooted and adding a Grub.installed property to the disk image, eg:
& Grub.installed PC
(API change)
* Grub.installed: Avoid running update-grub when used in a chroot, since
it will get confused.
* DiskImage.Finalization: Simplified this type since it does not need to
be used to install packages anymore. (API change)
The advantage of doing this comes when using hostChroot with
imageBuilt, since the Host then has its Grub.installed property
explicitly listed so propellor knows about it when otherwise deploying that
host. Also, it simplifies the quite complex imageBuilt parameters.
This commit was sponsored by Ewen McNeill.
|
|
|
|
This commit was sponsored by Ethan Aubin.
|
|
destination file did not yet exist.
This commit was sponsored by andrea rota.
|
|
|
|
|
|
f' normally means a later version of f
|
|
|
|
|
|
* Propellor.Property.XFCE added with some useful properties for the
desktop environment.
* Added File.applyPath property.
This commit was sponsored by Riku Voipio.
|
|
(minor API change as the type changed)
|
|
When provisioning a container, output was buffered until the whole process
was done; now output will be displayed immediately.
I know this didn't used to be a problem. I belive it was introduced by
accident when propellor started using concurrent-output. I know I've seen
it for a while and never was bothered enough to get to the bottom of it;
apparently "a while" was longer than I thought.
Also refactored code to do with chain provisioning to all be in
Propellor.Engine and avoided some duplication.
This commit was sponsored by Anthony DeRobertis on Patreon.
|
|
This reverts commit c59ce983999ddbfe6cb8b27e4f376b5c37d7f853.
That was wrong because only the *last* line of chain output is a Result.
It could be that a previous line is able to be read as a Result, and
the commit would make processing bail out at that point.
|
|
|
|
Avoid needing to wait for a subsequent line before displaying the
previous line.
|
