Created attachment 358694 [details] output of emerge --info Installing amanda-3.3.3 with USE-flag *minimal* fails with error: chmod: cannot access ‘/var/tmp/portage/app-backup/amanda-3.3.3/image//var/spool/amanda/DailySet1’: No such file or directory chmod: cannot access ‘/var/tmp/portage/app-backup/amanda-3.3.3/image//etc/amanda/DailySet1’: No such file or directory * ERROR: app-backup/amanda-3.3.3::gentoo failed (install phase): * fperms failed The problem is, that the directories ${AMANDA_USER_HOMEDIR}/${AMANDA_CONFIG_NAME} and /etc/amanda/${AMANDA_CONFIG_NAME} are not created, when USE-flag minimal is active. I attach a patch for the ebuild that solves this problem.
Created attachment 358696 [details] complet build log
Created attachment 358698 [details, diff] patch file that solves the problem
I got hit with this bug, but as a temporary work-around, I installed the whole Amanda (even though I only needed the minimal client). During the installation of the full Amanda, the DailySet1 directories are indeed created, and the fperm failure does not occur as a result. Thanks for the patch, Martin. I'll keep an eye open for when it hits Portage.
@the maintainer of app-backup/amanda: Please apply my patch in the next ebuild. Thanks, Martin
successfully applied Martin's patch to my local ebuild. Suggesting patch to be included in portage.
This Bug persists in the most-recent 3.3.3-r1 version bump, which went stable a couple of weeks ago :-( Can this patch be incorporated into a fresh version-bump, and make the journey into the Stable tree? Thank-you,
InCVS.
