amd64 ~ # emerge -p binutils-libs These are the packages that would be merged, in reverse order: Calculating dependencies ... .... ..... ........ !!! /etc/portage/package.env references non-existent file: /etc/portage/env/unchecked ...... ........ .............. ... .. .. .... done! Dependency resolution took 768.78 s. [ebuild R ] sys-libs/binutils-libs-2.39-r5 WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: sys-libs/binutils-libs:0 (sys-libs/binutils-libs-2.40-r5:0/2.40::gentoo, ebuild scheduled for merge) USE="-64-bit-bfd (-cet) -multitarget -nls -static-libs -test" ABI_X86="-32 (64) (-x32)" conflicts with sys-libs/binutils-libs:0/2.39= required by (dev-lang/ocaml-4.14.1:0/4.14.1::gentoo, installed) USE="emacs -flambda -latex -ocamlopt userland_GNU -xemacs" ABI_X86="(64)" ^^^^^^^^ Reproducible: Always
Please share world upgrade output instead. Need to see why OCaml can't be rebuilt.
There is insufficient information in this report to determine if this is a bug or a problem on your system. Please seek help in Gentoo support channels, and re-open with sufficient diagnostic information.
Did: emerge -C dev-lang/ocaml emerge -1 sys-libs/binutils-libs #upgrade caused dev-db/mariadb to rebuild emerge -1 dev-lang/ocaml # which worked fine. Bisecting dev-db/mariadb vs dev-lang/ocaml /var/db/repos/gentoo/dev-db/mariadb/mariadb-10.6.14.ebuild COMMON_DEPEND="... sys-libs/binutils-libs:0= ..." DEPEND="${COMMON_DEPEND} ..." RDEPEND="${COMMON_DEPEND} ..." /var/db/repos/gentoo/dev-lang/ocaml/ocaml-4.14.1.ebuild RDEPEND="sys-libs/binutils-libs:=" Ain't ebuild expert. Nevertheless I'd would have expected dev-lang/ocaml to behave the same way dev-db/mariadb did. No idea how dev-lang/ocaml ebuild should be modified in this regard.
You've unfortunately destroyed all relevant information then.
Created attachment 865002 [details] emerge world
The steps you took in comment 3 destroyed all actionable information; it is too late to provide further info in this bug. There is nothing more we can do.
The log I provided has been generated before action from comment 3. Later I managed to turn back to original condition and fortn. emerge -p world finally revealed another issue regarding dev-lang/ocaml. To my experience portage output can be very messy when a package causes issues, as explanation may push in the wrong direction. Only the package name fits. Anyhow original conditions have indeed been corrupted. Invalid status is fine by me.
