unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Gabriel Wicki <gabriel@erlikon.ch>, help-guix@gnu.org
Subject: Re: Unable to get rid of guix-past (and unable to pull)
Date: Fri, 29 Nov 2024 16:58:39 +0100	[thread overview]
Message-ID: <87ldx2dob4.fsf@gmail.com> (raw)
In-Reply-To: <5u3qwx5ayacksgd53gdkduh5lu4dhf2ttevo4dawcxb6a5yw4f@orqygvibt27q>

Hi,

On Thu, 28 Nov 2024 at 00:28, Gabriel Wicki <gabriel@erlikon.ch> wrote:

>     guix pull: error: aborting update of channel 'guix-past' to commit f99ada4123de1eadf668d34dac2d726407634549, which is not a descendant of 5fb77cce01f21a03b8f5a9c873067691cf09d057

[...]

>     guix-past 5fb77cc
>         repository URL: https://gitlab.inria.fr/guix-hpc/guix-past
>         branch: master
>         commit: 5fb77cce01f21a03b8f5a9c873067691cf09d057

Ouch!  That because Ludo pushed commit [1]
5fb77cce01f21a03b8f5a9c873067691cf09d057 to
https://gitlab.inria.fr/guix-hpc/guix-past but not to
https://codeberg.org/guix-science/guix-past.

In the meantime, you pulled and thus you get this 5fb77cc because it was
still the reference of the old location (inria).  Then you pulled again
but this time using the new location (codeberg).  And bang!

Somehow, that’s a migration typo. :-)  And we cannot do more now it’s
done.

1: https://gitlab.inria.fr/guix-hpc/guix-past/-/commits/master/?ref_type=HEADS

> Needless to say, `guix-past' is (seemingly) defined nowhere on my
> system.

As explained, it is indirectly pulled via guix-gaming-channels [2].

In other words, the scenario reads:

 1. Migration of guix-past from Inria to Codeberg
 2. 5fb77cc pushed to guix-past Inria
 3. guix-gaming-channels had not yet updated their dependency (guix-past)
 4. you pulled, so fetched 5fb77cc from guix-past Inria via the channel
    guix-gaming-channels
 5. guix-gaming-channels updated their dependency reference (guix-past)
 6. you pulled again… Bang!

Well, there is various solutions.  Somehow, you need to clean some cache
to make the authentication passes.  Is it still broken for you?

Cheers,
simon


1: https://gitlab.com/guix-gaming-channels/games/-/blob/34a0e847c1f5a062b4cfa261ee1ff06e1f9f0973/.guix-channel#L15-21



  parent reply	other threads:[~2024-11-29 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 23:28 Unable to get rid of guix-past (and unable to pull) Gabriel Wicki
2024-11-28  0:39 ` James Smith
2024-11-29 17:54   ` Gabriel Wicki
2024-11-29 15:58 ` Simon Tournier [this message]
2024-12-01 13:26   ` Ludovic Courtès
2024-12-01 18:28     ` Simon Tournier

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ldx2dob4.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gabriel@erlikon.ch \
    --cc=help-guix@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).