From: Alyssa Ross <hi@alyssa.is>
To: Yureka <yuka@yuka.dev>
Cc: devel@spectrum-os.org
Subject: Re: Nixpkgs updates
Date: Sun, 22 Feb 2026 12:30:49 +0100 [thread overview]
Message-ID: <87fr6t582e.fsf@alyssa.is> (raw)
In-Reply-To: <17b1e489-dc82-4c8b-9914-498019b69a41@yuka.dev>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
Yureka <yuka@yuka.dev> writes:
> My systems attempted to build a spectrum image against nixpkgs master
> last night, and failed because of pkgsMusl.netpbm and pkgsMusl.gdb,
> which are known blockers since the GCC 15 updates:
>
> https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue%20state%3Aopen%20author%3Ayuyuyureka
Thanks! I looked into both of these. Proposed a fix to netpbm in
Nixpkgs[1], but for gdb we should probably wait for a second submission
of this patch[2], since the current version relying on Glibc-internal
macros in not great. A second gdb patch[3] is also necessary for
aarch64, which looks fine to apply whenever we're ready.
I've added all these patches to the upstream bug/patch tracking
board[4]. Send me a contact request on there if you want write access. :)
[1]: https://github.com/NixOS/nixpkgs/pull/492997
[2]: https://inbox.sourceware.org/gdb-patches/20260213152151.3224544-1-sunilkumar.dora@windriver.com/
[3]: https://inbox.sourceware.org/gdb-patches/20260217060106.1906312-5-thiago.bauermann@linaro.org/
[4]: https://cryptpad.fr/kanban/#/2/kanban/view/yLtGXWLV6U7X5+Z1ay+oXKZMrSacqQe+51nXZYRh3ck/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2026-02-22 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 8:02 Nixpkgs updates Yureka
2026-02-09 19:34 ` Demi Marie Obenour
2026-02-09 19:41 ` Alyssa Ross
2026-02-22 14:25 ` Demi Marie Obenour
2026-02-23 11:28 ` Alyssa Ross
2026-02-23 15:58 ` Demi Marie Obenour
2026-02-22 11:30 ` Alyssa Ross [this message]
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=87fr6t582e.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.org \
--cc=yuka@yuka.dev \
/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://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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 NNTP newsgroup(s).