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

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

Hello,

some more info since I still do not understand where *.gz files are
coming from

Giovanni Biscuolo <g@xelera.eu> writes:

[...]

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

If I build the package with "--keep-failed" I can inspect the kept
building dir /home/guix-builder/guix-build-ruby-taskjuggler-3.7.1.drv-4,
and there are no *.gz files

[...]

>> so you need to use url-fetch/tarball and/or further unpack the
>> double-packed sources yourself in a custom phase.
>
> I'll try to do this: any example at hand please?

I've found and tried this:

--8<---------------cut here---------------start------------->8---

                  (add-after 'unpack 'unpack-bundled-sources
                    (lambda _
                      (with-directory-excursion "."
                        (invoke "tar" "xf" "checksums.yaml.gz"))))

--8<---------------cut here---------------end--------------->8---

but it fails:

--8<---------------cut here---------------start------------->8---

starting phase `unpack-bundled-sources'
tar: checksums.yaml.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
command "tar" "xf" "checksums.yaml.gz" failed with status 2

--8<---------------cut here---------------end--------------->8---

I still don't understand why appying a patch (with "(patches
(search-patches....))" in (source (origin...)) is failing.

Thanks! Giovanni

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

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

  reply	other threads:[~2021-06-22 16:36 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
2021-06-17 22:24   ` Tobias Geerinckx-Rice
2021-06-22 15:36   ` Giovanni Biscuolo
2021-06-22 16:35     ` Giovanni Biscuolo [this message]
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=87czsdx3fi.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).