From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer <michael.tremer@ipfire.org> To: development@lists.ipfire.org Subject: Re: Feedback on pakfire-3 testing Date: Fri, 10 Jan 2025 14:00:59 +0000 Message-ID: <F68735A0-CF2A-4344-A10B-791125CE7226@ipfire.org> In-Reply-To: <7060840f-5e8d-47af-a9a1-fa4b88f4d8d8@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4644055479019624762==" List-Id: <development.lists.ipfire.org> --===============4644055479019624762== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, Thank you for giving this a test. > On 10 Jan 2025, at 13:51, Adolf Belka <adolf.belka(a)ipfire.org> wrote: >=20 > Hi Michael, >=20 > I did a fresh git clone of the pakfire repo and built it. >=20 > Then ran builds of beep, libxcrypt and openssl. All completed successfully. That is good news. > beep took 15 secs, libxcrypt 50 secs and openssl 13 mins. Cool. This sounds about right. The first build should have created a snapshot= may so that running the second would have started much faster? > In the autogen.sh part of the pakfire build I did see a couple of warnings = but it didn't stop the pakfire build from completing successfully. >=20 >=20 > You should update your 'aclocal.m4' by running aclocal. > configure.ac:191: warning: AC_PROG_LEX without either yywrap or noyywrap is= obsolete >=20 > parallel-tests: installing 'build-aux/test-driver' > Makefile.am:1175: warning: variable 'TESTSUITE_LDFLAGS' is defined but no p= rogram or > Makefile.am:1175: library has 'TESTSUITE' as canonical name (possible typo) Yes, the first one I have no idea how to get rid of, the second is probably j= ust renaming the variable. > 8 from 30 tests in the make check section failed. That is not right. Could you check the *.log files of the individual ones and= see what is going wrong? > In the package build stage for all three packages that I tested I got the f= ollowing:- >=20 > sudo pakfire-builder build beep/beep.nm > Scanning local 00:00 60/60 > 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 Hmm, this is not right=E2=80=A6 As the files checked out by another user with= ID 1000? > beep-1.4.12.tar.gz 87k 87kB/s 00:01 0% > beep-1.4.12-1.ipfire3.src 88k 0B/s 100% > Building beep-1.4.12-1.ipfire3.src (eed8a645-191c-46d4-91a5-dfc82aec9829)... >=20 >=20 > python3-gobject3-3.46.0-1.ipfire3.x86_64 100% > # This file is part of systemd. > # > # systemd is free software; you can redistribute it and/or modify it > # under the terms of the GNU Lesser General Public License as published by > # the Free Software Foundation; either version 2.1 of the License, or > # (at your option) any later version. >=20 > # The superuser > g root 0 - - > u root 0:0 "Super User" /root >=20 > # The nobody user/group for NFS file systems > g nobody 65534 - - > u nobody 65534:65534 "Kernel Overflow User" - >=20 > # Administrator group: can *see* more than normal users > g adm 4 - - >=20 > # Administrator group: can *do* more than normal users > g wheel 10 - - >=20 > # Access to shared database of users on the system > g utmp 22 - - >=20 > # Physical and virtual hardware access groups > g audio 63 - - > g cdrom 11 - - > g dialout 18 - - > g disk 6 - - > g input 104 - - > g kmem 9 - - > g kvm 36 - - > g lp 7 - - > g render 105 - - > g sgx 106 - - > g tape 33 - - > g tty 5 - - > g video 39 - - >=20 > # Default group for normal users > g users 100 - - > # This file is part of systemd. > # > # systemd is free software; you can redistribute it and/or modify it > # under the terms of the GNU Lesser General Public License as published by > # the Free Software Foundation; either version 2.1 of the License, or > # (at your option) any later version. >=20 > u systemd-coredump - "systemd Core Dumper" > # This file is part of systemd. > # > # systemd is free software; you can redistribute it and/or modify it > # under the terms of the GNU Lesser General Public License as published by > # the Free Software Foundation; either version 2.1 of the License, or > # (at your option) any later version. >=20 > g systemd-journal 190 - > # This file is part of systemd. > # > # systemd is free software; you can redistribute it and/or modify it > # under the terms of the GNU Lesser General Public License as published by > # the Free Software Foundation; either version 2.1 of the License, or > # (at your option) any later version. >=20 > u systemd-oom - "systemd Userspace OOM Killer" This is from a systemd feature that currently seems to be very broken, I will= put this on my TODO list. > systemd-254-3.ipfire3.x86_64 100% > *** buffer overflow detected ***: terminated This is also a problem inside the build environment and I believe rebuilding = systemd fixes it. > The child process terminated abnormally with status code 11 > dbus-broker-32-1.ipfire3.x86_64 100% > uuidd-2.39.2-3.ipfire3.x86_64 100% > setup-3.0-19.ipfire3.noarch 100% > *** buffer overflow detected ***: terminated > The child process terminated abnormally with status code 11 > sudo-1.9.14p3-2.ipfire3.x86_64 100% > *** buffer overflow detected ***: terminated > The child process terminated abnormally with status code 11 > bash-completion-2.11-1.ipfire3.noarch 100% > filesystem-002-5.ipfire3.x86_64 0% > groff-1.22.4-1.ipfire3.x86_64 100% > openssh-9.4p1-1.ipfire3.x86_64 100% > smartmontools-7.4-1.ipfire3.x86_64 100% > mc-4.8.29-3.ipfire3.x86_64 100% > libtool-2.4.7-2.ipfire3.x86_64 100% > gettext-0.21.1-5.1.ipfire3.x86_64 100% > gettext-libs-0.21.1-5.1.ipfire3.x86_64 100% > findutils-4.9.0-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% > man-db-2.11.2-1.ipfire3.x86_64 100% > *** buffer overflow detected ***: terminated > The child process terminated abnormally with status code 11 > ipfire-release-build-3.0-alpha2-10.ipfire3.noarch 0% > pakfire-0.9.29-1.ipfire3.x86_64 100% > ipfire-release-3.0-alpha2-10.ipfire3.noarch 100% > *** buffer overflow detected ***: terminated > The child process terminated abnormally with status code 11 > Running in chroot, ignoring command 'start' > Running build stage 'prepare' >=20 > I recall you saying that running a repeat of the build should result in a q= uicker build. I have not found that. It has stayed very similar in time in al= l three cases. Can you run =E2=80=9Cpakfire-build snapshot update=E2=80=9D and see if that c= reates the snapshot? Maybe I didn=E2=80=99t fully think this through when it = is being created. -Michael >=20 > Regards, >=20 > Adolf. >=20 --===============4644055479019624762==--