gnusosa's centralized propellor repository for hosts spin-up. https://git.gnusosa.net/propellor/atom?h=master 2018-05-18T15:26:10Z 2018-05-18T15:26:10Z Joey Hess joeyh@joeyh.name 2018-05-18T15:26:10Z urn:sha1:f35f487831872bf4254b2712f2f49abbb03318e1 Use git verify-commit to verify gpg signatures, rather than the old method of parsing git log output. These two methods should always have the same result. Note that git verify-commit allows signatures with unknown validity, the same as git log's "U" output which was accepted. So any key in the gpg keyring is allowed to sign the commit. Propellor provides gpg with a keyring containing only the allowed keys. Needs git 2.0, which is in even debian oldstable. This commit was sponsored by Ewen McNeill on Patreon. 2018-04-30T13:16:05Z Joey Hess joeyh@joeyh.name 2018-04-30T13:16:05Z urn:sha1:b6ac64737b59e74d4aa2d889690e8fab3772d2c6 This reverts commit 02eca2ae4cf51d8e83d94d8359e15ac053451109. This seems to have broken propellor badly, in testing I'm seeing it crash at the end of a run with "thread blocked indefinitely in an STM transaction" and also during the run it printed out some odd output like: apache2: apache2: dummy IN SSHFP 4 1 35df80973f5877e4041f1b70947385eb2f6a0822 dummy IN SSHFP 4 2 3a0bb426e76eebc5c56e3b0f1428aa9d18539e9621bf8f9e3b7f56a4e7d81c85 Which seems like it might be output of commands that propellor is supposed to be reading? Seems likely that there's a bug or two that have crept into then concurrent-output library since the version embedded in propellor. 2018-04-23T17:56:56Z Joey Hess joeyh@joeyh.name 2018-04-23T17:56:56Z urn:sha1:09768ffa20997ee42b5860d90318419d5ef38bca Removed deps on transformers, text, stm. Updated debian/control and Propellor.Bootstrap accordingly. Sorted the lists of deps to make it easier to keep them in sync. 2017-10-04T17:22:50Z Joey Hess joeyh@joeyh.name 2017-10-04T17:22:50Z urn:sha1:af148be7226596433f8bee57f7a0002d6b23f4fb propellor currently still embeds concurrent-output, so the debian package does not need to depend on the library. 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-03-08T21:02:33Z Joey Hess joeyh@joeyh.name 2017-03-08T21:02:33Z urn:sha1:15690355cfc8f3562a9664896e83ca7989cef603 It's not used by propellor any longer. Has not been used for a long time actually. 2016-08-20T21:36:38Z Joey Hess joeyh@joeyh.name 2016-08-20T21:36:38Z urn:sha1:19ba498d109d02b8f19f71039ab11f6d612ade21 2016-08-20T18:52:23Z Sean Whitton spwhitton@spwhitton.name 2016-08-20T15:33:20Z urn:sha1:845d9de7ab790a1691237c8f3b7a6bf8787b3489 Fixes merging the /usr/src/propellor git bundle with git 2.9. 2016-05-22T20:05:15Z Joey Hess joeyh@joeyh.name 2016-05-22T20:05:15Z urn:sha1:23c0efee2ebf3575840e75af115a782cb447dd87 2016-03-28T02:10:48Z Joey Hess joeyh@joeyh.name 2016-03-28T02:10:48Z urn:sha1:af7b2d61c0c7f9b4fe53d8f5d18b5426a93cbd7b Using the external concurrent-output library lets it be built with -O2 as is needed to get good runtime memory use. Enabling -O0 because ghc is using rather a lot more time and memory due to the new more complex types. old master branch: Linking dist/build/propellor-config/propellor-config ... 24.59user 0.97system 0:25.93elapsed 98%CPU (0avgtext+0avgdata 354612maxresident)k 1544inputs+46064outputs (0major+371244minor)pagefaults 0swaps this branch before -O0: Linking dist/build/propellor-config/propellor-config ... 25.56user 0.73system 0:26.61elapsed 98%CPU (0avgtext+0avgdata 345348maxresident)k 0inputs+43480outputs (0major+364163minor)pagefaults 0swaps this branch with -O0: Linking dist/build/propellor-config/propellor-config ... 11.91user 0.75system 0:12.97elapsed 97%CPU (0avgtext+0avgdata 237472maxresident)k 16inputs+37264outputs (0major+336166minor)pagefaults 0swaps Above benchmarks are building all source files needed by config-simple.hs. The story is rather worse for joeyconfig.hs; building it now needs over 500 mb even with -O0 :-/