patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: colbyt <colby@colbyt.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 0/8] refresh nixpkgs for Linux 7.1
Date: Thu, 02 Jul 2026 14:03:06 +0200	[thread overview]
Message-ID: <87v7axwqdh.fsf@alyssa.is> (raw)
In-Reply-To: <20260626185509.3715326-1-colby@colbyt.com>

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

colbyt <colby@colbyt.com> writes:

> This series moves the default nixpkgs pin forward and fixes the build
> and runtime issues exposed on the generic Spectrum path. It lets the
> generic images follow linux_latest, which currently selects Linux 7.1.1.
>
> The changes are split by cause: aarch64-musl build fixes exposed by the
> pin bump, integrated skaware and GTK backports, Cloud Hypervisor 52.0
> with the local vhost-user GPU patchset rebased, the libfyaml pkg-config
> cleanup needed by AppStream, and the app VM closure-root fix for foot
> and Firefox.
>
> The Cloud Hypervisor update includes the crosvm SHMEM_MAP compatibility
> needed by the current crosvm GPU backend.

I have an update to current Nixpkgs staging-next in the work, that
should be ready to commit as soon as the staging cycle completes and
Nixpkgs unstable updates.  staging-next currently contains a lot of
fixes that aren't in unstable, so by waiting a week or so for it we can
avoid the need for a lot of downstream workarounds.  I'll post the patch
soon so you can try it out in advance, if you want.  (Eventually we need
to not be going months without updating, but while it's been so long I
think waiting an extra week or so is okay, and I promise the gap was
because other good things were happening — I just can't say what they
might have been yet. ;))  So with that in mind I will pass on the update
patches, but I'll still try to go through and review, because I
think there's educational value to that.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2026-07-02 12:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 18:55 [PATCH 0/8] refresh nixpkgs for Linux 7.1 colbyt
2026-06-26 18:55 ` [PATCH 1/8] pkgs: fix aarch64-musl builds with current nixpkgs colbyt
2026-07-02 12:18   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 2/8] lib: update nixpkgs colbyt
2026-06-26 18:55 ` [PATCH 3/8] pkgs/skaware: vendor backported patches colbyt
2026-07-02 11:53   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 4/8] pkgs/gtk3: skip integrated Wayland backport colbyt
2026-07-02 12:19   ` Alyssa Ross
2026-06-26 18:55 ` [PATCH 5/8] pkgs/skaware: skip integrated backports colbyt
2026-06-26 18:55 ` [PATCH 6/8] pkgs/cloud-hypervisor: update GPU patchset to v52 colbyt
2026-06-26 18:55 ` [PATCH 7/8] pkgs/libfyaml: fix pkg-config libs colbyt
2026-06-26 18:55 ` [PATCH 8/8] vm-lib: allow app VMs to name closure roots colbyt
2026-07-02 13:38   ` Alyssa Ross
2026-07-02 23:40     ` colby
2026-07-03 14:02       ` Alyssa Ross
2026-06-26 18:55 ` [PATCH optional] linux: use 6.18 for generic images colbyt
2026-07-02 13:42   ` Alyssa Ross
2026-07-02 23:20     ` colby
2026-07-02 12:03 ` 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=87v7axwqdh.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=colby@colbyt.com \
    --cc=devel@spectrum-os.org \
    /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).