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 1/6] pkgs/skaware: vendor backported patches
Date: Fri, 26 Jun 2026 15:39:04 +0200	[thread overview]
Message-ID: <87ldc1fmkn.fsf@alyssa.is> (raw)
In-Reply-To: <fe5ebc4b6b171af5955cc4c2f256a1006cd79885.1782409229.git.colby@colbyt.com>

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

colbyt <colby@colbyt.com> writes:

> Two skaware backports were fetched from cgit patch endpoints.  Those
> endpoints are not stable enough for package inputs: the same URL can
> return an unrelated patch, breaking the build before the VM can start.
>
> Keep the small upstream diffs in-tree instead.  The package still
> applies the same s6 and mdevd fixes, and the comments next to each patch
> record the upstream commit IDs.
>
> Signed-off-by: colbyt <colby@colbyt.com>

Yes, it has been unreliable… I looked into it before and it seemed like
it was some sort of overzealous anti-scraper mitigation.  I reported it
but it doesn't seem to have been improved, so something should be done
here.  I prefer not vendoring patches unless absolutely necessary
because experience from Homebrew and Nixpkgs shows they can end up
permanently accumulating quite an impact on repo size over time, but
these repos have an official GitHub mirror, so I'll change to fetching
the patches from there instead.  Thanks!

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

  reply	other threads:[~2026-06-26 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 17:48 [PATCH 0/6] cloud-hypervisor v52 and VM runtime fixes colbyt
2026-06-25 17:48 ` [PATCH 1/6] pkgs/skaware: vendor backported patches colbyt
2026-06-26 13:39   ` Alyssa Ross [this message]
2026-06-25 17:48 ` [PATCH 2/6] pkgs/cloud-hypervisor: update GPU patchset to v52 colbyt
2026-06-26 14:06   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 3/6] vm: use vhost-user networking for crosvm colbyt
2026-06-26 14:45   ` Alyssa Ross
2026-07-02  9:07   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 4/6] Documentation: use crosvm GPU socket-path option colbyt
2026-06-26 14:18   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 5/6] installer: suppress boot console status noise colbyt
2026-06-26 14:46   ` Alyssa Ross
2026-06-26 19:09     ` colby
2026-07-02 11:44       ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 6/6] start-vmm: test GPU socket configuration colbyt
2026-06-26 14:18   ` 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=87ldc1fmkn.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).