unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: "guix pull" expiry channels
Date: Fri, 11 Jun 2021 23:32:17 +0200	[thread overview]
Message-ID: <87y2bg3x5q.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ2TEiGLfOF6_QO274d-nFiG5vK97UqDv+e+JV1SFKswXA@mail.gmail.com> (zimoun's message of "Wed, 9 Jun 2021 14:51:54 +0200")

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

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> I do not know if it is not a bug.  From f8acd1a (pulled April, 21rst), I get:
>
> Updating channel 'guix' from Git repository at
> 'https://git.savannah.gnu.org/git/guix.git'...
> guix pull: error: Git error: failed to resolve path
> '/home/simon/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq':
> No such file or directory
>
>
> Indeed, after the error, I have this:
>
> $ ls ~/.cache/guix/checkouts/
> f5uvstgmyyeyhl66lla3yxbp26x25xwt7rbwah3kahh724xwzisa  last-expiry-cleanup
>
> Then if I run again "guix pull", it works as expected.
>
> It is hard to reproduce. ;-)  I suspect a bug in
> 'maybe-remove-expired-cache-entries' or 'update-cache-checkout'.

Sounds plausible!

The code in (guix git) determines expiration based on the mtime of
sub-directories in ~/.cache/guix/checkouts.  But that’s bogus, no?

Yes, and the Internet confirms: a directory’s mtime is only changed when
a file inside it is renamed, added, or deleted.)  Oops!  So it would
depend on how frequently you pull, and perhaps on the file system you
use, go figure.

The patch below should fix it.  Will push shortly, thank you!

Ludo’.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 740 bytes --]

diff --git a/guix/git.scm b/guix/git.scm
index 57fa2ca1ee..9c6f326c36 100644
--- a/guix/git.scm
+++ b/guix/git.scm
@@ -424,6 +424,14 @@ it unchanged."
        ;; REPOSITORY as soon as possible.
        (repository-close! repository)
 
+       ;; Update CACHE-DIRECTORY's mtime to so the cache logic sees it.
+       (match (gettimeofday)
+         ((seconds . microseconds)
+          (let ((nanoseconds (* 1000 microseconds)))
+            (utime cache-directory
+                   seconds seconds
+                   nanoseconds nanoseconds))))
+
        ;; When CACHE-DIRECTORY is a sub-directory of the default cache
        ;; directory, remove expired checkouts that are next to it.
        (let ((parent (dirname cache-directory)))

  parent reply	other threads:[~2021-06-11 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 12:51 "guix pull" expiry channels zimoun
2021-06-09 19:26 ` Pierre Neidhardt
2021-06-10  8:48   ` zimoun
2021-06-10  9:28     ` Pierre Neidhardt
2021-06-11 21:10   ` Ludovic Courtès
2021-06-11 21:32 ` Ludovic Courtès [this message]
2021-06-15  6:57   ` Pierre Neidhardt
2021-06-16  5:33   ` 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

  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=87y2bg3x5q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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 public inbox

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

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).