From: Josselin Poiret <dev@jpoiret.xyz>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Efraim Flashner" <efraim@flashner.co.il>,
"Steve George" <steve@futurile.net>,
Kaelyn <kaelyn.alexi@protonmail.com>,
guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Core updates status
Date: Mon, 06 May 2024 10:47:13 +0200 [thread overview]
Message-ID: <87v83r499q.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87o79j7jgm.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi Josselin,
>
> Josselin Poiret <dev@jpoiret.xyz> writes:
>
> [...]
>
>> However, as you can see, these are non-local failures: build failures
>> have to be fixed in a dependency, which incurs a lot of rebuilding.
>> I've fixed a couple of them locally, but here's a nasty one I just got
>> stuck on: curl has a .la file with "-lnettle -lhogweed -lgssapi_krb5",
>> which leads to a build failure for... flatpak :( So fixing this properly
>> would lead to a world rebuild.
>>
>> I'm worried this will keep accumulating a bunch of world rebuilds,
>> slowing down c-u some more. I'd vote to keep the pkgconf switch for
>> later and focus on merging the rest of what c-u has to offer.
>
> I don't mind too much; when we re-enable the change we should add a
> phase to the gnu-build-system automatically deleting/moving the libtool
> archives. so that we're covered.
I agree, although we'll have to be careful since some packages might
need them if they don't use pkg-config!
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2024-05-06 8:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:08 Core updates status Steve George
2024-04-24 9:56 ` Christina O'Donnell
2024-04-24 13:17 ` Steve George
2024-04-24 14:21 ` Christina O'Donnell
2024-04-25 14:06 ` Christina O'Donnell
2024-04-25 14:06 ` bug#40316: " Christina O'Donnell
2024-04-25 17:01 ` nss not reproducible Christina O'Donnell
2024-04-25 18:45 ` Core updates status Kaelyn
2024-04-26 12:56 ` Steve George
2024-04-26 15:58 ` Efraim Flashner
2024-05-05 20:45 ` Josselin Poiret
2024-05-06 2:38 ` Maxim Cournoyer
2024-05-06 8:47 ` Josselin Poiret [this message]
2024-05-06 10:21 ` Ludovic Courtès
2024-05-08 9:03 ` Josselin Poiret
2024-05-08 21:42 ` [PATCH] gnu: glibc: Update patches following upstream's master branch Josselin Poiret
2024-05-14 9:22 ` Ludovic Courtès
2024-05-09 15:41 ` Core updates status Maxim Cournoyer
2024-05-13 8:49 ` Efraim Flashner
2024-05-08 10:05 ` Andreas Enge
2024-05-08 17:46 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-09 15:38 ` Maxim Cournoyer
2024-05-10 8:08 ` Andreas Enge
2024-05-13 8:51 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v83r499q.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.com \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=steve@futurile.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.