| Summary: | dev-libs/icu-51.2-r1 conflicts with dev-tex/bibtexu-3.71_p20120701 | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Dirkjan Ochtman (RETIRED) <djc> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aballier, dschridde+gentoobugs, gentoo.2019, gentoo, hrabe, office, ps, tb, tex |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 484436, 496770 | ||
|
Description
Dirkjan Ochtman (RETIRED)
2013-11-04 09:56:11 UTC
This also happened to me when updating my box this morning:
====
WARNING: One or more updates have been skipped due to a dependency conflict:
dev-libs/icu:0
(dev-libs/icu-51.2-r1::gentoo, ebuild scheduled for merge) conflicts with
>=dev-libs/icu-4.4:0/51.1= required by (dev-tex/bibtexu-3.71_p20120701::gentoo, installed)
Would you like to merge these packages? [Yes/No] No
====
This is actually a portage bug. I think. You merged bibtexu when it had a subslot dependency on icu. Afterwards aballier removed the subslot dependency in the ebuild of bibtexu again. For some silly reason, portage cannot handle the upgrade then anymore. Workaround: emerge -1 dev-tex/bibtexu (which updates the vdb dependencies with those of the ebuild) and then repeat whatever you were doing before. Alexis, please please consider re-adding the subslot dependency on icu in the bibtexu ebuild. I don't want to revert your revert, but "preventing extra rebuilds" for a package that takes 20s to build is not a very strong argument. (In reply to Andreas K. Hüttel from comment #3) > Alexis, please please consider re-adding the subslot dependency on icu in > the bibtexu ebuild. I don't want to revert your revert, but "preventing > extra rebuilds" for a package that takes 20s to build is not a very strong > argument. since := deps are mainly about rebuilding and those rebuilds are useless with the current icu subslot, I don't understand what a "strong argument" could be :) just to be a bit more clear: if icu is _that_ insane and nobody wants to sanitize it, the best route would likely be to move bibtexu back into texlive-core and use the bundled icu copy since that's what upstream recommends... (In reply to Andreas K. Hüttel from comment #2) > Workaround: > emerge -1 dev-tex/bibtexu > (which updates the vdb dependencies with those of the ebuild) > > and then repeat whatever you were doing before. You're right! Thanks very much indeed :) *** Bug 490459 has been marked as a duplicate of this bug. *** *** Bug 491454 has been marked as a duplicate of this bug. *** This fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c752202d57a1e3163aded69301e2d71d1ea26ae7 (In reply to Sebastian Luther (few) from comment #9) > This fixed in git: > > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit; > h=c752202d57a1e3163aded69301e2d71d1ea26ae7 Could a new portage version be released including this and many other fixes you committed in git? I still see people suffering this bug (for example) Thanks a lot (In reply to Pacho Ramos from comment #10) > (In reply to Sebastian Luther (few) from comment #9) > > This fixed in git: > > > > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit; > > h=c752202d57a1e3163aded69301e2d71d1ea26ae7 > > Could a new portage version be released including this and many other fixes > you committed in git? I still see people suffering this bug (for example) > > Thanks a lot Pretty please, yes do that!!! We'd actually even need this in stable as soon as possible... see e.g. bug 469770 comment 4 (In reply to Andreas K. Hüttel from comment #11) that should have been bug 496770 comment 4 Released in sys-apps/portage-2.2.8. |
