From: Alyssa Ross <hi@alyssa.is>
To: Yureka <yuka@yuka.dev>, devel@spectrum-os.org
Subject: Re: Build failures against staging
Date: Sat, 11 Oct 2025 14:09:48 +0200 [thread overview]
Message-ID: <87h5w5iqr7.fsf@alyssa.is> (raw)
In-Reply-To: <82249ddc-ae1a-4e3a-a6ae-bb4717243fca@yuka.dev>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Yureka <yuka@yuka.dev> writes:
> Hello everyone,
>
>
> I attempted to build a spectrum (rev.
> c5d5786d3dc938af0b279c542d1e43bce381b4b9) image against nixpkgs staging
> (rev eb681f8139a93020f51b8256fc7dfe057b44747f) on x86_64. Here are the
> derivations which failed to build, for further investigation:
>
> - /nix/store/cbjmszj7r5r0abka3jsr6pijxba0sd2q-iproute2-6.17.0.drv
> (pkgsMusl.iproute2)
> -
> /nix/store/f1cc5abbfjslqvy6wkzrzsmsjj4hpk6h-openssl-static-x86_64-unknown-linux-musl-3.6.0.drv
> (pkgsStatic.openssl)
>
> The following also fail, but seem to have no specific connection
> spectrum or pkgsMusl/pkgsStatic (the GNU counterparts are broken on
> staging with the same error):
>
> - /nix/store/g0bklsp2daxxq74pkb3mqjcrb919194i-python3.13-inkex-1.4.2.drv
> (python3.pkgs.inkex)
> -
> /nix/store/nfwcjnbp6rv4cgzrxdqljc1k1h72z3kk-python3.13-cryptography-vectors-46.0.1.drv
> (python3.pkgs.cryptography.vectors)
> -
> /nix/store/36674wi2rkanm2ds2bx1183w7knj9mr0-wasilibc-static-wasm32-unknown-wasi-27.drv
> (pkgsCross.wasi32.stdenv.cc.libc, needed for firefox)
>
>
> I hope this is useful to catch any problems affecting spectrum before
> the following staging-next cycle.
Very useful, thank you! Would be nice to spread this work out some
more. :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-10-11 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 10:57 Build failures against staging Yureka
2025-10-11 12:09 ` Alyssa Ross [this message]
2025-10-12 22:05 ` Yureka
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=87h5w5iqr7.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).