app-portage/unsymlink-lib: Bump to v11, with lib32 removal fix
authorMichał Górny <mgorny@gentoo.org>
Wed, 10 Jan 2018 09:17:47 +0000 (10:17 +0100)
committerMichał Górny <mgorny@gentoo.org>
Wed, 10 Jan 2018 09:30:47 +0000 (10:30 +0100)
commit6a514c6f017bfbf921745cfe87e54dd2b15b236b
tree133668b09fba61e11d73ec4b940d514f4894dc09
parentb3ce9a81ab6ed752bfd0a5eeee0dd3daf9b920e0
app-portage/unsymlink-lib: Bump to v11, with lib32 removal fix

Bump to v11 that improves handling of lib32 removal failures. The errors
are now fatal and request resuming explicitly, rather than outputting
a warning that is easily missed. This also lets us allow lib32
to be a mount point again.

This version also tries to give more explicit explanation when lib32
is actually a mount point. However, the os.path.ismount() function
does not seem to detect bind mounts, as in the linked bug report.

Closes: https://bugs.gentoo.org/643632
app-portage/unsymlink-lib/Manifest
app-portage/unsymlink-lib/unsymlink-lib-11.ebuild [new file with mode: 0644]