Created attachment 794111 [details] dev-haskell:exceptions-0.10.4-r1:20220724-220400.log =dev-haskell/exceptions-0.10.4-r1 fails to install for me, with these eclass error messages: * Cabal package 'exceptions-0.10.4' is shipped with 'PM:8.10.4-r1' ('8.10.4'). * Ebuild author forgot an entry in CABAL_CORE_LIB_GHC_PV='PM:8.10.5-r1 PM:8.10.6 PM:8.10.7 PM:9.0.1-r1 PM:9.0.2 PM:9999'. * Found in /usr/lib64/ghc-8.10.4/package.conf.d.initial. And indeed, the primary difference between the ebuild for -0.10.4 in /var/db/pkg and the ebuild in the tree is the removal of GHC versions prior to 8.10.5-r1 from $CABAL_CORE_LIB_GHC_PV .
Created attachment 794114 [details] emerge-info.txt
exceptions-0.10.4 is a bundled library with ghc-9.0.2, so you need to upgrade to ghc-9.0.2 and run haskell-updater. After that, and everything should work. If you're stuck on being unable to upgrade to ghc-9.0.2, let me know.
The very same has happened to me when I tried upgrading from dev-haskell/exceptions-0.10.4 to dev-haskell/exceptions-0.10.4-r1 , but I have followed a dirtier path to allow the package to be installed: 1. I (re)moved exceptions-0.10.4-gentoo-ghc-8.10.4-r1.conf from /usr/lib64/ghc-8.10.4/package.conf.d.initial *and* exceptions-0.10.4-gentoo-ghc-8.10.4-r1.conf from /usr/lib64/ghc-8.10.4/package.conf.d . 2. Then I ran as root both ghc-pkg recache and ghc-pkg recache --global-package-db=/usr/lib64/ghc-8.10.4/package.conf.d.initial . 3. Last, dev-haskell/exceptions-0.10.4-r1 could be installed with no collision.
Ah, I forgot to mention that prior to that I did "ghc-pkg unregister --force exceptions-0.10.4" in order to force deregister the package, when I was trying to have dev-haskell/exceptions-0.10.4-r1 installed.
All my systems are "mostly-stable", with any additions to package.accept_keywords to meet dependencies being the lowest version that satisfies all reverse dependencies (unless it fails to build or fails tests and a higher version fixes such issues). In any case, the problematic GHC version has been removed from::Gentoo, so this is no longer an issue.