unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 26975-done@debbugs.gnu.org
Subject: bug#26975: Frequent errors in guix publish on Hydra
Date: Thu, 18 May 2017 21:39:06 +0200	[thread overview]
Message-ID: <874lwiarad.fsf@gnu.org> (raw)
In-Reply-To: <87lgpvaqu6.fsf@netris.org> (Mark H. Weaver's message of "Wed, 17 May 2017 21:36:33 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> Here's a recent excerpt of the console output from guix publish running
> Hydra.  Is this expected?
>
>       Mark
>
> GET /ggy44sk2w47j0dpbghpb9ipr6kik6vsm.narinfo
> GET /qnpsdhgiabvr89i9vdcmhzkggs79i0pc.narinfo
> GET /zgzvzsbhvyinb3vdsgswkqh2b0ih9x1i.narinfo
> In guix/workers.scm:
>      72:9  2 (_)
>     76:32  1 (_ system-error "stat" "~A: ~S" ("No such file or d?" ?) ?)
> In unknown file:
>            0 (make-stack #t)
> ERROR: In procedure make-stack:
> ERROR: In procedure stat: No such file or directory: "/var/cache/guix/publish/none/zgzvzsbhvyinb3vdsgswkqh2b0ih9x1i-xclip-0.12.tar.gz.nar"

Fixed in ffa5e0a6d2851832b7f0e6f943bc69e69e1bc8b0.

The consequence of this bug is that ‘guix publish --cache’ would always
return 404 for narinfos corresponding to already-compressed files
(files with a name ending in .gz, .xz, etc., such as source tarballs.)

Consequently, clients would download source tarballs from upstream or
from the /file URL rather than as a substitute.  Thus, this should be
almost invisible to users.

So we’ll upgrade ‘guix publish’ on hydra & bayfront, but no need to
rush, I think.

Thanks,
Ludo’.

      reply	other threads:[~2017-05-18 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  1:36 bug#26975: Frequent errors in guix publish on Hydra Mark H Weaver
2017-05-18 19:39 ` Ludovic Courtès [this message]

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=874lwiarad.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=26975-done@debbugs.gnu.org \
    --cc=mhw@netris.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 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).