unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org
Subject: Re: error building new package (In procedure chdir: Not a directory)
Date: Thu, 17 Jun 2021 22:52:20 +0200	[thread overview]
Message-ID: <87h7hwpkc7.fsf@nckx> (raw)
In-Reply-To: <87tulwldmi.fsf@xelera.eu>

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

Giovanni,

Giovanni Biscuolo 写道:
> If I try to build the package I get this error:
[…]

Your source tarball contains multiple gzipped files, one of which 
itself a tarball:

> metadata.gz
> data.tar.gz
> checksums.yaml.gz
> source is under 'checksums.yaml.gz'
> Backtrace:
>            2 (primitive-load 
>            "/gnu/store/0d1j4s7c1h8w6z700sxb88jqmjp?")
> In ice-9/eval.scm:
>     619:8  1 (_ #(#<directory (guile-user) 7ffff3bb3f00> 
>     "checksum?"))
> In unknown file:
>            0 (chdir "checksums.yaml.gz")
>
> ERROR: In procedure chdir:
> In procedure chdir: Not a directory

Guix's heuristic is very simple: chdir to the first (or last, 
dunno) file it finds in a tarball, because foo-1.2.3.tar.gz is 
expected to contain a single foo-1.2.3 directory.  It usually 
works, but here it fails, so you need to use url-fetch/tarball 
and/or further unpack the double-packed sources yourself in a 
custom phase.

Kind regards,

T G-R

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

  reply	other threads:[~2021-06-17 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 15:22 error building new package (In procedure chdir: Not a directory) Giovanni Biscuolo
2021-06-17 20:52 ` Tobias Geerinckx-Rice [this message]
2021-06-17 22:24   ` Tobias Geerinckx-Rice
2021-06-22 15:36   ` Giovanni Biscuolo
2021-06-22 16:35     ` Giovanni Biscuolo
2021-06-22 17:50       ` Julien Lepiller
2021-06-23  6:50         ` Giovanni Biscuolo

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=87h7hwpkc7.fsf@nckx \
    --to=me@tobias.gr \
    --cc=g@xelera.eu \
    --cc=guix-devel@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.
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).