The build fails in the prepare phase: * Applying pimcommon-17.04.3-deps.patch ... /var/tmp/portage/kde-apps/pimcommon-17.08.3/temp/environment: line 1442: /var/tmp/portage/kde-apps/pimcommon-17.08.3/files/pimcommon-17.04.3-deps.patch: No such file or directory The ebuild declare that patch, but the file is missing. Note, also, the unmatching version of the patch filename. $ grep PATCHES /usr/portage/kde-apps/pimcommon/pimcommon-17.08.3.ebuild PATCHES=( "${FILESDIR}/${PN}-17.04.3-deps.patch" ) Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge =kde-apps/pimcommon-17.08.3 3. Actual Results: The prepare phase fails Expected Results: Success
I also looked for the patch in my laptop, where I still have an unsynced portage. There I have the kde-apps/pimcommon-17.04.3 ebuild, but the patch didn't exist at that time.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8b26c3ab332c48e90ed09642e429bf059dde9c94 commit 8b26c3ab332c48e90ed09642e429bf059dde9c94 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2017-12-01 08:58:12 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2017-12-01 08:59:09 +0000 kde-apps/pimcommon: Re-add accidentally removed patch Closes: https://bugs.gentoo.org/639370 Package-Manager: Portage-2.3.13, Repoman-2.3.4 kde-apps/pimcommon/Manifest | 2 +- .../pimcommon/files/pimcommon-17.04.3-deps.patch | 54 ++++++++++++++++++++++ 2 files changed, 55 insertions(+), 1 deletion(-)
