On 03/06/2019 20:58, Jan Rękorajski wrote:
> On Mon, 03 Jun 2019, arekm wrote:
>
>> commit 28dc894f0a27bdc080bbfc821d2841760a70927b
>> Author: Arkadiusz Miśkiewicz
>> Date: Mon Jun 3 15:09:13 2019 +0200
>>
>> - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no
>> read acce
On Mon, 03 Jun 2019, arekm wrote:
> commit 28dc894f0a27bdc080bbfc821d2841760a70927b
> Author: Arkadiusz Miśkiewicz
> Date: Mon Jun 3 15:09:13 2019 +0200
>
> - bump libicu-devel to 63.1; builds fine with nodejs 10 even with no read
> access to resolv.conf
>
> firefox.spec | 2 +-
> 1 fil
On Mon, Jun 03, 2019 at 08:19:42AM +0200, Jacek Konieczny wrote:
> On 03/06/2019 07.25, Jan Rękorajski wrote>
> > I don't believe it's nodejs problem, I think it's builder
> > security/networking problem.
> But the security/networking restrictions are there for a reason. If we
> allow build process
That nodejs in firefox is not downloading anything AFAIK, it's just
convoluted build process that needs nodejs started and it cannot start
without dns :/
I don't remember how we run builds, but maybe if we point resolv.conf at
127.0.0.1 it will be enough for it.
On Mon, Jun 3, 2019 at 8:19 AM Jace
