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: Sat, 02 Sep 2023 10:29:05 +0100 Message-ID: <9F2C9E0B-9B94-4B64-A57C-5117CEA9AA74@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4027668300047759474==" List-Id: --===============4027668300047759474== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, Have you been running this as root? I am not sure how well this is all workin= g as an unprivileged user at the moment. I think there might be a little bit = of work ahead to make it work well. Otherwise, you can add =E2=80=94-debug to the command line and it should writ= e more detailed output into the journal. Best, -Michael > On 1 Sep 2023, at 17:37, Adolf Belka wrote: >=20 > Hi Michael, >=20 > On 01/09/2023 18:23, Michael Tremer wrote: >> Hello, >> Yes, I believe this is what it does on my system. So this is alright. >> Did you try the other commands? > Just tried them and got the following errors:- >=20 > pakfire-builder build beep/beep.nm > Database Error: SQL logic error: no such table: settings in "SELECT val FRO= M settings WHERE key =3D ?" > Database Error: SQL logic error: no such table: settings in "SELECT val FRO= M settings WHERE key =3D ?" > Package Database: testing 100% | 1.6M 00:00 > Package Database: bootstrap 100% | 2.1M 00:00 > Could not read next file: /var/lib/pakfire/local/ipfire/3: Cannot stat > OSError: [Errno 25] Inappropriate ioctl for device >=20 > The above exception was the direct cause of the following exception: >=20 > 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 exception= set >=20 > Regards, > Adolf. >> -Michael >>> On 1 Sep 2023, at 17:21, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> On 01/09/2023 16:39, Michael Tremer wrote: >>>> Hello Adolf, >>>>> On 17 Aug 2023, at 12:20, Adolf Belka wrote: >>>>>=20 >>>>> Hi Michael, >>>>>=20 >>>>> When I built pakfire I just installed the programs that were flagged up= as missing during the configure section. >>>>>=20 >>>>> I have now gone through the filenames you listed from debian and eventu= ally found what the equivalent packages that contain those are called in Arch= Linux (most were easy but a few were convoluted to find). >>>>>=20 >>>>> Everything was already installed on my laptop except for liblzma-dev wh= ich is lzlib in Arch Linux. >>>>>=20 >>>>> 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 th= e dependencies are optional. >>>> Apologies for taking so long to reply, but I should finally have a fix f= or 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 = again and you should have a few tests pass. Not all of them are passing at th= e moment. >>> This time 20 passed out of 28 >>>=20 >>> 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 IPF= ire 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 >>>>>=20 >>>>> Regards, >>>>>=20 >>>>> Adolf. >>>>>=20 >>>>>=20 >>>>> On 17/08/2023 12:18, Adolf Belka wrote: >>>>>> Hi Michael, >>>>>>=20 >>>>>> I did a clean new install and took the log files from the tests/libpak= fire and tests/python directories. >>>>>>=20 >>>>>> The only one that passed this time was the test.py from the tests/pyth= on directory. All others failed. >>>>>>=20 >>>>>> I have archived them into an xz file that is attached. >>>>>>=20 >>>>>> Regards, >>>>>> Adolf. >>>>>>=20 >>>>>> On 17/08/2023 11:38, Michael Tremer wrote: >>>>>>> Hello Adolf, >>>>>>>=20 >>>>>>> Thank you very much for the quick feedback. >>>>>>>=20 >>>>>>> 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. >>>>>>>=20 >>>>>>> Best, >>>>>>> -Michael >>>>>>>=20 >>>>>>>> On 17 Aug 2023, at 10:36, Adolf Belka wro= te: >>>>>>>>=20 >>>>>>>> I am using Arch Linux. >>>>>>>>=20 >>>>>>>> I already do some building of my bacula client package on my laptop = so it has 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, pyth= on-tornado 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 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. >>>>>>>>=20 >>>>>>>> make install went fine and after that I can run pakfire-builder --he= lp 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 hav= e a working 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 mayb= e we even get a chance to update a few packages of the distribution or someth= ing=E2=80=A6 >>>>>>>>>=20 >>>>>>>>> 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 y= et, 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 als= o use the time to find any issues that might occur on other distributions tha= n Debian which is what I have been using. >>>>>>>>>=20 >>>>>>>>> Please find the source here: https://git.ipfire.org/?p=3Dpakfire.gi= t;a=3Dsummary >>>>>>>>>=20 >>>>>>>>> On Debian, I have to install these packages as dependencies (yes it= is quite a lot): >>>>>>>>>=20 >>>>>>>>> * asciidoc, autoconf, automake, bison, build-essential, flex, intlt= ool, libarchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-d= ev, libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev, libnl-3-dev, libn= l-route-3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, libsolv-dev, lib= sqlite3-dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config, py= thon3-cpuinfo, python3-kerberos, python3-tornado, python3-psutil, python3-set= proctitle, 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 t= he configure 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-hel= p. >>>>>>>>>=20 >>>>>>>>> Please let me know if that works for you up to this point and pleas= e file a bug if changes are required to make Pakfire work on your distributio= n. >>>>>>>>>=20 >>>>>>>>> All the best, >>>>>>>>> -Michael >>>>>>>>=20 >>>>>>>> --=20 >>>>>>>> Sent from my laptop >>>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Sent from my laptop >>>>>=20 >>>=20 >>> --=20 >>> Sent from my laptop >=20 > --=20 > Sent from my laptop --===============4027668300047759474==--