| Age | Commit message (Collapse) | Author |
|---|
|
modified the locale.gen file and sometimes caused the property to need to make changes every time.
|
|
|
|
|
|
(cherry picked from commit 313a94cd87cd0f977310a6eada559dd383f6e9f0)
|
|
(cherry picked from commit 1a485202eeab60d9d677576278480a4109db72fb)
|
|
(cherry picked from commit 4705d6be44d1ce6ff5eb0c7b8bc3a904b6e8d220)
|
|
(cherry picked from commit 864bff7743bd3a77f1bfdb37bdeeea49e31e1f52)
|
|
(cherry picked from commit f16e0e4f632032c70adcb9ba9f108e87a6ae4321)
|
|
(cherry picked from commit 26fd68a9cda543e74492dc71680d10eaa881f351)
|
|
(cherry picked from commit 2214aca8f3ca92b9739b2884cb59274edad9170e)
|
|
(cherry picked from commit c97f1308739aa7877aac2f3c949c4aadf2266775)
|
|
There may not be changes from the origin repo, so fetchFirst wouldn't
build, but changes are pushed by spin, so it always needs to build.
|
|
buildFirst re-runs propellor with --continue, which is supposed to
make defaultMain bypass subsequent calls to buildFirst. But, use of a Bool
to do that caused the code to be unclear, and some of the cases lost track
of that.
--continue SimpleRun would buildFirst, and if the binary changed, would
--continue SimpleRun. This could loop repatedly, on systems such as FreeBSD
where building re-links the binary even when there are no changes. As
discussed in github pull #11
Fixed by introducing a CanRebuild data type, which buildFirst and updateFirst
require in order to do any work makes it more clear what's going on.
It's not a type-level proof that propellor won't rebuild repeatedly,
but gets closer to one.
(Only remaining way such a bug could slip in is if the CanRebuild
value was reused in a call to buildFirst and also inside the IO action
passed to it.)
There were some other weirdnesses around repeated builds. In particular,
Run as non-root did an updateFirst, followed by a buildFirst. I think this
redundant build was an accident, and have removed it.
|
|
(cherry picked from commit 3682285c696ff24169f2bdaad6fbbea6a561b560)
|
|
(cherry picked from commit 0e076fbfaa4d57f8d665436243d20bb9e28cbebc)
|
|
|
|
|
|
* Apt.upgrade: Run dpkg --configure -a first, to recover from
interrupted upgrades.
* Apt: Add safeupgrade.
|
|
|
|
authorized_keys file does not yet exist.
|
|
Seems that Canonical have trademarked numerous words ending in "buntu",
and would like to trademark anything ending in that to the extent their
lawyers can make that happen.
|
|
(cherry picked from commit 226bf3e8230037ad2de38760c962033ab6c64d9f)
|
|
(cherry picked from commit 57f7d81f1124fa5c56a593b9d5de6448155a938e)
|
|
(cherry picked from commit 202f9c282ee34897461dc56a79e607244c94cd99)
|
|
(cherry picked from commit ecff879cfeacfbff00649f4a3b9dd19eaefe134f)
|
|
(cherry picked from commit d4653a2c4683ff3eeb4decbb3c61bb9e9cef2c64)
|
|
(cherry picked from commit 34ee25d51b502af8da81c7b0701ac02cf1f43c1e)
|
|
(cherry picked from commit 717e693b2ad0bf39865ef28952f37670e70d8582)
|
|
Removed references to *buntu from code and documentation because of
an unfortunate trademark use policy.
http://joeyh.name/blog/entry/trademark_nonsense/
That included changing a data constructor to "FooBuntu", an API change.
|
|
different backup properties, to avoid concurrent jobs fighting over scarce resources (particularly memory). Other jobs block on a lock file.
|
|
|
|
|
|
|
|
Simply use onChange to let any other property by run after letsencrypt
gets/renews the cert. Much simpler and allows for revertable properties
too!
|
|
|
|
|
|
|
|
|
|
It's currently not letting me make a cert for kitenet.net as I made too
many during testing.
|
|
|
|
|
|
* Added Propellor.Property.LetsEncrypt
* Apache.httpsVirtualHost: New property, setting up a https vhost
with the certificate automatically obtained using letsencrypt.
|
|
|
|
unattended-upgrades is installed, to work around #812380 which results in many warnings from apt, including in cron mails.
|
|
a backup property; this causes obnam forget to be run.
|
|
|
|
|
|
|
|
|
|
|
