unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: 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 12:11:38 +0000	[thread overview]
Message-ID: <zcUl60uNx89TFw3s0JpJEnEdrd6MB3aAy1qGIslGMQPqBzpUnb7ZYrJ3eIOfjtxefiGRqCAqkLkER0_Tm1LHqvgmzav-6T4jlvtnidUe58w=@elenq.tech> (raw)
In-Reply-To: <5a6392cd-b478-846a-beda-4f97e46cbdd0@raghavgururajan.name>

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.

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


  reply	other threads:[~2021-01-08 12:12 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 [this message]
2021-01-08 12:20     ` Julien Lepiller
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

  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='zcUl60uNx89TFw3s0JpJEnEdrd6MB3aAy1qGIslGMQPqBzpUnb7ZYrJ3eIOfjtxefiGRqCAqkLkER0_Tm1LHqvgmzav-6T4jlvtnidUe58w=@elenq.tech' \
    --to=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 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).