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: Wed, 06 Sep 2023 19:12:05 +0200 Message-ID: <1bb1e389-f74c-43f5-b53e-49cb9c5af730@ipfire.org> In-Reply-To: <5EB30DB3-A6CA-466F-A661-E6CC3814DCDA@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8485841923471336237==" List-Id: --===============8485841923471336237== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 06/09/2023 15:41, Michael Tremer wrote: > Hello Adolf, >=20 > Yes, this looks better... >=20 >> On 5 Sep 2023, at 19:58, Adolf Belka wrote: >> >> Hi Michael, >> >> On 05/09/2023 18:25, Michael Tremer wrote: >>> Hello, >>> So I installed Archlinux (using the scenic route) and managed to fix both= problems that you encountered: >>> * The first one was the SQLite error message which was not really a probl= em, because we were trying to detect the database schema version here, but si= nce there was no database in the first place we could not read from the table. >>> This did not get logged before, and therefore I assume that this is a cha= nge in sqlite and as Archlinux simply is running on a later release, we ran i= nto this. It is very likely not an Archlinux-specific thing. >>> * The other thing isn=E2=80=99t Archlinux-specific either: The local pack= age repository did not exist, yet where Pakfire stores packages that have bee= n built locally. I must have recently introduced this problem when rewriting = the FTS stuff. >>> So, please pull and run this all again and let me know what breaks next :) >> This time pakfire-builder actually ran but there were a few error messages= on the way but these look to be more about the building now rather than gett= ing pakfire-builder to work. >> The following was what was output >> >> sudo pakfire-builder build beep/beep.nm >> Package Database: testing 100% | 2.1M 00:00 >> Could not retrieve uname for 1000: No such file or directory >> Could not retrieve gname for 1000: No such file or directory >> Could not retrieve uname for 1000: No such file or directory >> Could not retrieve gname for 1000: No such file or directory >> Could not retrieve uname for 1000: No such file or directory >> Could not retrieve gname for 1000: No such file or directory >> beep-1.3.tar.gz 100% | 19k 00:00 >> beep-1.3-2.ipfire3.src 20k 100% >> Building beep-1.3-2.ipfire3.src... >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D >=20 > Here should usually be a list of the transaction. As in: Which packages are= being installed. >=20 >> glibc-2.37-2.ipfire3.x86_64 100% >> ncurses-base-6.3-3.ipfire3.x86_64 100% >> libstdc++-12.3.0-1.ipfire3.x86_64 100% >> libgomp-12.3.0-1.ipfire3.x86_64 100% >> libgcc-12.3.0-1.ipfire3.x86_64 100% >> kernel-headers-6.4.3-3.ipfire3.x86_64 100% >> ca-certificates-2022.12-2.ipfire3.noarch 100% >> libdevmapper-2.03.16-2.ipfire3.x86_64 100% >> tzdata-2022g-1.ipfire3.noarch 100% >> libstdc++-devel-12.3.0-1.ipfire3.x86_64 100% >> libunwind-1.6.2-1.ipfire3.x86_64 100% >> npth-1.6-2.ipfire3.x86_64 100% >> libtasn1-4.19.0-1.ipfire3.x86_64 100% >> cyrus-sasl-libs-2.1.28-4.ipfire3.x86_64 100% >> popt-1.19-1.1.ipfire3.x86_64 100% >> nghttp2-1.51.0-1.1.ipfire3.x86_64 100% >> lzo-2.10-1.ipfire3.x86_64 100% >> pixman-0.42.2-1.ipfire3.x86_64 100% >> libgpg-error-1.46-1.ipfire3.x86_64 100% >> sqlite-libs-3.40.0-1.ipfire3.x86_64 100% >> libffi-3.4.4-1.ipfire3.x86_64 100% >> pcre2-utf32-10.40-1.ipfire3.x86_64 100% >> pcre2-utf16-10.40-1.ipfire3.x86_64 100% >> zstd-libs-1.5.2-1.ipfire3.x86_64 100% >> libseccomp-2.5.4-1.ipfire3.x86_64 100% >> xz-libs-5.2.8-1.ipfire3.x86_64 100% >> diffutils-3.8-1.ipfire3.x86_64 100% >> lzip-1.23-1.ipfire3.x86_64 100% >> make-4.4-1.ipfire3.x86_64 100% >> which-2.21-1.ipfire3.x86_64 100% >> libunistring-1.1-1.ipfire3.x86_64 100% >> bzip2-libs-1.0.8-2.ipfire3.x86_64 100% >> ncurses-libs-6.3-3.ipfire3.x86_64 100% >> libattr-2.5.1-1.ipfire3.x86_64 100% >> libksba-1.6.2-1.ipfire3.x86_64 100% >> ccache-4.7.4-1.ipfire3.x86_64 100% >> xz-5.2.8-1.ipfire3.x86_64 100% >> bzip2-1.0.8-2.ipfire3.x86_64 100% >> ncurses-6.3-3.ipfire3.x86_64 100% >> patch-2.7.6-1.ipfire3.x86_64 100% >> libacl-2.3.1-1.ipfire3.x86_64 100% >> tar-1.34-1.ipfire3.x86_64 100% >> libnl3-3.2.25-1.ipfire3.x86_64 100% >> json-c-0.16-1.ipfire3.x86_64 100% >> gdbm-1.23-1.ipfire3.x86_64 100% >> expat-2.5.0-1.ipfire3.x86_64 100% >> libcap-ng-0.8.3-1.ipfire3.x86_64 100% >> glibc-devel-2.37-2.ipfire3.x86_64 100% >> libxcrypt-4.4.33-2.ipfire3.x86_64 100% >> zlib-1.2.13-1.ipfire3.x86_64 100% >> perl-libs-5.36.0-2.1.ipfire3.x86_64 100% >> gmp-6.2.1-1.ipfire3.x86_64 100% >> sed-4.9-1.ipfire3.x86_64 100% >> hostname-3.23-1.ipfire3.x86_64 100% >> gzip-1.12-1.ipfire3.x86_64 100% >> libassuan-2.5.5-1.ipfire3.x86_64 100% >> libgcrypt-1.10.1-1.ipfire3.x86_64 100% >> readline-8.2-2.ipfire3.x86_64 100% >> python3-libs-3.11.0-1.ipfire3.x86_64 100% >> pam-1.5.2-1.1.ipfire3.x86_64 100% >> openssl-libs-3.0.8-1.ipfire3.x86_64 100% >> freetype-2.12.1-1.ipfire3.x86_64 100% >> perl-Exporter-5.77-2.1.ipfire3.noarch 100% >> mpfr-4.1.0-1.ipfire3.x86_64 100% >> libcap-2.66-1.ipfire3.x86_64 100% >> shadow-utils-4.13-1.ipfire3.x86_64 100% >> kmod-libs-30-2.ipfire3.x86_64 100% >> perl-Scalar-List-Utils-1.62-2.1.ipfire3.x86_64 100% >> gawk-5.2.1-1.ipfire3.x86_64 100% >> htop-3.2.1-1.ipfire3.x86_64 100% >> coreutils-9.1-1.ipfire3.x86_64 100% >> perl-File-Basename-2.85-2.1.ipfire3.noarch 100% >> perl-Path-Tools-3.84-2.1.ipfire3.x86_64 100% >> perl-5.36.0-2.1.ipfire3.x86_64 100% >> perl-Carp-1.33.01-2.1.ipfire3.noarch 100% >> perl-vars-1.05-2.1.ipfire3.noarch 100% >> perl-constant-1.33-2.1.ipfire3.noarch 100% >> perl-Fcntl-1.15-2.1.ipfire3.noarch 100% >> perl-POSIX-2.03-2.1.ipfire3.x86_64 100% >> perl-Symbol-1.09-2.1.ipfire3.noarch 100% >> perl-Text-Tabs+Wrap-2021.0814-2.1.ipfire3.noarch 100% >> perl-Pod-Escapes-1.07-2.1.ipfire3.noarch 100% >> perl-if-0.61.000-2.1.ipfire3.noarch 100% >> perl-Term-Cap-2.27-2.1.ipfire3.noarch 100% >> perl-Term-ANSIColor-5.01-2.1.ipfire3.noarch 100% >> perl-subs-1.04-2.1.ipfire3.noarch 100% >> perl-overloading-0.02-2.1.ipfire3.noarch 100% >> perl-mro-1.26-2.1.ipfire3.x86_64 100% >> perl-Text-ParseWords-3.31-2.1.ipfire3.noarch 100% >> perl-Storable-3.26-2.1.ipfire3.x86_64 100% >> perl-parent-0.238-2.1.ipfire3.noarch 100% >> perl-MIME-Base64-3.16-2.1.ipfire3.x86_64 100% >> perl-overload-1.35-2.1.ipfire3.noarch 100% >> perl-Getopt-Long-2.52-2.1.ipfire3.noarch 100% >> perl-Getopt-Std-1.13-2.1.ipfire3.noarch 100% >> perl-Encode-3.17-2.1.ipfire3.x86_64 100% >> perl-Class-Struct-0.66-2.1.ipfire3.noarch 100% >> perl-File-stat-1.12-2.1.ipfire3.noarch 100% >> perl-File-Path-2.18-2.1.ipfire3.noarch 100% >> perl-Compress-Raw-Zlib-2.105-2.1.ipfire3.x86_64 100% >> perl-File-Temp-0.231.100-2.1.ipfire3.noarch 100% >> perl-Compress-Raw-Bzip2-2.103-2.1.ipfire3.x86_64 100% >> perl-IO-1.50-2.1.ipfire3.x86_64 100% >> perl-IO-Compress-2.106-2.1.ipfire3.noarch 100% >> perl-SelectSaver-1.02-2.1.ipfire3.noarch 100% >> perl-Socket-2.033-2.1.ipfire3.x86_64 100% >> perl-Pod-Simple-3.43-2.1.ipfire3.noarch 100% >> perl-Pod-Usage-2.01-2.1.ipfire3.noarch 100% >> perl-podlators-4.14-2.1.ipfire3.noarch 100% >> perl-File-Find-1.40-2.1.ipfire3.noarch 100% >> libsolv-0.7.22-2.ipfire3.x86_64 100% >> libpng-1.6.39-2.ipfire3.x86_64 100% >> binutils-libs-2.40-1.ipfire3.x86_64 100% >> file-5.43-1.ipfire3.x86_64 100% >> libxml2-2.10.3-3.ipfire3.x86_64 100% >> nettle-3.8.1-2.ipfire3.x86_64 100% >> pcre-8.45-1.ipfire3.x86_64 100% >> pcre2-10.40-1.ipfire3.x86_64 100% >> libssh2-1.9.0-1.ipfire3.x86_64 100% >> openldap-libs-2.6.4-3.ipfire3.x86_64 100% >> libudev-253-5.ipfire3.x86_64 100% >> binutils-2.40-1.ipfire3.x86_64 100% >> less-608-1.ipfire3.x86_64 100% >> libcurl-7.86.0-2.1.ipfire3.x86_64 100% >> elfutils-libs-0.188-1.ipfire3.x86_64 100% >> pkg-config-0.29.2-1.ipfire3.x86_64 100% >> libuuid-devel-2.38.1-3.ipfire3.x86_64 100% >> libblkid-devel-2.38.1-3.ipfire3.x86_64 100% >> libmount-devel-2.38.1-3.ipfire3.x86_64 100% >> libarchive-3.6.1-2.ipfire3.x86_64 100% >> grep-3.8-1.ipfire3.x86_64 100% >> bash-5.2.9-1.ipfire3.x86_64 100% >> glib2-2.74.2-1.ipfire3.x86_64 100% >> fontconfig-2.13.1-1.ipfire3.x86_64 100% >> python3-3.11.0-1.ipfire3.x86_64 100% >> gobject-introspection-libs-1.74.0-3.ipfire3.x86_64 100% >> gmp-devel-6.2.1-1.ipfire3.x86_64 100% >> cairo-1.17.6-1.ipfire3.x86_64 100% >> python3-tornado-6.2.0-1.ipfire3.x86_64 100% >> python3-setproctitle-1.3.1-1.ipfire3.x86_64 100% >> python3-psutil-5.9.4-1.ipfire3.x86_64 100% >> gobject-introspection-1.74.0-3.ipfire3.x86_64 100% >> cairo-gobject-1.17.6-1.ipfire3.x86_64 100% >> libcom_err-devel-1.46.5-2.ipfire3.x86_64 100% >> libudev-devel-253-5.ipfire3.x86_64 100% >> libsmartcols-devel-2.38.1-3.ipfire3.x86_64 100% >> hwdata-0.366-1.ipfire3.noarch 100% >> libfidsk-devel-2.38.1-3.ipfire3.x86_64 100% >> systemd-libs-253-5.ipfire3.x86_64 100% >> python3-cpuinfo-9.0.0-1.ipfire3.x86_64 100% >> python3-cairo-1.23.0-2.ipfire3.x86_64 100% >> libdevmapper-devel-2.03.16-2.ipfire3.x86_64 100% >> p11-kit-0.24.1-1.ipfire3.x86_64 100% >> dbus-libs-1.15.2-1.ipfire3.x86_64 100% >> systemd-basetools-253-5.ipfire3.x86_64 100% >> util-linux-2.38.1-3.ipfire3.x86_64 100% >> cryptsetup-luks-2.6.1-1.ipfire3.x86_64 100% >> python3-dbus-1.3.2-1.ipfire3.x86_64 100% >> dbus-common-1.15.2-1.ipfire3.noarch 100% >> krb5-libs-1.20.1-1.ipfire3.x86_64 100% >> python3-systemd-235-1.ipfire3.x86_64 100% >> python3-gobject3-3.42.2-1.ipfire3.x86_64 100% >> gnutls-3.7.8-2.1.ipfire3.x86_64 100% >> python3-kerberos-1.3.1-1.ipfire3.x86_64 100% >> gnupg2-2.3.8-1.ipfire3.x86_64 100% >> gpgme-1.18.0-1.ipfire3.x86_64 100% >> systemd-253-5.ipfire3.x86_64 100% >> *** buffer overflow detected ***: terminated >=20 > This is obviously not good. Potentially this is a problem in the shell. >=20 >> The child process terminated abnormally >> dbus-broker-32-1.ipfire3.x86_64 100% >> setup-3.0-18.ipfire3.x86_64 100% >> *** buffer overflow detected ***: terminated >> The child process terminated abnormally >> bash-completion-2.11-1.ipfire3.noarch 100% >> vim-8.0.1184-2.ipfire3.x86_64 100% >> filesystem-002-4.ipfire3.x86_64 100% >> libtool-2.4.7-1.ipfire3.x86_64 100% >> gettext-0.21.1-2.1.ipfire3.x86_64 100% >> gettext-libs-0.21.1-2.1.ipfire3.x86_64 100% >> findutils-4.9.0-1.ipfire3.x86_64 100% >> pakfire-0.9.28-1.ipfire3.x86_64 100% >> gcc-12.3.0-1.ipfire3.x86_64 100% >> gcc-c++-12.3.0-1.ipfire3.x86_64 100% >> cpp-12.3.0-1.ipfire3.x86_64 100% >> ipfire-release-3.0-alpha2-7.ipfire3.noarch 100% >> *** buffer overflow detected ***: terminated >> The child process terminated abnormally >> ipfire-release-build-3.0-alpha2-7.ipfire3.noarch 100% >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 22: No such file or directory >> Could not retrieve gname for 190: No such file or directory >> Could not retrieve gname for 190: No such file or directory >=20 > Which groups do those IDs belong to on your system? Neither of those numbers are listed in the /etc/group file Regards, Adolf >=20 >> Storing Snapshot 310.5MB/s 931.4M 100% >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D >> beep-1.3-2.ipfire3.src 100% >> Running build stage 'prepare' >> [ 01:02.0875] + rm -rf '/var/tmp/pakfire-buildroot.QcH0X9/*' >> [ 01:02.0877] + mkdir -p /build/source >> [ 01:02.0879] + cd /build/source >> [ 01:02.0879] + for source in beep-1.3.tar.gz >> [ 01:02.0879] + tar --no-same-owner --no-acls --no-xattrs -xaf /usr/src/= packages/beep-1.3-2.ipfire3.src/files/beep-1.3.tar.gz >> [ 01:02.0882] + unset source >> [ 01:02.0883] + '[' -d /build/source/beep-1.3 ']' >> [ 01:02.0883] + cd /build/source/beep-1.3 >> [ 01:02.0883] + __patch --search-path=3D/usr/src/packages/beep-1.3-2.ipf= ire3.src/patches '' >> [ 01:02.0883] + paths=3D() >> [ 01:02.0883] + local paths >> [ 01:02.0883] + local path >> [ 01:02.0884] + patches=3D() >> [ 01:02.0884] + local patches >> [ 01:02.0884] + local patch >> [ 01:02.0884] + '[' 2 -gt 0 ']' >> [ 01:02.0884] + case "${1}" in >> [ 01:02.0884] + paths+=3D("${1#--search-path=3D}") >> [ 01:02.0884] + shift >> [ 01:02.0885] + '[' 1 -gt 0 ']' >> [ 01:02.0885] + case "${1}" in >> [ 01:02.0885] + patches+=3D("${1}") >> [ 01:02.0885] + shift >> [ 01:02.0885] + '[' 0 -gt 0 ']' >> [ 01:02.0885] + return 0 >> [ 01:02.0885] + mkdir -pv /build/source/beep-1.3/ >> [ 01:02.0886] + exit 0 >> [ 01:02.0886] ++ echo 'Bye bye.' >> [ 01:02.0886] Bye bye. >> Running build stage 'build' >> [ 01:02.0916] + '[' -d /build/source/beep-1.3/ ']' >> [ 01:02.0917] + cd /build/source/beep-1.3/ >> [ 01:02.0917] + make 'FLAGS=3D-O2 -g -Wall -Werror=3Dformat-security -Wp= ,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=3D3 -D_GLIBCXX_ASSERTIONS -fPIC -fst= ack-protector-all -funwind-tables -fasynchronous-unwind-tables -fstack-clash-= protection -fdebug-prefix-map=3D/build/source=3D/usr/src/debug -pipe -m64 -ma= rch=3Dx86-64-v2 -mtune=3Dgeneric -fcf-protection=3Dfull -flto=3Dauto -ffat-lt= o-objects -Wl,-O1 -Wl,--as-needed -Wl,-z,relro -Wl,-z,now' -j4 >> [ 01:02.0919] gcc -O2 -g -Wall -Werror=3Dformat-security -Wp,-U_FORTIFY_= SOURCE -Wp,-D_FORTIFY_SOURCE=3D3 -D_GLIBCXX_ASSERTIONS -fPIC -fstack-protecto= r-all -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -= fdebug-prefix-map=3D/build/source=3D/usr/src/debug -pipe -m64 -march=3Dx86-64= -v2 -mtune=3Dgeneric -fcf-protection=3Dfull -flto=3Dauto -ffat-lto-objects -W= l,-O1 -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -o beep beep.c >> [ 01:02.0923] /usr/lib64/gcc/x86_64-ipfire-linux/12.3.0/cc1: error while= loading shared libraries: libisl.so.23: cannot open shared object file: No s= uch file or directory >> [ 01:02.0926] make: *** [Makefile:14: beep] Error 1 >> Build stage 'build' failed with status 2 >> pakfire-jail /> >=20 > Okay, so this thing tried a build. There seems to a problem with GCC somewh= ere, but at least we got all the way here! >=20 > Thanks for testing :) >=20 > -Michael >=20 >> >> Regards, >> Adolf >> >>> -Michael >>>> On 4 Sep 2023, at 12:43, Adolf Belka wrote: >>>> >>>> Hi Michael, >>>> >>>> On 04/09/2023 12:29, Michael Tremer wrote: >>>>> Hello Adolf, >>>>>> On 2 Sep 2023, at 12:54, Adolf Belka wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> On 02/09/2023 13:33, Michael Tremer wrote: >>>>>>> Hello, >>>>>>> Is there an easy way to install Archlinux in a VM without running thr= ough this process manually? >>>>>>> https://wiki.archlinux.org/title/Installation_guide >>>>>> Unfortunately not that I am aware of, although it is not that complica= ted for just a command line based system. >>>>>> Arch Linux don't have an installer anymore. >>>>>> >>>>>> The only thing I can think of is that if you are able to use VirtualBo= x, I could create a VirtualBox text interface only vm which I could then expo= rt from my system as a file to send to you or place in my dropbox system for = you to upload. >>>>>> >>>>>> Would that be of any use? >>>>> Probably, but I suppose we will both spend the same time then. >>>>> I will just do the process as described on that wiki page. I was just s= urprised how manual it all is. >>>> I have found an Arch Linux wiki page about an installation helper. That = might make it a bit easier. It is not graphical but text based but it takes y= ou through and asks the various questions. Apparently the defaults are differ= ent than described in the normal installation guide. >>>> >>>> https://wiki.archlinux.org/title/Archinstall >>>> >>>> Regards, >>>> >>>> Adolf. >>>>> Best, >>>>> -Michael >>>>>> >>>>>> Regards, >>>>>> Adolf. >>>>>>> It might be quicker for me to reproduce the problem. >>>>>>> -Michael >>>>>>>> On 2 Sep 2023, at 12:11, Adolf Belka wrot= e: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> On 02/09/2023 13:02, Michael Tremer wrote: >>>>>>>>> Hello, >>>>>>>>>> On 2 Sep 2023, at 12:00, Adolf Belka wr= ote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 02/09/2023 12:53, Michael Tremer wrote: >>>>>>>>>>> Hello Adolf, >>>>>>>>>>>> On 2 Sep 2023, at 11:49, Adolf Belka = wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi Michael, >>>>>>>>>>>> >>>>>>>>>>>> I went back to pakfire and looked through the config.log file fr= om 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 /var/c= ache/pakfire are not present on the system. >>>>>>>>>>> That should be correct. Pakfire should create those directories i= tself if it is running as root. >>>>>>>>>>> For unprivileged users, it will create a cache directory in the u= ser=E2=80=99s home, because we cannot write to /var/lib/=E2=80=A6, etc. >>>>>>>>>>>> I also read through the INSTALL file in the pakfire directory an= d it said the following were required. >>>>>>>>>>>> >>>>>>>>>>>> Requirements: >>>>>>>>>>>> * Python 2.6 or greater (not Python 3.x) >>>>>>>>>>>> * python-argsparse (included in Python 2.7) >>>>>>>>>>>> * libcap >>>>>>>>>>>> * libsolv >>>>>>>>>>>> * xz >>>>>>>>>>>> * beecrypt (requires libgomp) >>>>>>>>>>>> * popt >>>>>>>>>>>> * libelf >>>>>>>>>>>> * elfutils >>>>>>>>>>> This is old and I will remove this as soon as possible :) >>>>>>>>>>>> I don't have beecrypt or libgomp installed and not available fro= m Arch 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 availa= ble on Arch Linux. >>>>>>>>>>>> >>>>>>>>>>>> Are the above requirements correct or out of date and should be = ignored? >>>>>>>>>>> Please ignore. If configure went through without complaining, you= have everything you need. >>>>>>>>>>> What I find very interesting are those SQL errors. When Pakfire s= tarts, it is creating an internal SQLite database to store package informatio= n and other things=E2=80=A6 And it looks like the database is there, but the = schema is not being created. And even weirder is that Pakfire does not abort = there=E2=80=A6 >>>>>>>>>>> Which versions of libarchive and SQLite do you have? >>>>>>>>>> sqlite 3.43.0 >>>>>>>>>> libarchive 3.7.1 >>>>>>>>> I have libarchive 3.6.2 and sqlite 3.40.1, but I don=E2=80=99t thin= k there are any significant differences here. >>>>>>>>> Could you please pull again and check if the message about the miss= ing file is gone? >>>>>>>> Did the pull, then re-ran the whole build instruction set again. I d= idn't do a sudo make uninstall first. >>>>>>>> >>>>>>>> Result was exactly the same error message. Nothing changed. >>>>>>>> >>>>>>>> sudo pakfire-builder build beep/beep.nm >>>>>>>> Database Error: SQL logic error: no such table: settings in "SELECT = val FROM settings WHERE key =3D ?" >>>>>>>> Database Error: SQL logic error: no such table: settings in "SELECT = val FROM settings WHERE key =3D ?" >>>>>>>> Package Database: testing 100% | 1.6M 00:00 >>>>>>>> Could not read next file: /var/lib/pakfire/local/ipfire/3: Cannot st= at >>>>>>>> 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 ex= ception set >>>>>>>> >>>>>>>> Regards, >>>>>>>> Adolf. >>>>>>>>> -Michael >>>>>>>>>> >>>>>>>>>> Adolf. >>>>>>>>>>> -Michael >>>>>>>>>>>> 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 thi= s is all working as an unprivileged user at the moment. I think there might b= e a little bit of work ahead to make it work well. >>>>>>>>>>>>> Yes, I was using an unprivileged user. I always do that unless = the instructions say to use sudo or if the program comes back and says it mus= t be run with root privileges. Or if I know that it has to be run with sudo l= ike make install. >>>>>>>>>>>>> >>>>>>>>>>>>> So tried it again with sudo and the error message was exactly t= he 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-bui= lder 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: Cann= ot stat >>>>>>>>>>>>> >>>>>>>>>>>>> I checked and there is no pakfire directory under /var/lib/ >>>>>>>>>>>>> Is there supposed to be? Maybe something is not working right d= uring the pakfire build on my system. The build is working okay but maybe som= ething that is required for the execution is not being correctly 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 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 val FROM settings WHERE key =3D ?" >>>>>>>>>>>>>>> Database Error: SQL logic error: no such table: settings in "= SELECT val FROM 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: Ca= nnot stat >>>>>>>>>>>>>>> OSError: [Errno 25] Inappropriate ioctl for device >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The above exception was the direct cause of the following exc= eption: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 wit= h an 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 wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Michael, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> When I built pakfire I just installed the programs that w= ere flagged up as missing during the configure section. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I have now gone through the filenames you listed from deb= ian and eventually 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 which is lzlib in Arch Linux. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Just to check, I installed lzlib and re-did the make chec= k 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 finall= y have a fix for the test suite: >>>>>>>>>>>>>>>>>> https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h= =3D9eef0cb603bc51a5b34f042fced6e4d0bfa8d9d8 >>>>>>>>>>>>>>>>>> https://git.ipfire.org/?p=3Dpakfire.git;a=3Dcommitdiff;h= =3Dc54bafa7e74dbcb5b07bafe8fadf2ca830fd93d7 >>>>>>>>>>>>>>>>>> Please just run =E2=80=9Cgit pull=E2=80=9D, then =E2=80=9C= make=E2=80=9D again 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 che= ck out the IPFire 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 th= e tests/libpakfire 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 e= mail me the =E2=80=9C*.log=E2=80=9D files in the test/libpakfire directory? L= et=E2=80=99s see what is going wrong there. For me a few tests fail, but a fe= w should run just 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 progressbar.py >>>>>>>>>>>>>>>>>>>>>> Further running of make check didn't change anything. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> make install went fine and after that I can run pakfir= e-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 e= veryone 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 distribu= tion or something=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 distr= ibution 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 use the time to find any issues that might occur on other dis= tributions 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 depend= encies (yes it is quite a lot): >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> * asciidoc, autoconf, automake, bison, build-essentia= l, flex, intltool, libarchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-d= ev, libgpgme-dev, libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev, lib= nl-3-dev, libnl-route-3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, li= bsolv-dev, libsqlite3-dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, = pkg-config, python3-cpuinfo, python3-kerberos, python3-tornado, python3-psuti= l, python3-setproctitle, uuid-dev >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I have no idea what the package names will be for you= r distribution, but I am sure you will all figure it out :) >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> You can use the usual three-clause build process afte= r generating the configure script: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> ./autogen.sh >>>>>>>>>>>>>>>>>>>>>>> ./configure =E2=80=94-prefix=3D/usr =E2=80=94-sy= sconfdir=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 p= oint and please file a bug if changes are required to make Pakfire work on yo= ur 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 >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --=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 >=20 >=20 --=20 Sent from my laptop --===============8485841923471336237==--