all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>
Cc: 50026@debbugs.gnu.org
Subject: bug#50026: Specify a pull-request in --with-branch package transformations
Date: Tue, 14 Sep 2021 09:43:54 +0200	[thread overview]
Message-ID: <877dfj8uv9.fsf@gnu.org> (raw)
In-Reply-To: <29e470a4-89a3-2ac1-1fbd-f4a747443fb9@inria.fr> (Philippe SWARTVAGHER's message of "Thu, 12 Aug 2021 11:38:38 +0200")

Hi!

Philippe SWARTVAGHER <philippe.swartvagher@inria.fr> skribis:

> guix build chameleon --with-branch=chameleon=merge-requests/262/head
>
> ```
>
> (with 262 being the pull-request I'm interested in) However, this fails:
>
> ```
>
> guix build: erreur : impossible de récupérer la branche «
> merge-requests/262/head » depuis
> https://gitlab.inria.fr/solverstack/chameleon : cannot locate
> remote-tracking branch 'origin/merge-requests/262/head'
> ```
>
> While commands stated in the documentation work well:
>
> ```bash
>
> git clone https://gitlab.inria.fr/solverstack/chameleon && cd chameleon
>
> git fetch origin merge-requests/262/head:mr-262
>
> git checkout mr-262

Any idea what makes this branches “special” from a Git viewpoint?

Guix uses libgit2 (via Guile-Git); perhaps there’s a feature here that
libgit2 doesn’t support, or perhaps there’s an additional step to make
to make those branches visible?

Thanks,
Ludo’.




  parent reply	other threads:[~2021-09-14  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  9:38 bug#50026: Specify a pull-request in --with-branch package transformations Philippe SWARTVAGHER
2021-08-12 15:30 ` raingloom
2021-08-12 20:06   ` Philippe SWARTVAGHER
2021-09-14  7:43 ` Ludovic Courtès [this message]
2021-09-14  8:12   ` 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=877dfj8uv9.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=50026@debbugs.gnu.org \
    --cc=philippe.swartvagher@inria.fr \
    /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.