patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Yureka <yuka@yuka.dev>, devel@spectrum-os.org
Subject: Re: Nixpkgs updates
Date: Mon, 09 Feb 2026 20:41:16 +0100	[thread overview]
Message-ID: <87zf5hvh5v.fsf@alyssa.is> (raw)
In-Reply-To: <16bef820-e5b5-45f3-8583-a1a652dbcc6c@gmail.com>

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

Demi Marie Obenour <demiobenour@gmail.com> writes:

> On 2/9/26 03:02, Yureka wrote:
>> 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
>
> Can those be removed from the closure somehow?

I'm pretty sure I answered a very similar question last time, but just
in case: it would likely be more ongoing maintenance work to maintain
closure reducing overrides than it would be to fix the occasional build
failure of a dependency that is not strictly required, at least until we
have better tooling for identifying problematic Nixpkgs changes.  In
addition, that larger amount of work would have less overall utility,
because package fixes benefit other Nixpkgs users, whereas adding to an
ever-expanding list of local overrides does not.

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

  reply	other threads:[~2026-02-09 19:41 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 [this message]
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

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=87zf5hvh5v.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --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).