From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka <adolf.belka@ipfire.org> To: development@lists.ipfire.org Subject: Re: Getting everyone started with Pakfire Date: Thu, 17 Aug 2023 13:20:48 +0200 Message-ID: <c6360586-95bc-4ba0-b368-51c4585f090a@ipfire.org> In-Reply-To: <ea5711e9-a27c-4717-ae3f-78eeb2f1eb51@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2940602203604678349==" List-Id: <development.lists.ipfire.org> --===============2940602203604678349== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, When I built pakfire I just installed the programs that were flagged up=20 as missing during the configure section. I have now gone through the filenames you listed from debian and=20 eventually found what the equivalent packages that contain those are=20 called in Arch Linux (most were easy but a few were convoluted to find). Everything was already installed on my laptop except for liblzma-dev=20 which is lzlib in Arch Linux. Just to check, I installed lzlib and re-did the make check and the same=20 problems occurred. Regards, Adolf. On 17/08/2023 12:18, Adolf Belka wrote: > Hi Michael, > > I did a clean new install and took the log files from the=20 > tests/libpakfire and tests/python directories. > > The only one that passed this time was the test.py from the=20 > tests/python directory. All others failed. > > I have archived them into an xz file that is attached. > > Regards, > Adolf. > > On 17/08/2023 11:38, Michael Tremer wrote: >> Hello Adolf, >> >> Thank you very much for the quick feedback. >> >> After running =E2=80=9Cmake check=E2=80=9D, could you email me the =E2=80= =9C*.log=E2=80=9D files in=20 >> the test/libpakfire directory? Let=E2=80=99s see what is going wrong there= .=20 >> For me a few tests fail, but a few should run just fine. >> >> Best, >> -Michael >> >>> On 17 Aug 2023, at 10:36, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >>> >>> I am using Arch Linux. >>> >>> I already do some building of my bacula client package on my laptop=20 >>> so it has the normal build tools installed. >>> >>> To get autogen.sh to run I had to install intltool >>> >>> To get configure to run I had to additionally install. >>> >>> asciidoc, python-py-cpuinfo, python-pykerberos, python-systemd,=20 >>> python-tornado and libsolv >>> >>> After that configure ran without any problems, as did make. >>> >>> Although make check is in brackets I gave it a go but got 1 pass and=20 >>> 26 fails. The only pass was for test.py >>> I ran the make check a second time and then two passed - test.py and=20 >>> progressbar.py >>> Further running of make check didn't change anything. >>> >>> make install went fine and after that I can run pakfire-builder=20 >>> --help and get the help screen. >>> >>> Regards, >>> Adolf. >>> >>> >>> On 16/08/2023 17:29, Michael Tremer wrote: >>>> Hello everyone, >>>> >>>> For our meet-up that is starting soon, I would like everyone to=20 >>>> have a working installation of Pakfire - our new build system. >>>> >>>> I am not sure yet in what way we are going to use it, but generally=20 >>>> there will be an intro for everyone who hasn=E2=80=99t had one yet, and = >>>> maybe we even get a chance to update a few packages of the=20 >>>> distribution or something=E2=80=A6 >>>> >>>> Because I don=E2=80=99t know which distributions you are using, and beca= use=20 >>>> we don=E2=80=99t have any packages for any major distribution just yet, = I=20 >>>> would like to ask everyone to install Pakfire manually on their=20 >>>> systems in advance of our meet-up, so that we can start straight=20 >>>> away. We should also use the time to find any issues that might=20 >>>> occur on other distributions than Debian which is what I have been=20 >>>> using. >>>> >>>> Please find the source here:=20 >>>> https://git.ipfire.org/?p=3Dpakfire.git;a=3Dsummary >>>> >>>> On Debian, I have to install these packages as dependencies (yes it=20 >>>> is quite a lot): >>>> >>>> * asciidoc, autoconf, automake, bison, build-essential, flex,=20 >>>> intltool, libarchive-dev, libcap-dev, libcurl4-openssl-dev,=20 >>>> libelf-dev, libgpgme-dev, libjson-c-dev, liblzma-dev, libmagic-dev,=20 >>>> libmount-dev, libnl-3-dev, libnl-route-3-dev, libpcre2-dev,=20 >>>> libpython3-dev, libseccomp-dev, libsolv-dev, libsqlite3-dev,=20 >>>> libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config,=20 >>>> python3-cpuinfo, python3-kerberos, python3-tornado, python3-psutil,=20 >>>> python3-setproctitle, uuid-dev >>>> >>>> I have no idea what the package names will be for your=20 >>>> distribution, but I am sure you will all figure it out :) >>>> >>>> You can use the usual three-clause build process after generating=20 >>>> the configure script: >>>> >>>> =C2=A0=C2=A0 ./autogen.sh >>>> =C2=A0=C2=A0 ./configure =E2=80=94-prefix=3D/usr =E2=80=94-sysconfdir=3D= /etc =E2=80=94-enable-debug >>>> =C2=A0=C2=A0 make >>>> =C2=A0=C2=A0 (make check) >>>> =C2=A0=C2=A0 make install >>>> >>>> After that, you should be able to run pakfire-builder =E2=80=94-help. >>>> >>>> Please let me know if that works for you up to this point and=20 >>>> please file a bug if changes are required to make Pakfire work on=20 >>>> your distribution. >>>> >>>> All the best, >>>> -Michael >>> >>> --=20 >>> Sent from my laptop >>> >> > --=20 Sent from my laptop --===============2940602203604678349==--