From: Raghav Gururajan <raghavgururajan@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40646@debbugs.gnu.org
Subject: [bug#40646] gnu: Add blueman.
Date: Sun, 19 Apr 2020 20:25:57 -0400 [thread overview]
Message-ID: <1082E275-C6A5-4D33-997F-2E45C7A36BB4@disroot.org> (raw)
In-Reply-To: <87ftcz15i4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Hi Ludo!
Yes yes, sorry, I did not over look. I was gonna try it and then goon let you know. :-)
Regards,
RG.
On April 19, 2020 6:21:23 p.m. EDT, "Ludovic Courtès" <ludo@gnu.org> wrote:
>Hi,
>
>"Raghav Gururajan" <raghavgururajan@disroot.org> skribis:
>
>>>> + (substitute* "apps/blueman-adapters.in"
>>>> + (("@PYTHON@") (string-append (assoc-ref inputs "python")
>>>> + "/bin/python3.7")))
>>>
>>> Are you sure this is necessary? If these are scripts, the
>>> ‘patch-shebangs’ phase should take care of it. Perhaps it’s enough
>to
>>> add ‘python-wrapper’ as an input (it provides a “python” executable)
>and
>>> then you can remove all this?
>>
>> It is not necessary. Those scripts were not patched by
>'patch-shebangs' phase, and received warnings during build. So
>corrected them manually. :-)
>
>I think you overlooked the rest of my comment: if you add
>‘python-wrapper’ as an input, everything will be fine.
>
>Could you check?
>
>Thanks in advance!
>
>Ludo’.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1751 bytes --]
next prev parent reply other threads:[~2020-04-20 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 17:52 [bug#40646] gnu: Add blueman Raghav Gururajan
2020-04-19 11:22 ` Ludovic Courtès
2020-04-19 11:27 ` Raghav Gururajan
2020-04-19 22:21 ` Ludovic Courtès
2020-04-20 0:25 ` Raghav Gururajan [this message]
2020-04-20 6:10 ` [bug#40646] gnu: Add blueman. (v2) Raghav Gururajan
2020-04-22 15:20 ` bug#40646: " Ludovic Courtès
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=1082E275-C6A5-4D33-997F-2E45C7A36BB4@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=40646@debbugs.gnu.org \
--cc=ludo@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).