summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-06-11creating Adding support for a SQL serverNicolas.Schodet
2018-05-17add news item for propellor 5.4.0Joey Hess
2018-05-17releasing package propellor version 5.4.0Joey Hess
2018-05-17Merge branch 'joeyconfig'Joey Hess
2018-05-17add missing close parenJoey Hess
2018-05-17Merge branch 'master' of ssh://propellor.branchable.comJoey Hess
2018-05-17tried to improve changelog wordingJoey Hess
2018-05-17Apt.installedBackport replaced with Apt.backportInstalledSean Whitton
Apt.installedBackport would do this: apt-get install -t stretch-backports foo bar Apt.backportInstalled does this: apt-get install foo/stretch-backports bar/stretch-backports The Apt.installedBackport behaviour can install the dependencies of foo and bar from stretch-backports even when the versions in stretch will satisfy the dependencies of the backports of foo and bar. So this property can result in very many more backports being installed on the host when intended. But the number of installed backports should always be minimised. Worse, whether this happens is highly dependent on the system state, and the order in which other properties get ensured. For example, & Apt.installed ["dgit"] & Apt.installedBackport ["dgit"] will install only dgit from stretch-backports, but unless debhelper and devscripts happen to already be installed, & Apt.installedBackport ["dgit"] & Apt.installed ["dgit"] will install dgit, debhelper, devscripts and maybe more from backports. This is surprising, difficult to debug, and breaks the expectation that when the order in which properties are ensured is not specified with connectives like `requires` and `before`, ensuring them in any order will produce the same result. Property renamed because user configs should not silently break, as they would if they did not list dependencies that must be installed from stable-backports. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
2018-05-17Restic.installed: stop trying to install a backport on jessieSean Whitton
No such backport exists in the archive. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
2018-05-15fix linkdave@2ab82f485adf7e2ce787066e35f5f9789bff430b
2018-05-09propellor spinJoey Hess
2018-05-09add news item for propellor 5.3.6Joey Hess
2018-05-09releasing package propellor version 5.3.6Joey Hess
2018-05-09clean up after mergeJoey Hess
2018-05-09Merge branch 'joeyconfig'Joey Hess
2018-05-09fix linkJoey Hess
2018-05-07propellor spinJoey Hess
2018-05-06setting up joeyconfig after mergeJoey Hess
2018-05-06changelogJoey Hess
2018-05-06clean up after mergeJoey Hess
2018-05-06Merge branch 'joeyconfig'Joey Hess
2018-05-06setting up joeyconfig after mergeJoey Hess
2018-05-06Merge remote-tracking branch 'felix/unbound' into joeyconfigJoey Hess
2018-05-06remove rsyslog from honeybee to save disk spaceJoey Hess
2018-05-05propellor spinJoey Hess
2018-05-05propellor spinJoey Hess
2018-05-05Unbound: move haddock comment to cachingDnsServerFélix Sipma
2018-05-05propellor spinJoey Hess
2018-05-05propellor spinJoey Hess
2018-05-04propellor spinJoey Hess
2018-05-04updateJoey Hess
2018-05-04markdownJoey Hess
2018-05-04Unbound: add a warning note for CNAMEFélix Sipma
2018-05-04Unbound: handle missing recordsFélix Sipma
2018-05-04Unbound: simplify existing recordsFélix Sipma
2018-05-04Unbound: handle SRV recordFélix Sipma
2018-05-03clean up after mergeJoey Hess
2018-05-03Merge branch 'joeyconfig'Joey Hess
2018-05-03propellor spinJoey Hess
2018-05-03commentJoey Hess
2018-05-03propellor spinJoey Hess
2018-05-03remove badly placed and redundant commentJoey Hess
2018-05-03propellor spinJoey Hess
2018-05-03setting up joeyconfig after mergeJoey Hess
2018-05-03Merge branch 'master' into joeyconfigJoey Hess
2018-05-03Update shim each time propellor is run in a container, to deal with library ↵Joey Hess
version changes. 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.
2018-05-03propellor spinJoey Hess
2018-05-03propellor spinJoey Hess
2018-05-02Merge branch 'master' of ssh://propellor.branchable.comJoey Hess
2018-05-02changelogJoey Hess
generated by cgit v1.3-2-g0d8e (git 2.53.0) at 2026-06-25 17:01:38 +0000