From: Julien Lepiller <julien@lepiller.eu>
To: Ekaitz Zarraga <ekaitz@elenq.tech>,
Raghav Gururajan <rg@raghavgururajan.name>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [Telegram-Desktop]: Help with packaging
Date: Fri, 08 Jan 2021 07:20:26 -0500 [thread overview]
Message-ID: <B595C653-578E-4B25-86CE-29142CBFAAA2@lepiller.eu> (raw)
In-Reply-To: <zcUl60uNx89TFw3s0JpJEnEdrd6MB3aAy1qGIslGMQPqBzpUnb7ZYrJ3eIOfjtxefiGRqCAqkLkER0_Tm1LHqvgmzav-6T4jlvtnidUe58w=@elenq.tech>
Le 8 janvier 2021 07:11:38 GMT-05:00, Ekaitz Zarraga <ekaitz@elenq.tech> a écrit :
>Hi,
>
>I'm not sure about what I'm going to say so take it with care:
>
>About the permission error I think the build directories are write
>protected by default it Guix, please someone correct me if I'm wrong.
>I'd say you can change the permissions of the folder with the chmod
>util, you can see many packages do it. Just call it like:
>
>(chmod filename mode)
>
>Being `mode` something like #o664 for an equivalent `chmod 664
>filename` bash call.
Well, not by default: /gnu is read-only, but the package wants to write to /tmp, which is read-write. However, since you're using the git-fetch method for the sources, they are copied as is. Since they come from the store, the files are read-only, whicg makes your sources read-only.
>
>So I guess you need an extra build phase to correct the permissions on
>the folder so the script can write to it.
>
>Maybe that will fix both errors, but make sure also that you have the
>dependencies for ElementTree, just in case.
>
>I hope this helps...
>
>Best,
>Ekaitz
next prev parent reply other threads:[~2021-01-08 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 1:54 [Telegram-Desktop]: Help with packaging Raghav Gururajan
2021-01-08 1:59 ` Raghav Gururajan
2021-01-08 12:11 ` Ekaitz Zarraga
2021-01-08 12:20 ` Julien Lepiller [this message]
2021-01-08 12:16 ` Ricardo Wurmus
2021-01-08 21:21 ` Mark H Weaver
2021-01-08 22:04 ` Ricardo Wurmus
2021-01-08 22:52 ` Raghav Gururajan
2021-01-09 1:59 ` Raghav Gururajan
2021-01-12 3:32 ` Raghav Gururajan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B595C653-578E-4B25-86CE-29142CBFAAA2@lepiller.eu \
--to=julien@lepiller.eu \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=rg@raghavgururajan.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.