dev-libs/icu-64.2 has been stabilized for amd64 (https://bugs.gentoo.org/685288), so libreoffice-bin needs to be recompiled.
Guys, this is happens every time with any dep upgrade of libreoffice-bin. It is very hard to use libreoffice-bin in a long run because of these issues. https://bugs.gentoo.org/467836 (icu, 2013) https://bugs.gentoo.org/485574 (boost, 2013) https://bugs.gentoo.org/639132 (python, 2017) Can you add libreoffice-bin to be a blocker, perhaps automatically? Gentoo should stabilize all these deps at the same time with libreoffice-bin. The next bin version should be in the portage at least so users can keyword it. For now, we are stacked with non-upgradable system.
Please don't interfere with stabilisation.
Sorry, since your comment on 685288 says it should be stabilized in sync with libreoffice, I thought this was a requirement for icu stabilization. Am I supposed to manually --exclude=icu at every upgrade in order not to break my stable system? I'm unsure what is the proper way to handle this until libreoffice-bin gets fixed :s
(In reply to Shiba from comment #3) > Sorry, since your comment on 685288 says it should be stabilized in sync > with libreoffice, I thought this was a requirement for icu stabilization. Am > I supposed to manually --exclude=icu at every upgrade in order not to break > my stable system? I'm unsure what is the proper way to handle this until > libreoffice-bin gets fixed :s I'm not sure what your problem is, with libreoffice-bin installed, portage will simply ignore the ICU upgrade and nothing is going to break.
I kept getting tons of conflicts (it even asked me to unmask icu 64.1) until I did the first upgrade with --exclude=icu. After that, emerge stopped being so confused and it's now working fine. Sorry I turned this into a forum :/
I'm getting this while trying to emerge libreoffice-bin from the beginning: emerge -vp libreoffice-bin These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild UD ] dev-libs/icu-63.1-r1:0/63.1::gentoo [64.2:0/64.2::gentoo] USE="-debug -doc -examples -static-libs" ABI_X86="32 (64) (-x32)" 0 KiB [ebuild N ] app-office/libreoffice-bin-6.1.5.2::gentoo USE="java kde -gnome" PYTHON_TARGETS="python3_6" 0 KiB Total: 2 packages (1 downgrade, 1 new), Size of downloads: 0 KiB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/icu:0 (dev-libs/icu-63.1-r1:0/63.1::gentoo, ebuild scheduled for merge) pulled in by dev-libs/icu:0/63.1 required by (app-office/libreoffice-bin-6.1.5.2:0/0::gentoo, ebuild scheduled for merge) ^^^^^^^ (dev-libs/icu-64.2:0/64.2::gentoo, installed) pulled in by dev-libs/icu:0/64.2= required by (media-libs/libzmf-0.0.2:0/0::gentoo, installed) ^^^^^^^^ (and 19 more with the same problem) NOTE: Use the '--verbose-conflicts' option to display parents omitted above It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. emerge -vp --exclude=icu libreoffice-bin does not work. What's the next step?
I managed to resolve by masking >=dev-libs/icu-64.1 temporary. The API of icu does not change much and I only seen something like this: net-libs/nodejs-11.14.0 (icu ? >=dev-libs/icu-63.1) The media-libs/libzmf you mentioned requires dev-libs/icu:= which means portage will just rebuild it after icu upgrade. The only potential problem is if you installed another binary software compiled against a different version of icu. The solution would be just to recompile affected packages (install libreoffice from source). The next step is to kick Gentoo devs butt, so they start planing in advance, compile a next -bin version and make it stable together with any related dependency as I highlighted earlier.
(In reply to Anton Bolshakov from comment #7) > The next step is to kick Gentoo devs butt, so they start planing in advance, > compile a next -bin version and make it stable together with any related > dependency as I highlighted earlier. Comments like this are rude and inappropriate for bug posts. Users need to appreciate that the vast majority of developers are volunteers. Be polite. Offer to help. Besides, at this time, nothing is broken and everything works.
(In reply to Andy Figueroa from comment #8) > Comments like this are rude and inappropriate for bug posts. Users need to > appreciate that the vast majority of developers are volunteers. Be polite. > Offer to help. Besides, at this time, nothing is broken and everything works. I agree with the first part. But I disagree with the second one. If you try to emerge world your system, the icu stable upgrade fails because libreoffice-bin explicitly requires icu-63.1-r1 if you have the binary package of libreoffice installed. So, I guess the only solution is that the Gentoo devs offer a newly compiled version against icu-0.64.
Also you might end up in the very unfortunate situation of having to downgrade icu, like it happened to Vasilis. I understand it doesn't break stable Gentoo, as both 63.1-r1 and 64.2 are marked stable, but please consider that icu triggers some big rebuilds, e.g. the WebKits, which on my main system take: Mon May 20 17:29:12 2019 >>> net-libs/webkit-gtk-2.24.2 merge time: 2 hours, 27 minutes and 28 seconds. Wed May 22 19:15:57 2019 >>> dev-qt/qtwebkit-5.212.0_pre20180120 merge time: 2 hours, 39 minutes and 57 seconds. Including everything else that would have been rebuilt, I don't think I'm exaggerating if I say it could have taken a full working day to get libreoffice-bin. Sorry if I keep stressing the point, but I believe that if getting libreoffice-bin ends up taking as long as building from source, it kinda fails its purpose. If Gentoo devs are interested in discussing this further, we can take this to the forum.
So, should we wait for a new compiled binary package in the next couple of days, or should we compile the source package anyway?
Why does this depend on the stabilisation of version 6.2*? Can libreoffice 6.1* not just be rebuilt with new icu and published as revision 1 with updated dependencies? I know this is all voluntary work and I highly appreciate it - but since LibreOffice is one of the packages you need to have on nearly every desktop system, even if you don't actively use it, just because of the documents that get thrown at you...
(In reply to Andreas Prieß from comment #12) > Why does this depend on the stabilisation of version 6.2*? Because we don't do work twice when it can be avoided. Stabilisation of 6.2.4.2 is just waiting on the binaries being made.
Before stabilization, you should push an ~arch version, let users test it during 30 days or something. You know Gentoo's policy better. I was facing few critical issues in the past. Once, libreoffice-bin would refuse to load at all (and that version was stabilized!).
That does not make sense for -bin.
Same problem here. Please recompile libreoffice-bin with new icu version or add a new libreoffice version to portage, compiled with new icu.
(In reply to Andreas Sturmlechner from comment #15) > That does not make sense for -bin. I do not understand that statement. Why?
I am building it right now so if anyone if interested I could do a quickpkg and provide you with a link.
Same here!
I'm sorry, but the stabilization for 6.2.4.2 takes way too long. In the mean time, we have a broken stable system, where icu wants to upgrade, but installed libreoffice-bin-6.1.5.2 blocks it. A newer 6.1.5.2 release should have been provided that was built with icu-64.2. Right now, we are forced to remove the binary package and compile from source, after all the compilation chaos that the newer icu causes.
This is where https://wiki.gentoo.org/wiki/Preserve-libs comes in handy. I've upgraded icu on my system and still use libreoffice-bin normally. Apart from a message at the end of every emerge, it's really not a problem to wait for an updated version.
(In reply to Emmanuel Vasilakis from comment #21) > This is where https://wiki.gentoo.org/wiki/Preserve-libs comes in handy. > I've upgraded icu on my system and still use libreoffice-bin normally. Apart > from a message at the end of every emerge, it's really not a problem to wait > for an updated version. That's a nice tip that I actually forgot about.
app-office/libreoffice-bin-6.2.4.2 is now in tree.
(In reply to Andreas Sturmlechner from comment #23) > app-office/libreoffice-bin-6.2.4.2 is now in tree. Thank you!!!
Thanks to dilfridge ofc.
Andreas, you are correct, the issue is not "FIXED" properly. Is any better way to resolve it so it won't come back ever again?
