all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Phil <phil@beadling.co.uk>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Help to workaround libgit2 fetch refs issue
Date: Fri, 04 Mar 2022 18:43:10 +0100	[thread overview]
Message-ID: <ad59e98f2f95086da1e9788804193df76992cdad.camel@gmail.com> (raw)
In-Reply-To: <875yougixp.fsf@beadling.co.uk>

Am Freitag, dem 04.03.2022 um 09:34 +0000 schrieb Phil:
> Just to add....
> 
> Duplicating of guix-checkout in a private channel has side-effects -
> if anyone has any ideas of how to workaround this, I'd be love to
> discuss... alas, at this point I think I have 3 temporary options:
> 
> 1) Patch in my local Guix and roll my own build of Guix (see below)
> 2) Workaround outside of Guix by cloning the repo for Guix not using
> libgit2
> 3) Tell my CI/CD to continue to build all my PRs twice if the first
> build fails.
> 
> [...]
Again I wonder what the introduction of a new record type solves here.
Wouldn't it be easier to just adapt git-fetch to handle that edge case
and use normal git-references?  Origin methods have network access, so
you can pretty much do whatever.

Cheers


  reply	other threads:[~2022-03-04 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 18:31 Help to workaround libgit2 fetch refs issue Phil
2022-03-02 21:06 ` Liliana Marie Prikler
2022-03-03 18:20   ` Phil
2022-03-04  9:34     ` Phil
2022-03-04 17:43       ` Liliana Marie Prikler [this message]
2022-03-05 11:57         ` Phil
2022-04-30  9:28           ` zimoun

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=ad59e98f2f95086da1e9788804193df76992cdad.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=phil@beadling.co.uk \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.