unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: Julien Lepiller <julien@lepiller.eu>,
	guix-devel@gnu.org, janneke@gnu.org
Subject: Re: Merging core-updates?
Date: Sun, 12 Feb 2023 18:29:04 +0000	[thread overview]
Message-ID: <Q64KtPEpi0BNnW2-LrDhCglH5mNp6dhwx0OBdmRQ5goTqo-LRKfXtuOdbIOO8HDRZ8koMtQaTMR7JreGE9FAaL9K7wWzcoIDH1BAzj8aPaw=@protonmail.com> (raw)
In-Reply-To: <Y+kdJYB1F2tm0Slf@jurong>

Hi,

------- Original Message -------
On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge <andreas@enge.fr> wrote:

>
>
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>
> > And I was able to rebuild (with --check) patch-mesboot. The error looks
> > a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
> > :)
>
>
> Ah indeed, that looks like deal breaking; maybe someone from MES can have
> a look?
>
> What is the magic incantation with double "@@" to build this package?
> Ah, here we go, for reference to self:
> guix build -e '(@@ (gnu packages commencement) patch-mesboot)'
>
> Andreas

While not directly related to the patch-mesboot error, I want to mention that there is also https://issues.guix.gnu.org/58719 blocking i686 builds on core-updates (and x86_64 builds of certain packages like wine64, which has i686 dependencies) since the update to glibc 2.35.

It may also need assistance from the MES folks to fix, since the error message is about an undefined symbol in glibc-mesboot's libpthread.so.0:

make[2]: Entering directory '/tmp/guix-build-file-5.44.drv-0/file-5.44/magic'
../src/file -C -m magic
/tmp/guix-build-file-5.44.drv-0/file-5.44/src/.libs/file: symbol lookup error: /gnu/store/s4yd6ibxsh5q1j9ipygb9vpjj4g00wc9-glibc-mesboot-2.16.0/lib/libpthread.so.0: undefined symbol: h_errno, version GLIBC_PRIVATE
make[2]: *** [Makefile:863: magic.mgc] Error 127

Cheers,
Kaelyn


P.S. I also have https://issues.guix.gnu.org/59453 open for few months to fix the Vulkan layer paths in mesa on core-updates, which I'd really like to see land before a core-updates merge happens (it had originally been part of a mesa version update patch I sent in back in October, but which had been obsoleted by a newer patch release of mesa landing in core-updates; mesa in core-updates is also a few releases behind at this point, but that's a separate matter).


  reply	other threads:[~2023-02-12 18:29 UTC|newest]

Thread overview: 124+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12  9:05 Merging core-updates? Julien Lepiller
2023-02-12 11:06 ` Andreas Enge
2023-02-12 11:52   ` Julien Lepiller
2023-02-12 11:58     ` Julien Lepiller
2023-02-12 13:05       ` Christopher Baines
2023-02-20 11:10         ` Christopher Baines
2023-02-12 17:08       ` Andreas Enge
2023-02-12 18:29         ` Kaelyn [this message]
2023-02-13 20:04           ` Efraim Flashner
2023-02-13 21:36             ` Kaelyn
2023-02-14 14:50               ` Efraim Flashner
2023-02-14 20:29                 ` Kaelyn
2023-02-15  0:07                   ` Kaelyn
2023-02-12 18:40         ` Janneke Nieuwenhuizen
2023-02-13 11:34         ` Janneke Nieuwenhuizen
2023-02-13 13:57           ` Andreas Enge
2023-02-15  8:39             ` Janneke Nieuwenhuizen
2023-02-16 14:19               ` Andreas Enge
2023-02-16 15:03                 ` bug#49985: " Janneke Nieuwenhuizen
2023-02-16 15:24                   ` Andreas Enge
2023-02-16 15:33                   ` Julien Lepiller
2023-02-12 14:49   ` Josselin Poiret
2023-02-13  3:05     ` John Kehayias
2023-02-12 12:02 ` Leo Famulari
2023-02-21 23:01   ` Ludovic Courtès
2023-02-12 13:28 ` Christopher Baines
2023-03-05 19:52   ` Christopher Baines
2023-03-05 22:18     ` Merging core-updates? OFF TOPIC PRAISE Joshua Branson
2023-02-12 15:51 ` Merging core-updates? Efraim Flashner
2023-02-13 16:40   ` Katherine Cox-Buday
2023-02-13 17:11     ` John Kehayias
2023-02-13 20:22   ` Andreas Enge
2023-02-13 20:38     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-13  9:43 ` zimoun
2023-02-13 10:56   ` Architecture support [was: Re: Merging core-updates?] Efraim Flashner
2023-02-13 12:59     ` Architecture support Andreas Enge
2023-02-14 16:30     ` Architecture support [was: Re: Merging core-updates?] Andreas Enge
2023-02-14 16:40       ` Julien Lepiller
2023-02-15  9:45         ` Architecture support Andreas Enge
2023-02-17 16:49         ` Architecture support [was: Re: Merging core-updates?] Christopher Baines
2023-02-19 22:50           ` Architecture support Andreas Enge
2023-02-20  9:23             ` Christopher Baines
2023-02-14 20:10       ` Architecture support [was: Re: Merging core-updates?] Efraim Flashner
2023-02-15  9:35         ` Andreas Enge
2023-02-13 20:35 ` Merging core-updates? Andreas Enge
2023-02-13 21:31   ` Efraim Flashner
2023-02-14 18:27     ` Andreas Enge
2023-02-15 18:51       ` Andreas Enge
2023-02-15 19:19         ` Openjdk (was: Merging core-updates?) Andreas Enge
2023-02-16 11:03           ` Efraim Flashner
2023-02-16 11:38             ` Julien Lepiller
2023-02-18 11:28               ` Andreas Enge
2023-02-17 10:36             ` Andreas Enge
2023-02-17 14:49             ` Andreas Enge
2023-02-17 16:28               ` Andreas Enge
2023-02-17 17:27                 ` Kaelyn
2023-02-18 10:55                   ` Andreas Enge
2023-02-16 11:41         ` Merging core-updates? Maxime Devos
2023-02-16 16:03           ` Andreas Enge
2023-02-18 11:03   ` Ocaml (was: Merging core-updates?) Andreas Enge
2023-02-18 11:38     ` Andreas Enge
2023-02-19  9:15       ` Julien Lepiller
2023-02-20 10:35         ` Simon Tournier
2023-02-20 11:16           ` Julien Lepiller
2023-02-20 11:55             ` Ocaml Andreas Enge
2023-02-19 11:02   ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 11:15     ` Andreas Enge
2023-02-19 11:19       ` Andreas Enge
2023-02-19 15:10         ` Attila Lendvai
2023-02-21 16:24           ` Python Andreas Enge
2023-02-19 11:30     ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 20:31       ` Python Andreas Enge
2023-02-21 16:41         ` Python Andreas Enge
2023-02-22 14:23           ` Python Andreas Enge
2023-02-23 15:16           ` Python Andreas Enge
2023-02-24 16:47             ` Python Andreas Enge
2023-02-24 16:51               ` Python Andreas Enge
2023-02-24 18:08               ` Python Lars-Dominik Braun
2023-02-25 15:15                 ` Python Andreas Enge
2023-02-25 15:45                   ` Python Lars-Dominik Braun
2023-02-25 16:39                     ` Python Andreas Enge
2023-02-25 16:56                       ` Python Lars-Dominik Braun
2023-02-25 18:00                         ` Python Andreas Enge
2023-02-25 18:06                           ` Python Andreas Enge
2023-02-25 18:15                             ` Python Andreas Enge
2023-02-25 18:33                               ` Python Andreas Enge
2023-02-27 19:14                                 ` Python Lars-Dominik Braun
2023-02-28 15:05                                   ` Python Andreas Enge
2023-02-25 18:29                           ` Python Andreas Enge
2023-03-11 11:20                           ` Python Andreas Enge
2023-03-11 11:44                             ` Python Andreas Enge
2023-03-15 13:49                         ` Python Andreas Enge
2023-03-18  8:59                           ` Python Lars-Dominik Braun
2023-03-18  9:15                             ` Python Andreas Enge
2023-03-18 10:02                               ` Python Lars-Dominik Braun
2023-03-18 10:13                                 ` Python Andreas Enge
2023-03-18  9:43                           ` Python Lars-Dominik Braun
2023-03-18 19:37                             ` Python Andreas Enge
2023-03-21 18:56                               ` Python Lars-Dominik Braun
2023-03-30  9:57                                 ` Python Lars-Dominik Braun
2023-03-30 10:10                                   ` Python Andreas Enge
2023-04-03 17:29                                   ` PyQt in core-updates Andreas Enge
2023-04-04  7:55                                     ` Lars-Dominik Braun
2023-04-17  8:32                                       ` Andreas Enge
2023-03-30 11:05                               ` Python Lars-Dominik Braun
2023-03-31  8:52                                 ` Python Andreas Enge
2023-02-27 18:55                 ` Python Efraim Flashner
2023-02-27 19:12                   ` Python Lars-Dominik Braun
2023-02-21 16:50       ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 11:47     ` Lars-Dominik Braun
2023-02-19 11:57       ` Andreas Enge
2023-02-19 15:50         ` Lars-Dominik Braun
2023-02-19 20:27           ` Python Andreas Enge
2023-02-25 17:44             ` Python Andreas Enge
2023-02-19 21:35           ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 22:08           ` Andreas Enge
2023-02-19 22:59             ` Kaelyn
2023-02-21 16:18               ` Andreas Enge
2023-02-19 19:55         ` Andreas Enge
2023-02-19 11:48     ` Andreas Enge
2023-02-19 22:24     ` Andreas Enge
2023-02-21 16:58       ` Andreas Enge
2023-02-22  9:40         ` Icecat (was: Python) Andreas Enge
2023-02-16 20:11 ` Merging core-updates? Josselin Poiret

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='Q64KtPEpi0BNnW2-LrDhCglH5mNp6dhwx0OBdmRQ5goTqo-LRKfXtuOdbIOO8HDRZ8koMtQaTMR7JreGE9FAaL9K7wWzcoIDH1BAzj8aPaw=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.org \
    --cc=julien@lepiller.eu \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).