ebuildtester-0.1.10 tries to write to /etc/portage/package.XXX to unmask packages, while these are directories in the current Gentoo docker image, so unmasking (and ebuildtester) fails. This seems to have been fixed in 0.1.11 over on ebuildtesters github (https://github.com/nicolasbock/ebuildtester/commit/e3d20784885dfd967c5e99432d5e905c5a00c240), so an ebuild version bump would fix the issue I suppose.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a8646562250e9066f74d5ec6aa8e34a53d957d90 commit a8646562250e9066f74d5ec6aa8e34a53d957d90 Author: Nicolas Bock <nicolasbock@gentoo.org> AuthorDate: 2018-09-26 11:32:59 +0000 Commit: Nicolas Bock <nicolasbock@gentoo.org> CommitDate: 2018-09-26 11:41:00 +0000 dev-python/ebuildtester: Version bump to v0.12 Closes: https://bugs.gentoo.org/665318 Package-Manager: Portage-2.3.49, Repoman-2.3.10 dev-python/ebuildtester/Manifest | 1 + dev-python/ebuildtester/ebuildtester-0.1.12.ebuild | 31 ++++++++++++++++++++++ 2 files changed, 32 insertions(+)
