Bug 927687 – Can't emerge binutils during profile upgrade

• Status: RESOLVED DUPLICATE of bug 927631
• Product: Gentoo Linux

[Description Stephan Litterst 2024-03-24 10:27:26 UTC]

Created attachment 888390 [details]
output of emerge --info

I am lost in the last profiles upgrade to version 23 and have no idea what went wrong :-/

I followed the instructions in 2024-03-22-new-23-profiles and changed the profile from
  [5]   default/linux/amd64/17.1/desktop (exp)
to
  [46]  default/linux/amd64/23.0/split-usr/desktop (stable) *

I am still using openrc (it is an old installation).

I commeted out the CHOST line in /etc/portage/make.conf.

I created a etc/portage/binrepos.conf as the installation of binutils wants it.

And I run into this problem:
 Messages for package sys-devel/binutils-2.41-r5:

 * 
 * Your profile is of type merged-usr, but your directories
 * on-disk are of type split-usr.
 * Please switch back to your last valid profile setting and
 * read the documentation about merged-usr and profile changes.
 * 
 * ERROR: sys-devel/binutils-2.41-r5::gentoo failed (setup phase):
 *   ERROR: 23.0 merged-usr profile, but disk is split-usr
 * 
 * Call stack:
 *            ebuild.sh, line 784:  Called __ebuild_main 'setup'
 *   phase-functions.sh, line 991:  Called __source_all_bashrcs
 *            ebuild.sh, line 426:  Called __try_source '/usr/portage/profiles/releases/23.0/profile.bashrc'
 *            ebuild.sh, line 487:  Called __qa_source '/usr/portage/profiles/releases/23.0/profile.bashrc'
 *            ebuild.sh, line 123:  Called source '/usr/portage/profiles/releases/23.0/profile.bashrc'
 *       profile.bashrc, line   9:  Called die
 * The specific snippet of code:
 *              die "ERROR: 23.0 merged-usr profile, but disk is split-usr"
 * 
 * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.41-r5::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.41-r5::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.41-r5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.41-r5/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/binutils-2.41-r5/empty'
 * S: '/var/tmp/portage/sys-devel/binutils-2.41-r5/work/binutils-2.41'

Any ideas? What could possibly be wrong?

[Comment 1 Stephan Litterst 2024-03-24 10:28:12 UTC]

Created attachment 888391 [details]
output of emerge -pqv

[Comment 2 Stephan Litterst 2024-03-24 10:29:24 UTC]

Created attachment 888392 [details]
build.log

[Comment 3 Stephan Litterst 2024-03-24 10:29:45 UTC]

Created attachment 888393 [details]
environment

[Comment 4 Sam James 2024-03-24 10:30:49 UTC]

Please emerge --sync, we think we sorted this one out. Thanks!

*** This bug has been marked as a duplicate of bug 927631 ***

[Comment 5 Stephan Litterst 2024-03-25 19:33:29 UTC]

Thanks! emerge --sync solved it.