This package does not support Python 3.12. Please test it with Python 3.12 as a matter of urgency as the default will change in early June, as per message on gentoo-dev: https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg99104.html. Please check the information provided in the tracker. Ask in #gentoo-python on IRC if need any help.
(In reply to Michał Górny from comment #0) > This package does not support Python 3.12. Please test it with Python 3.12 > as a matter of urgency as the default will change in early June, as per > message on gentoo-dev: > https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg99104.html. > Please check the information provided in the tracker. Ask in #gentoo-python > on IRC if need any help. Can't do that here, unfortunately. Testing needs to be done with the source version. Once 3.12 is default we can rebuild the bin and then it depends on it.
*** Bug 934729 has been marked as a duplicate of this bug. ***
https://www.gentoo.org/support/news-items/2024-05-09-python3-12.html "Please test it with Python 3.12 as a matter of urgency as the default will change in early June" This is now beyond urgent and needs to become priority.
Yes, this needs to be solved quickly. boost 1.85 was marked stable and libreoffice-bin blocks it, because it requires version 1.84. Unfortunately the stabilization of boost must take place at the same time as a newer libreoffice binary.
Well, the other option is just binning it.
(In reply to Andreas Sturmlechner from comment #5) > Well, the other option is just binning it. If you mean compiling it from source, then I already do this in my single strong machine, but I cannot do this in my old laptop which took 2.5 hours for the 4.3 version of Libreoffice. In such cases, of course I prefer to use the binary version available. If you mean something else, please elaborate.
Is not possible to re-use the binary from: https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64/app-office/libreoffice/ to be used as "libreoffice-bin"?
(In reply to Pacho Ramos from comment #7) > Is not possible to re-use the binary from: > https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64/app- > office/libreoffice/ > > to be used as "libreoffice-bin"? I'm afraid not. It pulls all dependencies as binary packages, which are already installed and it seems to be built against boost-1.84.0.
(In reply to Vasilis Lourdas from comment #6) > If you mean something else, please elaborate. Dropping it from ::gentoo, since continued support for producing this -bin version is not possible.
(In reply to Pacho Ramos from comment #7) > Is not possible to re-use the binary from: > https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64/app- > office/libreoffice/ > > to be used as "libreoffice-bin"? I finally got to install it from the binhost repo. So, after a few USE flags changes, it does not want to be rebuilt and it seems to work fine.
Just another feedback that binhost libreoffice works fine. -bin seems kind of redundant and more limited at this point.
(In reply to Shiba from comment #11) > Just another feedback that binhost libreoffice works fine. -bin seems kind > of redundant and more limited at this point. But it will be still needed until: https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart#Preferring_binary_to_source_for_particular_packages is handled :/ But I am not sure if libreoffice-bin ebuild could be adapted to use that binary instead
For me, libreoffice binary from binhost is currently a no-go, because it either ask for : - kde useflag on (with half of the plasma desktop pulled in) - or eds useflag on (evolution-data-server and webkit-gtk). Concerning the binhost binaries, there is 3 different libreoffice binaries on the repo. I do not see the difference between 2 of them. With the following command : > $ grep -A 20 'app-office/libreoffice-24.2.4.2-r1' /var/cache/edb/binhost/mirrors.ircam.fr/pub/gentoo-distfiles/releases/amd64/binpackages/23.0/x86-64/Packages | grep -w 'USE' > USE: abi_x86_64 amd64 bluetooth branding cups dbus eds elibc_glibc gstreamer gtk kernel_linux mariadb python_single_target_python3_12 vulkan > USE: abi_x86_64 amd64 bluetooth branding cups dbus elibc_glibc gtk kde kernel_linux mariadb python_single_target_python3_12 vulkan > USE: abi_x86_64 amd64 bluetooth branding cups dbus eds elibc_glibc gstreamer gtk kernel_linux mariadb python_single_target_python3_12 vulkan > Package 2 is with kde useflag on. Package 1 and 3 are with eds useflag on. But you can also see that package 1 and 3 are built with exactly the same useflags. Why ? what is the difference between these two binaries ? Would it be possible to build a binary without gnome nor plasma/kde support for all small desktops ? Thank you.
(In reply to Fab from comment #13) > - kde useflag on (with half of the plasma desktop pulled in) There is not a single Plasma desktop package being pulled in. KF6 libs, yes.
Created attachment 899676 [details] emerge --getbinpkg output (In reply to Andreas Sturmlechner from comment #14) > (In reply to Fab from comment #13) > > - kde useflag on (with half of the plasma desktop pulled in) > There is not a single Plasma desktop package being pulled in. KF6 libs, yes. Sorry, I never used plasma nor kde, from my external point of view I admit that I do not know the difference. But please have a look at the attached emerge output and all these packages from kde-frameworks category. Wanting to install a binary package from binhost does not mean that I want to install all its dependencies also from binhost with eyes closed.
We should focus back on app-office/libreoffice-bin needing an upgrade.
7.6.7.2 was just added to ::gentoo.
