I tried to emerge dev-tex/latex-unicode-20041017. I got a [blocks B ] dev-texlive/texlive-latexrecommended ("dev-texlive/texlive-latexrecommended" is blocking dev-tex/latex-unicode-20041017) After playing around with some unmerge/depclean things unsuccessfully I have taken a look at the ebuild file (/usr/portage/dev-tex/latex-unicode/latex-unicode-20041017.ebuild). The ebuild seems to block the mentioned dev-texlive/texlive-latexrecommended: {{{ 20 DEPEND="!dev-texlive/texlive-latexrecommended 21 cjk? ( dev-tex/cjk-latex )" }}} But it inherits from the eclass latex-package: {{{ 5 inherit latex-package }}} The eclass latex-package in turn requires the virtual/latex-base package. From file /usr/portage/eclass/latex-package.eclass: {{{ 58 RDEPEND="virtual/latex-base" 59 DEPEND="${RDEPEND} 60 >=sys-apps/texinfo-4.2-r5" }}} ... which in turn requires the dev-texlive/texlive-latexrecommended package. From file /usr/portage/virtual/latex-base/latex-base-1.0.ebuild: {{{ 14 DEPEND="" 15 RDEPEND=" 16 dev-texlive/texlive-latexrecommended 17 dev-texlive/texlive-fontutils 18 " }}} Thus dev-tex/latex-unicode-20041017 requires AND blocks dev-texlive/texlive-latexrecommended at once. Reproducible: Always Steps to Reproduce: 0. emerge --sync 1. less /usr/portage/dev-tex/latex-unicode/latex-unicode-20041017.ebuild - dev-texlive/texlive-latexrecommended is blocked in line 20 - latex-package is inherited in line 5 2. less usr/portage/eclass/latex-package.eclass - virtual/latex-base is required in line 58 3. less /usr/portage/virtual/latex-base/latex-base-1.0.ebuild - dev-texlive/texlive-latexrecommended is required in line 16 Actual Results: I find that the dependencies are not well-formend. Expected Results: The opposite. I don't know what the actual problem with these two packages dev-tex/latex-unicode-20041017 and dev-texlive/texlive-latexrecommended might be. The maintainers will have their reasons to block latexrecommended from latex-unicode. But for now the ebuild dev-tex/latex-unicode-20041017 seems to be needless for it cannot be emerged at all.
*** This bug has been marked as a duplicate of bug 248489 ***
