[core-updates] libetonyek link failure

  • Done
  • quality assurance status badge
Details
One participant
  • Leo Famulari
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 10 Jul 19:33 +0200
(address . bug-guix@gnu.org)
Zo7F4tyBAbUcGAfM@jasmine.lan
Attachment: file
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEaEByLu7k06ZO5T6saqwZY3V/R/8FAmaOxdsACgkQaqwZY3V/
R/8hdxAApR35pSitgGfFmzshsrNTXDx+oaX13RbSCpGPAIYhhOeNgsiBRW0me7jy
IvI1+uKivR9Ve0a/zxoOVi5TT3HNXIIaKwt7WEXbeg9zRyxyyIOoNHsDerM97hG6
jZYyZ4u0N08yE7upFoKm1HijNjNPCZZ8+UuL8Ahif1wMK0VgwpOtKUm2b/wI927H
3UVrEpY0XCozF16/b8BVrB/KTSJiB9m/efPb0DYatVCwWif42KhddVAzqRbeXPWv
7khqUcqUP9y2fKaBF8NYbIRnQ6Nz0dM4w9AMdHrCUC+WLNqqnp9cHX0UHdQX0W0p
JG4sZoxi/4+QVpxnjrH/F5446az+nacYlULrwWiepeMYMTuV/7F1980SEpPBm2eR
ipeLr8zqrhNnct0r8ybbdmZRLoGjehQ0sqfYTtjvq2Dpw3axdltHhZ5cvm3rHjTS
4wBpIbfJCTDzAhRLLre34Vlb9Jz6iPfqR9G6OlvH3CsLtEQZL4XLphb2wyMddKvP
Xszpw8hJFU/H8zhEF5kqxXd/x+vITv7JPrO486O4RWP2OogKVqtaReV8TYoXX3d5
NjlpwwzG7Fu4GQSIJVQKMr8hTb2LXoMgB7SVhSF6eoNhsd4a531EiA4xn3xyARy7
631NMD6cKJ4esV+i9JYdfWOGNJLVOSck2KyY5kvLIGdAD83+zxc=
=gRBM
-----END PGP SIGNATURE-----


L
L
L
Leo Famulari wrote on 11 Jul 18:41 +0200
Re: [core-updates] libetonyek link failure
(address . 72040@debbugs.gnu.org)
ZpALK_SmftBH4zx2@jasmine.lan
On Thu, Jul 11, 2024 at 12:00:56PM -0400, Leo Famulari wrote:
Toggle quote (5 lines)
> I think this upstream report (closed without resolution) describes the
> problem:
>
> https://bugs.documentfoundation.org/show_bug.cgi?id=152569

I sent a report to the mailing list where build failures are supposed to
be reported:


It hasn't shown up yet, presumably being hold for moderation. I'll link
to it here when it appears.
L
L
Leo Famulari wrote on 11 Jul 21:15 +0200
Re: [core-updates] Boost bug / breaks libreoffice [was libetonyek link failure]
(address . 72040@debbugs.gnu.org)
ZpAvTzbPknFQT7x5@jasmine.lan
I found the bug report, which is for Boost:


Basically, versions 1.81 through 1.83 exhibit this defect.

I'm testing a patch for Boost now. It will cause a huge number of
rebuilds, so it would be great to come up with another approach.
L
L
Leo Famulari wrote on 11 Jul 22:23 +0200
(address . 72040@debbugs.gnu.org)
ZpA_Leh5av2htGYT@jasmine.lan
On Thu, Jul 11, 2024 at 03:15:27PM -0400, Leo Famulari wrote:
Toggle quote (3 lines)
> I'm testing a patch for Boost now. It will cause a huge number of
> rebuilds, so it would be great to come up with another approach.

Here's a patch that patches Boost, while also creating a hidden package
boost-for-source-highlight. This variant is only used by the
source-highlight package, which is used by gdb, and thus rust. So, it
aims to avoid rebuilding everything rust.

I'm testing it now.

Any thoughts?
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEaEByLu7k06ZO5T6saqwZY3V/R/8FAmaQPyUACgkQaqwZY3V/
R/+NOhAApU8xGgGA1SXw+mBc2bf1+A0SQ89hUMDj+w5M1EKkBUeZ+U6TvHlMzxvt
Sw72knzxBmCJDks+lFKaiZodhjpQuPowiDZ+q4uYIyIs7EFIqVj1j0tFzdQ0ffV8
qVx87JIZowoVg4LMhMYerYUnTfpBqC/DqvOmmILdFlgFxn3L9wbhvMjP07bEZKO1
t5JYGVf8t0n61EClyarc32lPTB1UwPqERkD7OU8lqWaG5EYtM7a5iSF5zjlZ3I9k
KgEUzdb3ZjbMjDOM6sXUUPQe1iULRtyyZ9dy9tg2ufezrKL52xwl84euGerXGCiI
WPLxocCOh51/tPojl9XBpGPU5/CISi5wlskUXa+2Bz7dCwqY1GF+SsZoKVRUyAvm
uMzVRJOcKV4LirYIM4E/tEMdxtIxc/C0I+Tjmgs3Hd2pV9aBKWk+BpRHNUxR4UOc
uFlz8lDaFJ89pYGI3B98Aq7KJPUTTFCJ2stoALBBNxbAlHnIZfHsOPld5d4Cxe35
FbPSCSvngk6NXjuCFEmfJUW+PTPcWKuB94J6SdQtYNUmKyyC1zbFFtbHsyRickcF
3Fk+2RS77AnGY2wBHUDZPJNgHIWCzeLuGmH2oF0ikYXcJVSwHisSg3OWOlnEwyuq
3fzZ2T074PFIjXoO30J4pwpyv0hm1HEAUgi+L1tpElaZkH0kWvg=
=NvPy
-----END PGP SIGNATURE-----


L
L
Leo Famulari wrote on 13 Jul 19:39 +0200
(address . 72040@debbugs.gnu.org)
ZpK7yfHwapBPlkaM@jasmine.lan
On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
Toggle quote (5 lines)
> Here's a patch that patches Boost, while also creating a hidden package
> boost-for-source-highlight. This variant is only used by the
> source-highlight package, which is used by gdb, and thus rust. So, it
> aims to avoid rebuilding everything rust.

Here's an updated patchset that builds on the previous patch.

It patches Boost to fix the bug, creates the Boost variant for
source-highlight / gdb / Rust, and then finally fixes a missing
dependency failure in Libreoffice.

It does cause several thousand rebuilds (5933 rebuilds), but much fewer than if we did
not avoid changing the source-highlight derivation (15383 rebuilds).

There is some discussion on the Libreoffice mailing list, but so far
it's inconclusive from my perspective. But if I understand correctly,
their recommended solution would be to create a source origin of
Boost >=1.84, copy that into the Libreoffice and libetonyek source
trees, and build the programs against that "internal" Boost. I'm not
sure that's better than simply updating Boost.
L
L
Leo Famulari wrote on 13 Jul 19:40 +0200
(address . 72040@debbugs.gnu.org)
ZpK78nE9v4EfB9z3@jasmine.lan
On Sat, Jul 13, 2024 at 01:39:21PM -0400, Leo Famulari wrote:
Toggle quote (7 lines)
> There is some discussion on the Libreoffice mailing list, but so far
> it's inconclusive from my perspective. But if I understand correctly,
> their recommended solution would be to create a source origin of
> Boost >=1.84, copy that into the Libreoffice and libetonyek source
> trees, and build the programs against that "internal" Boost. I'm not
> sure that's better than simply updating Boost.

I forgot, here is the link to the discussion on their mailing list:

L
L
Leo Famulari wrote on 24 Jul 23:48 +0200
(address . 72040-done@debbugs.gnu.org)
ZqF2nFjdbKNQl_-Z@jasmine.lan
On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote:
Toggle quote (11 lines)
> Subject: [PATCH] WIP: Boost: Fix a bug that breaks libetonyek.
>
> This fixes <https://issues.guix.gnu.org/72040>
>
> * gnu/packages/patches/boost-fix-duplicate-definitions-bug.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/boost.scm (boost)[source]: Use it.
> (boost-for-source-highlight): New variable, not using the patch.
> * gnu/packages/pretty-print.scm (source-highlight)[inputs]: Replace BOOST with
> BOOST-FOR-SOURCE-HIGHLIGHT.

Pushed as 1ab3e3b26fdc43d48826119d4f51379571dd89b6 along with a followup
patch that fixes another problem with Libreoffice. With these changes,
we have Libreoffice on core-updates.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEaEByLu7k06ZO5T6saqwZY3V/R/8FAmahdpsACgkQaqwZY3V/
R//3sQ//VZFK2loz4hgmMMOJynH1beV2XuWRVaOphTDuU+r9FuGt31uKN5OqWUoU
CXuKeW1PSY3Nq/xv52y+hVQCt9IKaa6+d0J5NRCDdnWwv6jxJ+QuuR8YbNIk1hG2
uCPURER8j1vRHsIvkQZtZquW8Wm83GFNhXmYJru9uPc8mELOR9o2sQx2j4WZq1zt
fE0JcP9wUbKn5Ny09Bz/Fn8YIPeHpHU4dMC8hg0l3C+3slAzA0+BSCJDXnTWkZOp
raioldJXsAr6pqt2hsLYV1i8AF4FoDnfXGqbJe5090W+vlewdd5FqdQfP3iyKX7r
8a6wFBymBGOHAR5ykIGptD6rxu5QM+qyPNOQg05PEROefU9WVDMdBnzBJV5n+p1x
BqP5TS4Vb1/qGM9xeg1v0XG7HVU4/DQe95qNkkorpfqqLcedVorxcHoSl1Qs4v5W
gppXxA3iDFDcKsT6bFBHHUbbLcgDABzLY67jAxsQCx8ZGq8opXSIB0QBIjXgVvff
wu5bXSO06LdlKYnZcU6uu0uz1Ue3h4AGIKDa5TP5mm91sAYh1F90LvVeHSjtUw+H
Fx43iK0zi2QF/B+PDefSmFYiwLQbq2gMFOVxwKgUCcmptXX8nnFBE1ETlPSKyiQ7
uG1qwJplCFBdMy9LL0fi5QSIIQ+aO6yY65VaaWP+6cojniVbCRE=
=Mxx8
-----END PGP SIGNATURE-----


Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 72040@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 72040
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch