all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: 59196@debbugs.gnu.org
Subject: bug#59196: guix pull fails on A20-OlinuXino-LIME2-eMMC
Date: Wed, 16 Nov 2022 04:17:15 +0100	[thread overview]
Message-ID: <20221116041715.3633eee7@primary_laptop> (raw)
In-Reply-To: <166841242191.18688.11635928554710611383@localhost>

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

Hi,

I've found an idea: guix pull can pull to a precise commit:
>       --commit=COMMIT    download the specified "guix" channel COMMIT

So maybe it works with a commit close to Guix 1.3. If that's the case
we can probably bisect it to the commit that broke your guix pull.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-16  3:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 17:53 bug#59196: `guix pull` fails on A20-OLinuXino-LIME2-eMMC Tanguy LE CARROUR
2022-11-12 15:40 ` bug#59196: guix pull fails on A20-OlinuXino-LIME2-eMMC Denis 'GNUtoo' Carikli
2022-11-13 10:48 ` Tanguy LE CARROUR
2022-11-13 20:54   ` Denis 'GNUtoo' Carikli
2022-11-14  7:53     ` Tanguy LE CARROUR
2022-11-14 22:44       ` Denis 'GNUtoo' Carikli
2022-11-16  3:17       ` Denis 'GNUtoo' Carikli [this message]
2022-11-16  8:13         ` Tanguy LE CARROUR
2022-11-16 15:09           ` Tanguy LE CARROUR
2024-09-10 15:44 ` bug#59196: `guix pull` fails on A20-OLinuXino-LIME2-eMMC Simon Tournier
2024-09-12  6:33   ` Tanguy LE CARROUR
2024-09-20 16:22     ` Simon Tournier
2024-11-27  8:46       ` Update on " Tanguy LE CARROUR
2024-11-27  9:25       ` bug#59196: " Tanguy LE CARROUR
2024-11-27 11:20         ` Julien Lepiller
2024-11-27 11:51           ` Tanguy LE CARROUR
2024-11-27 17:43             ` Tanguy LE CARROUR
2024-11-27 21:13               ` Julien Lepiller

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=20221116041715.3633eee7@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=59196@debbugs.gnu.org \
    --cc=tanguy@bioneland.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 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.