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:37:58 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3945913867399052915==" List-Id: --===============3945913867399052915== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 01/09/2023 18:23, Michael Tremer wrote: > Hello, >=20 > Yes, I believe this is what it does on my system. So this is alright. >=20 > Did you try the other commands? Just tried them and got the following errors:- pakfire-builder build beep/beep.nm Database Error: SQL logic error: no such table: settings in "SELECT val=20 FROM settings WHERE key =3D ?" Database Error: SQL logic error: no such table: settings in "SELECT val=20 FROM settings WHERE key =3D ?" Package Database: testing 100%=20 | 1.6M 00:00 Package Database: bootstrap 100%=20 | 2.1M 00:00 Could not read next file: /var/lib/pakfire/local/ipfire/3: Cannot stat OSError: [Errno 25] Inappropriate ioctl for device The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/bin/pakfire-builder", line 437, in c() File "/usr/bin/pakfire-builder", line 212, in __call__ ret =3D args.func(args) ^^^^^^^^^^^^^^^ File "/usr/bin/pakfire-builder", line 233, in _build p =3D self.pakfire(ns) ^^^^^^^^^^^^^^^^ File "/usr/bin/pakfire-builder", line 194, in pakfire p =3D pakfire.Pakfire(arch=3Dns.arch, conf=3Dc, logger=3Dlogger.log) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SystemError: returned a result with an=20 exception set Regards, Adolf. >=20 > -Michael >=20 >> On 1 Sep 2023, at 17:21, Adolf Belka wrote: >> >> Hi Michael, >> >> On 01/09/2023 16:39, Michael Tremer wrote: >>> Hello Adolf, >>>> 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 eventua= lly found what the equivalent packages that contain those are 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 whi= ch is lzlib in Arch Linux. >>>> >>>> Just to check, I installed lzlib and re-did the make check and the same = problems occurred. >>> The configure script will complain if something is missing as none of the= dependencies are optional. >>> Apologies for taking so long to reply, but I should finally have a fix fo= r the test suite: >>> https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h=3D9eef0cb603b= c51a5b34f042fced6e4d0bfa8d9d8 >>> https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h=3Dc54bafa7e74= dbcb5b07bafe8fadf2ca830fd93d7 >>> Please just run =E2=80=9Cgit pull=E2=80=9D, then =E2=80=9Cmake=E2=80=9D a= gain and you should have a few tests pass. Not all of them are passing at the= moment. >> 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 >> >>> If pakfire-builder =E2=80=94-help runs fine, you could check out the IPFi= re 3.x repository and run this: >>> git clone https://git.ipfire.org/pub/git/ipfire-3.x.git >>> cd ipfire-3.x >>> pakfire-builder build beep/beep.nm >>> Please let me know how that is going. >>> -Michael >>>> >>>> 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/libpakf= ire and tests/python directories. >>>>> >>>>> The only one that passed this time was the test.py from the tests/pytho= n 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 wrot= e: >>>>>>> >>>>>>> I am using Arch Linux. >>>>>>> >>>>>>> I already do some building of my bacula client package on my laptop s= o 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, pytho= n-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 = progressbar.py >>>>>>> Further running of make check didn't change anything. >>>>>>> >>>>>>> make install went fine and after that I can run pakfire-builder --hel= p 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 = 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 distribution or somethi= ng=E2=80=A6 >>>>>>>> >>>>>>>> Because I don=E2=80=99t know which distributions you are using, and = because we don=E2=80=99t have any packages for any major distribution just ye= t, 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= use the time to find any issues that might occur on other distributions than= Debian 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, intlto= ol, libarchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-de= v, libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev, libnl-3-dev, libnl= -route-3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, libsolv-dev, libs= qlite3-dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config, pyt= hon3-cpuinfo, python3-kerberos, python3-tornado, python3-psutil, python3-setp= roctitle, uuid-dev >>>>>>>> >>>>>>>> I have no idea what the package names will be for your distribution,= but I am sure you will all figure it out :) >>>>>>>> >>>>>>>> You can use the usual three-clause build process after generating th= e 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= file 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 >> Sent from my laptop >=20 >=20 --=20 Sent from my laptop --===============3945913867399052915==--