| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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 commit was sponsored by Jake Vosloo on Patreon.
|
|
Removed mountNow as a top-level property, as I don't think it makes
sense for anything except for mounted to use it.
db45x's patch turns out to have introduced a bug in mounted's use of
"mountNow src". That made mountNow check if the device was a mount
point, which it isn't. The fix would have been to use "mountNow mnt",
but my inlining of mountnow just basically reverted the part of the
patch that introduced the bug.
swapOn does not involve the fstab so moved to the Mount module.
(Also noticed that Mount.mounted is a kind of weird property, given that
it fails the next time ran. It's only used internally by some chroot
properties, so I left it as-is, but added a comment. It might make sense
to make Mount.mounted check like mountNow does if the thing is already
mounted.)
|
|
|
|
|
|
|
|
|
|
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!
|
|
* Fix bug when using setContainerProps with a chroot that prevented
properties added to a chroot that way from being seen when propellor
was running inside the chroot. This affected disk image creation, and
possibly other things that use chroots.
The problem was, propagateChrootInfo was being passed the initial
version of the Chroot, but then the Chroot got more properties
added, and so those were not recorded in the _chroot info.
Fix was simply to make InfoPropagator be passed the Chroot as an
additional parameter, so Chroot.provisioned' can pass in the final
Chroot to it.
|
|
|
|
changed around version 0.6. Both output formats are supported now.
Do we trust kpartx to not change again, given how little documented its
output format is and that it's changed w/o warning? Little other things
like vmdebootstrap depend on its output in the same way..
This commit was sponsored by Ignacio on Patreon.
|
|
building disk images. /dev/mapper/loop* symlinks are now detected as block devices.
|
|
the default CDN.
This info is used by Apt.stdSourcesList and Sbuild.builtFor.
Thanks, Sean Whitton.
|
|
|
|
|
|
|
|
lost kite2 ed25519 key
|
|
in addition to the old secret_id_key.
|
|
|
|
|
|
|
|
|
|
|
|
Though stdArchiveLines is not used in Apt.hs, this is the logical replacement
for the old debCdn property.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
