From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Feedback on pakfire-3 testing
Date: Fri, 10 Jan 2025 14:51:40 +0100 [thread overview]
Message-ID: <7060840f-5e8d-47af-a9a1-fa4b88f4d8d8@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 6003 bytes --]
Hi Michael,
I did a fresh git clone of the pakfire repo and built it.
Then ran builds of beep, libxcrypt and openssl. All completed successfully.
beep took 15 secs, libxcrypt 50 secs and openssl 13 mins.
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.
You should update your 'aclocal.m4' by running aclocal.
configure.ac:191: warning: AC_PROG_LEX without either yywrap or noyywrap is obsolete
parallel-tests: installing 'build-aux/test-driver'
Makefile.am:1175: warning: variable 'TESTSUITE_LDFLAGS' is defined but no program or
Makefile.am:1175: library has 'TESTSUITE' as canonical name (possible typo)
8 from 30 tests in the make check section failed.
In the package build stage for all three packages that I tested I got the following:-
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
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)...
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.
# The superuser
g root 0 - -
u root 0:0 "Super User" /root
# The nobody user/group for NFS file systems
g nobody 65534 - -
u nobody 65534:65534 "Kernel Overflow User" -
# Administrator group: can *see* more than normal users
g adm 4 - -
# Administrator group: can *do* more than normal users
g wheel 10 - -
# Access to shared database of users on the system
g utmp 22 - -
# 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 - -
# 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.
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.
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.
u systemd-oom - "systemd Userspace OOM Killer"
systemd-254-3.ipfire3.x86_64 100%
*** buffer overflow detected ***: terminated
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'
I recall you saying that running a repeat of the build should result in a quicker build. I have not found that. It has stayed very similar in time in all three cases.
Regards,
Adolf.
next reply other threads:[~2025-01-10 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:51 Adolf Belka [this message]
2025-01-10 14:00 ` Michael Tremer
2025-01-10 14:35 ` Adolf Belka
2025-01-10 14:59 ` Adolf Belka
2025-01-10 15:18 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7060840f-5e8d-47af-a9a1-fa4b88f4d8d8@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox