| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
* 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.
|
|
|
|
|
|
This way, when a disk image is built using this property, and booted up,
running propellor won't try to ensure this property again.
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
|
|
|
from the bootstrapped config the first time.
When the config changes, the bootstrapped propellor needs to get rebuilt.
This commit was sponsored by Fernando Jimenez on Patreon.
|
|
|
|
|
|
Since some programs (such as VBoxManage convertdd) refuse to operate on
disk images not aligned to a sector size.
This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
|
|
|
|
|
|
|
|
|
|
|
|
I have a cron job updating a file in there..
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
It turns out that IncludeOptional will error out if it is passed non-wildcard
directories that do not exist.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
So if the insecure password is later changed, the new password won't be
exposed.
|
|
|
|
|
|
|
|
|
|
|
|
Not sure what the problem was, but it hung. Also though, I noticed that
stdin was still open when git fetch was run, so if git fetch itself
decided to read from stdin, it would mess up the protocol forwarding.
While git fetch should never read from stdin, that was reason enough to
fall back to plan B.
|
|
|
|
|
|
ref HEAD"
Tricky stdin buffering problem.
An easier fix would have been:
hSetBuffering stdin NoBuffering
But that approach is less robust; even with NoBuffering, anything that
uses hLookAhead causes 1 byte of buffering. And, any reads from stdin
before hSetBuffering would still cause the problem. Instead, I used a
bigger hammer that will always work. It involves a bit more CPU work,
but this is data that is already being fed through ssh; copying it one
more time won't cause a measurable performance impact.
This commit was sponsored by Jack Hill on Patreon.
|
|
|
|
|
|
|
