Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 671824 - sys-apps/portage-2.3.52-r1 instprep invalid logfile warnings
Summary: sys-apps/portage-2.3.52-r1 instprep invalid logfile warnings
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
Keywords: InVCS
Depends on:
Blocks: 671498
  Show dependency tree
Reported: 2018-11-24 22:24 UTC by Duncan
Modified: 2019-04-10 04:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Duncan 2018-11-24 22:24:56 UTC
Nutshell ($PF expanded):

!!! can't process invalid log file: /tmp/portage/$PF/temp/logging/instprep

Is instaprep related to recent changes regarding FEATURES (listed below) I have turned off, and it isn't prepared for the absence of the file due to having the features turned off?

I recently started seeing this (AFAIK harmless but it looks alarming) warning on at least some merges.  I suspect it may be on all of them, but I don't normally see the full logs on successful merges due to running parallel, and the warning apparently doesn't show up in the per-package message summary at the end, only in the full log.

This specific example is taken from an individual elfutils binpkg downgrade run (due from elfutils-0.175 due to the recent masking, run individually after seeing it in the --update --deep --ask output, in ordered to take advantage of the older binpkg):

>>> Regenerating /etc/
>>> Original instance of package unmerged safely.
>>> dev-libs/elfutils-0.173 merged.
>>> Regenerating /etc/
!!! can't process invalid log file: /tmp/portage/dev-libs/elfutils-0.173/temp/logging/instprep
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.

In case it's FEATURES related, note that at the last portage upgrade I decided it was time to update them, specifically matched my FEATURES list against that in the manpage, and explicitly set each one either FEATURE or -FEATURE.  I know I deleted an outdated one or two but don't remember whether I actually activated/deactivated any of the current ones.  Here's what portage reports as active now:

FEATURES="binpkg-docompress binpkg-dostrip binpkg-logs buildpkg buildsyspkg candy ccache cgroup collision-protect config-protect-if-modified distlocks downgrade-backup ebuild-locks fixlafiles ipc-sandbox merge-sync mount-sandbox network-sandbox news parallel-fetch parallel-install pid-sandbox protect-owned sandbox sfperms strict strict-keepdir unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
Comment 1 Larry the Git Cow gentoo-dev 2018-11-25 00:02:59 UTC
The bug has been referenced in the following commit(s):

commit c8eae4eb00c3c14ec27f4bb8c8983ff6274e478e
Author:     Zac Medico <>
AuthorDate: 2018-11-24 23:45:37 +0000
Commit:     Zac Medico <>
CommitDate: 2018-11-25 00:02:10 +0000

    EBUILD_PHASES: add instprep (bug 671824)
    Whitelist instprep for collect_ebuild_messages, so that it will
    not reject elog messages from the instprep phase like this:
    !!! can't process invalid log file: /tmp/portage/$PF/temp/logging/instprep
    Fixes: 3f50bfc1ae5b ("Support disabling docompress for binary package builds")
    Reported-by: Duncan <>
    Signed-off-by: Zac Medico <>

 lib/portage/ | 1 +
 1 file changed, 1 insertion(+)
Comment 2 Zac Medico gentoo-dev 2018-11-25 00:03:31 UTC
Comment 3 Duncan 2018-11-25 00:37:22 UTC
Oops!  s/instaprep/instprep/

(Not instant, install!  I had the same problem when reading the patch discussion on the portage-dev list.  Seems I picked up "instaprep" from somewhere and it's confusing me.  Maybe I should have mentioned it then.  Oh, well.)
Comment 4 Zac Medico gentoo-dev 2019-04-10 04:32:38 UTC
Fixed in portage-2.3.62.