unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Julien Lepiller <julien@lepiller.eu>,
	guix-devel@gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: Re: error building new package (In procedure chdir: Not a directory)
Date: Wed, 23 Jun 2021 08:50:32 +0200	[thread overview]
Message-ID: <877dilvzuv.fsf@xelera.eu> (raw)
In-Reply-To: <CB71BE40-80C7-432B-AEE1-752725E5CA2E@lepiller.eu>

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

Hello Julien and Tobias,

Julien Lepiller <julien@lepiller.eu> writes:

> I think that's because the patch first extracts the archive, chdirs to
> the first directory, and applies the patch. But if there's no
> directory, it can't chdir and fails.

Yes, that's the problem: I thought that

  (patches (search-patches "ruby-taskjuggler-fix-TjTime.patch"))

was working the same as with other (origin...)s declarations but AFAIU
it does not work with "rubygems-uri"s

> Note that (with-directory-excursion ".") does nothing :)

Oh OK, anyway that piece of code is useless since "after-unpack" there
are no more gzipped files... obviously they are already unpacked :-D

> Le 22 juin 2021 12:35:45 GMT-04:00, Giovanni Biscuolo <g@xelera.eu> a écrit :

[...]

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

I'm new to gem's but after I've "manually" downloaded
https://rubygems.org/downloads/taskjuggler-3.7.1.gem I see that the
three files listed above are part of the gem file structure: I guess
ruby-build-system is trying to apply the patch before unpacking the *.gz
archives, but AFAIU it should do it after unpacking.

I'll try to study the code to see if I understand how it works
and if this is a bug, but unfortunately I've little time this days.

Thank you for your help! Giovanni

[...]

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

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

      reply	other threads:[~2021-06-23  6: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
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 [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=877dilvzuv.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --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).