libreoffice-bin needs to have its poppler dependency updated.
I had to remove it to process a world update and libreoffice-bin is depending on an obsolete version of poppler, causing a conflict with the current installed version.
which version of libreoffice-bin?
(In reply to shentino from comment #0)
> libreoffice-bin needs to have its poppler dependency updated.
> I had to remove it to process a world update and libreoffice-bin is
> depending on an obsolete version of poppler, causing a conflict with the
> current installed version.
So which version of poppler do you have?
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
(app-text/poppler-0.45.0:0/62::gentoo, ebuild scheduled for merge) pulled in by
app-text/poppler:0/62 required by (app-office/libreoffice-bin-184.108.40.206:0/0::gentoo, ebuild scheduled for merge)
(app-text/poppler-0.46.0-r1:0/63::gentoo, installed) pulled in by
>=app-text/poppler-0.12.3-r3:0/63= required by (app-text/texlive-core-2014-r4:0/0::gentoo, installed)
(and 1 more with the same problem)
Btw, aren't shared libraries supposed to be dynamically linked? Why does libreoffice-bin have to depend on an exact version of poppler anyway? Shouldn't the current version be backward compatible with the version libreoffice-bin was linked against?
it's a downside of having rolling release. it's because poppler (and other libs) bumped independently of libreoffice-bin... the last one need permanent regeneration, specially when you use ~arch. That's the fact you have to bear. libreoffice-bin is a special binary that built against certain "slice" of libraries versions (and normlly only stable versions), so when library updated, say, poppler or glew, for example, lo-bin will not work properly. To workaround this, either slower pace of lib bumps needed or lo-bin needed continous bumps, which is quite time and power consuming task.