gnusosa's centralized propellor repository for hosts spin-up. https://git.gnusosa.net/propellor/atom?h=master 2018-05-03T16:25:25Z 2018-05-03T16:25:25Z Joey Hess joeyh@joeyh.name 2018-05-03T16:25:25Z urn:sha1:94653981cab8a9e0640a8ce3eee54a186479c1e5 Surprised this didn't come up before, since propellor was run against progressively old versions of libraries when propelling eg, a chroot. It finally broke on an arm box, where libm got updated to a new version and propellor used a symbol from the new version. The comment says that propellor may be running from an existing shim in which case it's reused. That could be a nested chroot or other container, or perhaps propellor was deployed via a precompiled tarball which is built using a shim. The code used to use "checkAlreadyShimmed shim" which I don't see how it deals with either of those scenarios. Changed to "checkAlreadyShimmed propellorbin", which I think will deal with them, but I've not tested such scenarios. Added code to delete old versions of libraries out of the shim directory to avoid masses of old ones piling up over time. Property.Chroot sets up the shim directory and then bind mounts it into the chroot. To avoid deleting the source of a bind mount, made this only delete files in the shim directory, but not the shim directory itself. 2017-11-18T01:58:53Z Joey Hess joeyh@joeyh.name 2017-11-18T01:58:39Z urn:sha1:6dae019be9ebed76f282ec3cb258df7bf5891320 Reconsidered making services never run inside chroots, that seemed too potentially limiting. Using Info rather than checking policy-rc.d because it will also work outside of debian, but more because policy-rc.d has an extremely complicated interface and I didn't want to deal with it. This commit was sponsored by Jochen Bartl on Patreon. 2017-10-19T19:35:29Z Nicolas Schodet nico@ni.fr.eu.org 2017-10-19T19:35:29Z urn:sha1:b437fa963d7e44945d24c1c5a6453cebcaf7a682 2017-07-29T05:42:21Z Joey Hess joeyh@joeyh.name 2017-07-29T05:42:21Z urn:sha1:680c55d120033582e1b2316110b163684c4a918a 2017-07-06T00:59:39Z Joey Hess joeyh@joeyh.name 2017-07-06T00:58:03Z urn:sha1:7e9dc8880fc18d9dbaef039b3fc81db40cbdf9a9 2017-07-06T00:19:33Z Joey Hess joeyh@joeyh.name 2017-07-06T00:19:19Z urn:sha1:68f864299303ac8d510f19d67e8d7e6fe0681138 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. 2017-07-05T17:52:29Z Joey Hess joeyh@joeyh.name 2017-07-05T17:52:29Z urn:sha1:2b9d5ca90f053ad21fbbab89b3045bd0822400d5 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. 2017-05-16T00:12:08Z Joey Hess joeyh@joeyh.name 2017-05-16T00:12:08Z urn:sha1:d3b49aa149ea8ac9052b5b3d2a048206a7293301 2017-05-16T00:09:31Z Joey Hess joeyh@joeyh.name 2017-05-16T00:09:31Z urn:sha1:ba3bd76f4ade7ffeea3c1837f868f5264d284a8c 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. 2017-04-10T15:12:17Z Joey Hess joeyh@joeyh.name 2017-04-10T15:12:17Z urn:sha1:03950541b77405b8822dd2cadb47bc249a2bb5d3