When trying to bootstrap a fresh prefix installation (on Ubuntu) the bootstrapping process dies after completing stage 3 when trying to perform emerge -e system. The reason for the breakage is that the prefix overlay contains an old portage version which is not updated during any of the stages. Reproducible: Always Steps to Reproduce: 1. Download latest bootstrap-prefix.sh 2. Execute bootstrap-prefix.sh to create a fresh prefix installation. Actual Results: Bootstrap fails after completing stage 3: * stage3 successfully finished * IMPORTANT: 4 news items need reading for repository 'gentoo_prefix'. * Use eselect news to read news items. Calculating dependencies... done! Calculating dependencies... done! !!! All ebuilds that could satisfy ">=dev-util/pkgconfig-0.27.1" have been masked. !!! One of the following masked packages is required to complete your request: - dev-util/pkgconfig-9999::gentoo_prefix (masked by: EAPI 5) - dev-util/pkgconfig-0.28::gentoo_prefix (masked by: EAPI 5) - dev-util/pkgconfig-0.27.1::gentoo_prefix (masked by: EAPI 5) The current version of portage supports EAPI '4'. You must upgrade to a newer version of portage before EAPI masked packages can be installed. Expected Results: Bootstrap should complete without problems. The problem can be resolved by manually upgrading portage inside the prefix and running emerge -e system again. This time it works without problems.
Thanks a lot for reporting. This bug is being worked upon.
snapshot update impossible, bootstrapping is in a miserable state, due to portage erroring out (xception BlockingIOError: BlockingIOError(35, 'write could not complete without blocking', 0) in <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'> ignored)
(In reply to comment #2) > snapshot update impossible, bootstrapping is in a miserable state, due to > portage erroring out (xception BlockingIOError: BlockingIOError(35, 'write > could not complete without blocking', 0) in <_io.TextIOWrapper > name='<stdout>' mode='w' encoding='UTF-8'> ignored) Not aware of details of the snapshot update. What does this error mean?
this means we have a portage that is horribly broken, preventing the whole bootstrap process to succeed
On OpenSUSE 11, I ran into this error with the automated bootstrap script. When it aborted with the EAPI4 error, I was able to continue by doing the following: 1) set the environment variables per the manual bootstrap process, 2) emerge portage, 3) emerge -e system (what the script originally failed on). I ran into another error after that but at least this allowed me to move forward from the EAPI4 error and get further along.
this should be fixed tomorrow, thanks
