GNU bug report logs - #40646
gnu: Add blueman.

Previous Next

Full log

Message #20 received at 40646 <at> debbugs.gnu.org (full text, mbox):

From: Raghav Gururajan <raghavgururajan <at> disroot.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 40646 <at> debbugs.gnu.org
Subject: Re: [bug#40646] gnu: Add blueman. (v2)
Date: Mon, 20 Apr 2020 02:10:32 -0400

[Message part 1 (text/plain, inline)]

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 <at> gnu.org> wrote:
> >Hi,
> >
> >"Raghav Gururajan" <raghavgururajan <at> 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!

Please find the revised patch attached with this email. I tried
'python-wrapper', but still getting warnings during build.

Regards,
RG.

[0001-gnu-Add-blueman.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.