all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: zimoun <zimon.toutoune@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>, "Roel Janssen" <roel@gnu.org>
Cc: 47949@debbugs.gnu.org
Subject: bug#47949: Failed to produce output path for guix-package-cache
Date: Wed, 26 Oct 2022 16:25:30 -0700	[thread overview]
Message-ID: <878rl2kw0l.fsf@contorta> (raw)
In-Reply-To: <86o7tybbmq.fsf@gmail.com>

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

On 2022-10-26, zimoun wrote:
> On Wed, 26 Oct 2022 at 09:57, Vagrant Cascadian <vagrant@debian.org> wrote:
>
>> It is consistently the same errors in the log, though on further looking
>> i discovered a branch in ~/.cache/guix/checkouts/ that had old removed
>> files in it (including wicd.scm/wicd.go) ... *maybe* that was somehow
>> related. I did remove all the evidence, so so if stale checkouts is
>> somehow the issue, it will be hard to reproduce again... oops.
>
> Hum, what does “guix describe” say?

I'll try this instead, with some annotation:

$ guix pull -l 1w
# Version used when 139 failed:
Generation 138       Oct 19 2022 19:04:26
  guix e61660c
    repository URL: /home/vagrant/src/guix
    branch: master
    commit: e61660c78f1190c578dd6f202bc5529cbdcff84e

# First version where I noticed failures:
Generation 139       Oct 22 2022 13:07:08
  guix bb2701b
    repository URL: /home/vagrant/src/guix
    branch: master
    commit: bb2701b9111a3d82a82ceaaf2b22b51ecd8ac21f

# Failed to pull from 139, successfully pulled from 138:
Generation 140       Oct 24 2022 13:19:21
  guix 8663be6
    repository URL: /home/vagrant/src/guix-master
    branch: master
    commit: 8663be6da7f13a8eeea71dc1f493f7adc5b7672a

# failed to pull from 139, successfully pulled from 138:
Generation 141       Oct 25 2022 13:08:12
  guix a0751e3
    repository URL: /home/vagrant/src/guix-master
    branch: master
    commit: a0751e3250dfea7e52468c8090e18c3118d93a60

# Finally noticed the ~/.cache/guix/... leftover cruft and removed
# cached checkouts, successfully pulled from 141:
Generation 142       Oct 26 2022 10:03:18 (current)
  guix c07b55e
    repository URL: /home/vagrant/src/guix-master
    branch: master
    commit: c07b55eb94f8cfa9d0f56cfd97a16f2f7d842652

Apparently I sometimes used:

  guix pull --url=/home/vagrant/src/guix --branch=master

and sometimes:

  guix pull --url=/home/vagrant/src/guix-master --branch=master

Which end up using different directories in ~/.cache/guix/checkouts/
... and one of the directories has some cruft leftover in it.

After cleaning out the cruft, so far so good...


>> I did manage again to use an old commit to pull up to a more recent
>> master (a0751e3250dfea7e52468c8090e18c3118d93a60), and see there are new
>> commits now so will try again. Will see.
>
> What is your hackish workflow?  You do,
>
>     guix pull --commit=<old> && guix pull

To use the older generations I used:

  /var/guix/profiles/per-user/vagrant/current-guix-138-link/bin/guix pull ...


> right?  From your recent pull, does this
>
>     guix time-machine --commit=<new> -- help
>
> work?  where <new> is newer than your current revision.

Oh yeah, that reminds me to add to the confusion, "guix time-machine
--commit=SOMECOMMIT" worked fine, even where "SOMECOMMIT" didn't
successfully work with guix pull.

Maybe that's a clue pointing to the crufty .cache directories?


live well,
  vagrant

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

  reply	other threads:[~2022-10-26 23:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 11:38 bug#47949: Failed to produce output path for guix-package-cache Roel Janssen
2021-04-28 21:38 ` Ludovic Courtès
2021-04-29  7:01   ` Roel Janssen
2021-04-29  7:56     ` Ludovic Courtès
2022-10-25 19:50       ` Vagrant Cascadian
2022-10-26  8:10         ` zimoun
2022-10-26 16:57           ` Vagrant Cascadian
2022-10-26 19:58             ` zimoun
2022-10-26 23:25               ` Vagrant Cascadian [this message]
2022-10-28 20:23                 ` Vagrant Cascadian
2022-10-29 14:42                   ` Maxime Devos
2022-11-02 11:02                   ` zimoun
2022-11-02 18:40                     ` Vagrant Cascadian
2022-11-03  8:48                       ` zimoun
2022-11-03 18:35                         ` Vagrant Cascadian
2023-04-28 16:47                           ` Maxim Cournoyer
2023-04-28 17:41                             ` Maxim Cournoyer
2023-05-03 16:44                             ` Simon Tournier
2023-05-04 12:53                               ` Maxim Cournoyer
2023-05-04 18:05                                 ` Simon Tournier
2023-05-05 14:23                                   ` Maxim Cournoyer
2023-05-03 19:25                             ` Ludovic Courtès
2023-05-04 12:55                               ` Maxim Cournoyer
2023-05-04 12:59                               ` Maxim Cournoyer

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=878rl2kw0l.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=47949@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=roel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.