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: The upcoming nixpkgs staging cycle
Date: Mon, 15 Dec 2025 16:05:57 +0100	[thread overview]
Message-ID: <87ldj3lr8q.fsf@alyssa.is> (raw)
In-Reply-To: <77e3c2c6-7d23-432e-b1b1-655a9b1e3d1d@gmail.com>

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

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

> On 12/15/25 03:50, Yureka wrote:
>> Hi,
>> 
>> 
>> I attempted running the spectrum release checks on nixpkgs staging 
>> commit dc05cdb0ced63fee5124d22a5cc43a0eab3a23bb.
>> 
>> I found the following build failures (all from the default 
>> glibc/non-cross package set) and reported them upstream:
>> 
>> https://github.com/NixOS/nixpkgs/issues/470961
>> https://github.com/NixOS/nixpkgs/issues/470962
>> https://github.com/NixOS/nixpkgs/issues/470964
>
> Would it make sense to somehow remove those from Spectrum's dependency
> tree?  I don't think any of these are things that Spectrum actually
> needs.
>
> That might be a larger de-bloating effort, though.  There is no
> need to have NetworkManager when the kernel will eventually have IP
> networking support removed!

As we've discussed before, changing lots of package options to remove
dependencies will have a huge ongoing maintenance cost.  I would
therefore like to wait until we have better tooling for dealing with
Nixpkgs regressions before we start doing this.

(Yureka monitoring staging is a good step in this direction though!)

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

      reply	other threads:[~2025-12-15 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15  8:50 The upcoming nixpkgs staging cycle Yureka
2025-12-15  8:53 ` Demi Marie Obenour
2025-12-15 15:05   ` 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=87ldj3lr8q.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).