| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Install dnsmasq first to avoid connfile conflict
Don't set up container when in chroot, won't work. Propellor should
perhaps prevent this..
|
|
|
|
|
|
|
|
|
|
|
|
* Borg: Converted BorgRepo from a String alias to a data type.
(API change)
* Borg: Allow specifying ssh private key to use when accessing a borg
repo by using the BorgRepoUsing constructor with UseSshKey.
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
|
|
|
|
|
|
|
|
|
And, the borg property adds a :: , so don't need that in the use on
branchable.
|
|
|
|
|
|
broke my dad's email client somehow
|
|
|
|
|
|
|
|
|
|
This reverts commit 83a708582d790a89af8c7d7806b88653889f8532.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I have a cron job updating a file in there..
|
|
|
|
|
|
MissingH is a heavy dependency, which pulls in parsec and a bunch of stuff.
So eliminating it makes propellor easier to install and less likely to
fail to build.
changesFileContent now uses hashable's hash. This may not be stable across
upgrades, I'm not sure -- but it's surely ok here, as the hash is not
stored.
socketFile also uses hash. I *think* this is ok, even if it's not stable.
If it's not stable, an upgrade might make propellor hash a hostname to a
different number, but with 9 digets of number in use, the chances of a
collision are small. In any case, I've opned a bug report asking for the
stability to be documented, and I think it's intended to be stable, only
the documentation is bad.
NB: I have not checked that the arch linux and freebsd packages for the new
deps, that Propellor.Bootstrap lists, are the right names or even exist.
Since propellor depends on hashable, it could be changed to use
unordered-containers, rather than containers, which would be faster and
perhaps less deps too.
This commit was sponsored by Alexander Thompson on Patreon.
|
|
This caused a problem when eg a gmail email was sent to branchable and
forwarded on to kite. Kite thought branchable was forging the dkim
signature of gmail, and gmail does strict enforcement of dkim, so it
rejected it.
DKIM seems like a mightly hefty hammer, and I remember similar issues
being dicussed where mailing list software got broken by DKIM.
I guess this will mean a few more joe-jobs get through, but I'd rather
not silently lose important legitimate email!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There is no armel build, unfortunately; the "arm" build is armhf at
least currently.
|
|
Signed-off-by: Zihao Wang <dev@wzhd.org>
|
|
|
