From mboxrd@z Thu Jan 1 00:00:00 1970 From: sio / To: development@lists.ipfire.org Subject: Re: The unshared changes give a problem with build after doing git pull on next Date: Thu, 29 Aug 2024 12:00:55 +0000 Message-ID: <172493285563.23677.14425673725004466262@mail02.haj.ipfire.org> In-Reply-To: <37C134D2-053F-4B2B-8571-37470D124BAD@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2145976049537544045==" List-Id: --===============2145976049537544045== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Michael Tremer wrote: > Hello sio, > The build system does not have any network access. We block this so that an= y compromised package cannot download anything more malicious that we don=E2= =80=99t have a paper trail for. It is also that not all build systems have in= ternet access all the time. > So you will have to download everything you need through the lfs/netdata fi= le, extract, and then run the build. > In the =E2=80=9C./make.sh shell=E2=80=9D environment we make network access= possible so that you can download files and patches and what not. > -Michael > > On 29 Aug 2024, at 02:07, sio / siosios1(a)hotmail.com wrote: > > I ran two separate builds on two different machines from scratch and they= ran through the build process no problems that i could tell. I also added th= e netdata package to the mix on a second run on one of the machines and faile= d the build with the below error. mind you i have a 3rd machine with CU187 on= it and it built the netdata package flawlessly, same files as I used on the = CU188 machine so I am not sure if this is from the change or not. I have also= gone into the shell with make.sh on the machine that had the error and could= build netdata just fine with the same commands as in the lfs file. > > netdata build from shell: > > --- We are done! --- > > ^ > > |.-. .-. .-. .-. .-. . netdata .-. .-. .-. .-. .-. = .- > > | '-' '-' '-' '-' '-' '-' '-' '-' '-' '-= ' =20 > > +----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+= ---> > > --- is installed now! ---=20 > > enjoy real-time performance and health monitoring... > > ipfire build chroot (x86_64) root:~/netdata-v1.47.0$ > > Ping from shell: > > [root(a)cloud ipfire-2.x]# ./make.sh shell > > Entering to a shell inside the build environment, go out with exit > > ipfire build chroot (x86_64) root:~$ ping github.com > > PING github.com (140.82.116.3) 56(84) bytes of data. > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D1= ttl=3D52 time=3D110 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D2= ttl=3D52 time=3D89.0 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D3= ttl=3D52 time=3D112 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D4= ttl=3D52 time=3D109 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D5= ttl=3D52 time=3D102 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D6= ttl=3D52 time=3D101 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D7= ttl=3D52 time=3D110 ms > > 64 bytes from lb-140-82-116-3-sea.github.com (140.82.116.3): icmp_seq=3D8= ttl=3D52 time=3D106 ms > > Error: > > netdata (1.47.0) = = [ 1:36 ][ FAIL ] > > Could not resolve host: github.com > > shutting down connection #0 > > --- LOG END --- > > error: downloading 'https://github.com/netdata/kernel-collector/releas= es/download/v1.4.5.1/netda...' failed > > status_code: 6 > > status_string: "Could not resolve hostname" > > log: > > --- LOG BEGIN --- > > Could not resolve host: github.com > > shutting down connection #0 > > --- LOG END --- > > ninja: build stopped: subcommand failed. > > FAILED '' > > ABORTED Failed to build Netdata. > > make: *** [netdata:86: /usr/src/log/netdata-v1.47.0] Error 1 > > make: Leaving directory '/usr/src/lfs' > > ERROR: Building netdata > > hello Michael, ok, that would make sense but was there a changed in 188 vs 187? just asking = due to being able to build the same identical package on 187, if there wasn't= a change then i need to do some more investigating. thank you for the info y= ou can provide on this. --===============2145976049537544045==--