From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Getting everyone started with Pakfire Date: Thu, 17 Aug 2023 10:38:08 +0100 Message-ID: In-Reply-To: <5bac4727-e5b2-453b-916e-21778aeff7f4@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0530067644125489401==" List-Id: --===============0530067644125489401== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 the test/libpakfire directory? Let=E2=80=99s see what = is going wrong there. For me a few tests fail, but a few should run just fine. Best, -Michael > On 17 Aug 2023, at 10:36, Adolf Belka wrote: >=20 > I am using Arch Linux. >=20 > I already do some building of my bacula client package on my laptop so it h= as the normal build tools installed. >=20 > To get autogen.sh to run I had to install intltool >=20 > To get configure to run I had to additionally install. >=20 > asciidoc, python-py-cpuinfo, python-pykerberos, python-systemd, python-torn= ado and libsolv >=20 > After that configure ran without any problems, as did make. >=20 > Although make check is in brackets I gave it a go but got 1 pass and 26 fai= ls. The only pass was for test.py > I ran the make check a second time and then two passed - test.py and progre= ssbar.py > Further running of make check didn't change anything. >=20 > make install went fine and after that I can run pakfire-builder --help and = get the help screen. >=20 > Regards, > Adolf. >=20 >=20 > On 16/08/2023 17:29, Michael Tremer wrote: >> Hello everyone, >>=20 >> For our meet-up that is starting soon, I would like everyone to have a wor= king installation of Pakfire - our new build system. >>=20 >> I am not sure yet in what way we are going to use it, but generally there = will be an intro for everyone who hasn=E2=80=99t had one yet, and maybe we ev= en get a chance to update a few packages of the distribution or something=E2= =80=A6 >>=20 >> Because I don=E2=80=99t know which distributions you are using, and becaus= e we don=E2=80=99t have any packages for any major distribution just yet, I w= ould like to ask everyone to install Pakfire manually on their systems in adv= ance of our meet-up, so that we can start straight away. We should also use t= he time to find any issues that might occur on other distributions than Debia= n which is what I have been using. >>=20 >> Please find the source here: https://git.ipfire.org/?p=3Dpakfire.git;a=3Ds= ummary >>=20 >> On Debian, I have to install these packages as dependencies (yes it is qui= te a lot): >>=20 >> * asciidoc, autoconf, automake, bison, build-essential, flex, intltool, li= barchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-dev, lib= json-c-dev, liblzma-dev, libmagic-dev, libmount-dev, libnl-3-dev, libnl-route= -3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, libsolv-dev, libsqlite3= -dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config, python3-c= puinfo, python3-kerberos, python3-tornado, python3-psutil, python3-setproctit= le, uuid-dev >>=20 >> I have no idea what the package names will be for your distribution, but I= am sure you will all figure it out :) >>=20 >> You can use the usual three-clause build process after generating the conf= igure script: >>=20 >> ./autogen.sh >> ./configure =E2=80=94-prefix=3D/usr =E2=80=94-sysconfdir=3D/etc =E2=80= =94-enable-debug >> make >> (make check) >> make install >>=20 >> After that, you should be able to run pakfire-builder =E2=80=94-help. >>=20 >> Please let me know if that works for you up to this point and please file = a bug if changes are required to make Pakfire work on your distribution. >>=20 >> All the best, >> -Michael >=20 > --=20 > Sent from my laptop >=20 --===============0530067644125489401==--