| Summary: | dev-texlive/texlive-mathextra-2015 file collision with dev-texlive/texlive-latexextra-2014 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jocelyn Mayer <l_indien> |
| Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | dev-portage, tex |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=612296 https://bugs.gentoo.org/show_bug.cgi?id=612300 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | dev-texlive/texlive-mathextra-2015 build log | ||
|
Description
Jocelyn Mayer
2017-03-11 10:11:11 UTC
tl-mathextra-2015 has:
DEPEND=">=dev-texlive/texlive-fontsrecommended-2015
>=dev-texlive/texlive-latex-2015
!<dev-texlive/texlive-latexextra-2015
"
RDEPEND="${DEPEND} "
So portage should handle that I think. CC'ing portage team in case it's a portage bug, but the texlive ebuild is fine I think.
The !<dev-texlive/texlive-latexextra-2015 blocker in the texlive-mathextra-2015 ebuild appears to be correct.
It's possible to trigger a file collision by using the emerge --nodeps option, since --nodeps causes blockers to be ignored. For example, this would trigger it:
emerge --nodeps texlive-mathextra
Thanks for investigating ! I did trigger this issue while doing a @world update. My update sequence is never using --nodeps, looking like: # emerge --pretend --verbose --deep --update --newuse @system [...] # emerge --verbose --deep --update --newuse @system [...] # emerge --pretend --verbose --deep --update --newuse @world [...] # emerge --verbose --deep --update --newuse @world [...] # emerge --pretend --verbose @preserved-rebuild [...] # emerge --verbose @preserved-rebuild [...] Then I think there might have been something wrong in portage dependency graph during this @world update... |
