From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Getting everyone started with Pakfire Date: Fri, 01 Sep 2023 18:21:12 +0200 Message-ID: <46ddbe12-b361-4da5-924e-000067994e5f@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6787047893817316466==" List-Id: --===============6787047893817316466== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 01/09/2023 16:39, Michael Tremer wrote: > Hello Adolf, >=20 >> On 17 Aug 2023, at 12:20, Adolf Belka wrote: >> >> Hi Michael, >> >> When I built pakfire I just installed the programs that were flagged up as= missing during the configure section. >> >> I have now gone through the filenames you listed from debian and eventuall= y found what the equivalent packages that contain those are called in Arch Li= nux (most were easy but a few were convoluted to find). >> >> Everything was already installed on my laptop except for liblzma-dev which= is lzlib in Arch Linux. >> >> Just to check, I installed lzlib and re-did the make check and the same pr= oblems occurred. >=20 > The configure script will complain if something is missing as none of the d= ependencies are optional. >=20 > Apologies for taking so long to reply, but I should finally have a fix for = the test suite: >=20 > https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h=3D9eef0cb603bc5= 1a5b34f042fced6e4d0bfa8d9d8 > https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h=3Dc54bafa7e74db= cb5b07bafe8fadf2ca830fd93d7 >=20 > Please just run =E2=80=9Cgit pull=E2=80=9D, then =E2=80=9Cmake=E2=80=9D aga= in and you should have a few tests pass. Not all of them are passing at the m= oment. This time 20 passed out of 28 PASS: tests/libpakfire/main PASS: tests/libpakfire/arch PASS: tests/libpakfire/archive FAIL: tests/libpakfire/build FAIL: tests/libpakfire/cgroup PASS: tests/libpakfire/compress PASS: tests/libpakfire/config PASS: tests/libpakfire/db PASS: tests/libpakfire/dependencies PASS: tests/libpakfire/digest PASS: tests/libpakfire/downloader PASS: tests/libpakfire/file FAIL: tests/libpakfire/jail PASS: tests/libpakfire/key FAIL: tests/libpakfire/makefile PASS: tests/libpakfire/package PASS: tests/libpakfire/packager PASS: tests/libpakfire/parser PASS: tests/libpakfire/progressbar PASS: tests/libpakfire/repo PASS: tests/libpakfire/snapshot PASS: tests/libpakfire/string FAIL: tests/libpakfire/util FAIL: tests/python/keys.py FAIL: tests/python/jail.py FAIL: tests/python/package.py PASS: tests/python/progressbar.py PASS: tests/python/test.py >=20 > If pakfire-builder =E2=80=94-help runs fine, you could check out the IPFire= 3.x repository and run this: >=20 > git clone https://git.ipfire.org/pub/git/ipfire-3.x.git > cd ipfire-3.x > pakfire-builder build beep/beep.nm >=20 > Please let me know how that is going. >=20 > -Michael >=20 >> >> 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 tests/libpakfir= e and tests/python directories. >>> >>> The only one that passed this time was the test.py from the 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 the test/libpakfire directory? Let=E2=80=99s se= e what is going wrong there. For me a few tests fail, but a few should run ju= st fine. >>>> >>>> Best, >>>> -Michael >>>> >>>>> On 17 Aug 2023, at 10:36, Adolf Belka wrote: >>>>> >>>>> I am using Arch Linux. >>>>> >>>>> I already do some building of my bacula client package on my laptop 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, 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 26= fails. The only pass was for test.py >>>>> I ran the make check a second time and then two passed - test.py and pr= ogressbar.py >>>>> Further running of make check didn't change anything. >>>>> >>>>> make install went fine and after that I can run pakfire-builder --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 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 th= ere will be an intro for everyone who hasn=E2=80=99t had one yet, and maybe w= e even get a chance to update a few packages of the distribution or something= =E2=80=A6 >>>>>> >>>>>> Because I don=E2=80=99t know which distributions you are using, and be= cause we don=E2=80=99t have any packages for any major distribution just yet,= I would like to ask everyone to install Pakfire manually on their systems in= advance of our meet-up, so that we can start straight away. We should also u= se the time to find any issues that might occur on other distributions than D= ebian which is what I have been using. >>>>>> >>>>>> Please find the source here: https://git.ipfire.org/?p=3Dpakfire.git;a= =3Dsummary >>>>>> >>>>>> On Debian, I have to install these packages as dependencies (yes it is= quite a lot): >>>>>> >>>>>> * asciidoc, autoconf, automake, bison, build-essential, flex, intltool= , libarchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-dev,= libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev, libnl-3-dev, libnl-r= oute-3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, libsolv-dev, libsql= ite3-dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config, pytho= n3-cpuinfo, python3-kerberos, python3-tornado, python3-psutil, python3-setpro= ctitle, uuid-dev >>>>>> >>>>>> I have no idea what the package names will be for your distribution, b= ut I am sure you will all figure it out :) >>>>>> >>>>>> You can use the usual three-clause build process after generating the = configure script: >>>>>> >>>>>> ./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 >>>>>> >>>>>> 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 please f= ile a bug if changes are required to make Pakfire work on your distribution. >>>>>> >>>>>> All the best, >>>>>> -Michael >>>>> >>>>> --=20 >>>>> Sent from my laptop >>>>> >>>> >>> >> >> --=20 >> Sent from my laptop >> >=20 --=20 Sent from my laptop --===============6787047893817316466==--