|author||Joey Hess||2018-05-03 12:25:25 -0400|
|committer||Joey Hess||2018-05-03 12:25:25 -0400|
Update shim each time propellor is run in a container, to deal with library 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.
Diffstat (limited to 'debian')
1 files changed, 2 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog
index 4d077d35..39fd6cba 100644
@@ -7,6 +7,8 @@ propellor (5.3.6) UNRELEASED; urgency=medium
* stack.yaml: Updated to lts-9.21.
* Make Schroot.overlaysInTmpfs revertable
Thanks, Sean Whitton
+ * Update shim each time propellor is run in a container, to deal with
+ library version changes.
-- Joey Hess <firstname.lastname@example.org> Mon, 23 Apr 2018 13:12:25 -0400