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: Sat, 02 Sep 2023 12:49:36 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8839983701991644168==" List-Id: --===============8839983701991644168== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, I went back to pakfire and looked through the config.log file from my build. From that I noticed the following defines #define PAKFIRE_CONFIG_DIR "/etc/pakfire" #define PAKFIRE_CACHE_DIR "/var/cache/pakfire" #define PAKFIRE_PRIVATE_DIR "/var/lib/pakfire" #define PAKFIRE_SCRIPTS_DIR "/lib/pakfire" #define PAKFIRE_TMP_DIR "/var/tmp" After running sudo make install then /var/lib/pakfire and=20 /var/cache/pakfire are not present on the system. I also read through the INSTALL file in the pakfire directory and it=20 said the following were required. Requirements: =C2=A0* Python 2.6 or greater (not Python 3.x) =C2=A0* python-argsparse (included in Python 2.7) =C2=A0* libcap =C2=A0* libsolv =C2=A0* xz =C2=A0* beecrypt (requires libgomp) =C2=A0* popt =C2=A0* libelf =C2=A0* elfutils I don't have beecrypt or libgomp installed and not available from Arch=20 Linux except from their AUR which requires me to build them. Also the mention of not Python 3.x as that is all that is available on=20 Arch Linux. Are the above requirements correct or out of date and should be ignored? Regards, Adolf. On 02/09/2023 12:26, Adolf Belka wrote: > Hi Michael, > > On 02/09/2023 11:29, Michael Tremer wrote: >> Hello Adolf, >> >> Have you been running this as root? I am not sure how well this is=20 >> all working as an unprivileged user at the moment. I think there=20 >> might be a little bit of work ahead to make it work well. > Yes, I was using an unprivileged user. I always do that unless the=20 > instructions say to use sudo or if the program comes back and says it=20 > must be run with root privileges. Or if I know that it has to be run=20 > with sudo like make install. > > So tried it again with sudo and the error message was exactly the same. > > Tried > sudo pakfire-builder --debug build beep/beep.nm > > and the error message was exactly the same. > > Tried sudo -s to get a root prompt and then ran the pakfire-builder=20 > command and exactly the same error message. > > As the first part of the error message is > > Database Error: SQL logic error: > > I confirmed that I do have sqlite installed. > > There is also a line in the error > > Could not read next file: /var/lib/pakfire/local/ipfire/3: Cannot stat > > I checked and there is no pakfire directory under /var/lib/ > Is there supposed to be? Maybe something is not working right during=20 > the pakfire build on my system. The build is working okay but maybe=20 > something that is required for the execution is not being correctly=20 > setup. > > What files should the pakfire make install be creating? > > Regards, > Adolf > > >> >> Otherwise, you can add =E2=80=94-debug to the command line and it should=20 >> write more detailed output into the journal. >> >> Best, >> -Michael >> >>> On 1 Sep 2023, at 17:37, Adolf Belka wrote: >>> >>> Hi Michael, >>> >>> 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:- >>> >>> pakfire-builder build beep/beep.nm >>> Database Error: SQL logic error: no such table: settings in "SELECT=20 >>> val FROM settings WHERE key =3D ?" >>> Database Error: SQL logic error: no such table: settings in "SELECT=20 >>> val FROM settings WHERE key =3D ?" >>> Package Database: testing 100%=C2=A0=C2=A0 | 1.6M=C2=A0 00:00 >>> Package Database: bootstrap 100%=C2=A0=C2=A0 | 2.1M=C2=A0 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): >>> =C2=A0 File "/usr/bin/pakfire-builder", line 437, in >>> =C2=A0=C2=A0=C2=A0 c() >>> =C2=A0 File "/usr/bin/pakfire-builder", line 212, in __call__ >>> =C2=A0=C2=A0=C2=A0 ret =3D args.func(args) >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^^^^^^^^^^^^^^^ >>> =C2=A0 File "/usr/bin/pakfire-builder", line 233, in _build >>> =C2=A0=C2=A0=C2=A0 p =3D self.pakfire(ns) >>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ^^^^^^^^^^^^^^^^ >>> =C2=A0 File "/usr/bin/pakfire-builder", line 194, in pakfire >>> =C2=A0=C2=A0=C2=A0 p =3D pakfire.Pakfire(arch=3Dns.arch, conf=3Dc, logger= =3Dlogger.log) >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> SystemError: returned a result with an=20 >>> exception set >>> >>> Regards, >>> Adolf. >>>> -Michael >>>>> 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 =20 >>>>>>> wrote: >>>>>>> >>>>>>> Hi Michael, >>>>>>> >>>>>>> When I built pakfire I just installed the programs that were=20 >>>>>>> flagged up 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=20 >>>>>>> are called in Arch Linux (most were easy but a few were=20 >>>>>>> convoluted to find). >>>>>>> >>>>>>> Everything was already installed on my laptop except for=20 >>>>>>> liblzma-dev which is lzlib in Arch Linux. >>>>>>> >>>>>>> Just to check, I installed lzlib and re-did the make check and=20 >>>>>>> the same problems occurred. >>>>>> The configure script will complain if something is missing as=20 >>>>>> none of the dependencies are optional. >>>>>> Apologies for taking so long to reply, but I should finally have=20 >>>>>> a fix for 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=20 >>>>>> 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=20 >>>>>> IPFire 3.x repository and run this: >>>>>> =C2=A0=C2=A0 git clone https://git.ipfire.org/pub/git/ipfire-3.x.git >>>>>> =C2=A0=C2=A0 cd ipfire-3.x >>>>>> =C2=A0=C2=A0 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=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=20 >>>>>>>>> files in the test/libpakfire directory? Let=E2=80=99s see what is=20 >>>>>>>>> going wrong there. For me a few tests fail, but a few should=20 >>>>>>>>> run just fine. >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> -Michael >>>>>>>>> >>>>>>>>>> On 17 Aug 2023, at 10:36, Adolf Belka=20 >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> I am using Arch Linux. >>>>>>>>>> >>>>>>>>>> I already do some building of my bacula client package on my=20 >>>>>>>>>> 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,=20 >>>>>>>>>> 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=20 >>>>>>>>>> pass and 26 fails. The only pass was for test.py >>>>>>>>>> I ran the make check a second time and then two passed -=20 >>>>>>>>>> test.py and progressbar.py >>>>>>>>>> Further running of make check didn't change anything. >>>>>>>>>> >>>>>>>>>> make install went fine and after that I can run=20 >>>>>>>>>> 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=20 >>>>>>>>>>> to have a working installation of Pakfire - our new build=20 >>>>>>>>>>> system. >>>>>>>>>>> >>>>>>>>>>> I am not sure yet in what way we are going to use it, but=20 >>>>>>>>>>> generally there will be an intro for everyone who hasn=E2=80=99t = had=20 >>>>>>>>>>> one yet, and maybe we even get a chance to update a few=20 >>>>>>>>>>> packages of the distribution or something=E2=80=A6 >>>>>>>>>>> >>>>>>>>>>> Because I don=E2=80=99t know which distributions you are using, a= nd=20 >>>>>>>>>>> because we don=E2=80=99t have any packages for any major=20 >>>>>>>>>>> distribution just yet, I would like to ask everyone to=20 >>>>>>>>>>> install Pakfire manually on their systems in advance of our=20 >>>>>>>>>>> meet-up, so that we can start straight away. We should also=20 >>>>>>>>>>> use the time to find any issues that might occur on other=20 >>>>>>>>>>> distributions than Debian which is what I have been 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=20 >>>>>>>>>>> (yes it is quite a lot): >>>>>>>>>>> >>>>>>>>>>> * asciidoc, autoconf, automake, bison, build-essential,=20 >>>>>>>>>>> flex, intltool, libarchive-dev, libcap-dev,=20 >>>>>>>>>>> libcurl4-openssl-dev, libelf-dev, libgpgme-dev,=20 >>>>>>>>>>> libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev,=20 >>>>>>>>>>> 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,=20 >>>>>>>>>>> pkg-config, python3-cpuinfo, python3-kerberos,=20 >>>>>>>>>>> python3-tornado, python3-psutil, 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=20 >>>>>>>>>>> generating the configure script: >>>>>>>>>>> >>>>>>>>>>> =C2=A0=C2=A0=C2=A0 ./autogen.sh >>>>>>>>>>> =C2=A0=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=C2=A0 make >>>>>>>>>>> =C2=A0=C2=A0=C2=A0 (make check) >>>>>>>>>>> =C2=A0=C2=A0=C2=A0 make install >>>>>>>>>>> >>>>>>>>>>> After that, you should be able to run pakfire-builder =E2=80=94-h= elp. >>>>>>>>>>> >>>>>>>>>>> Please let me know if that works for you up to this point=20 >>>>>>>>>>> and please file a bug if changes are required to make=20 >>>>>>>>>>> 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 >>> Sent from my laptop >> >> > --=20 Sent from my laptop --===============8839983701991644168==--