From: catalyst@nightheron.gentoo.org
To: releng@gentoo.org,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-minimal.spec
Date: Mon, 29 Jun 2020 04:11:39 +0000 (UTC) [thread overview]
Message-ID: <20200629041139.4DB1020774@nightheron.gentoo.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 12986 bytes --]
>>> Recording sys-boot/grub in "world" favorites file...
* Messages for package sys-power/acpid-2.0.32-r1:
* Unable to find kernel sources at /usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Messages for package acct-group/dhcp-0:
* Adding group 'dhcp' to your system ...
* - Groupid: 300
* Messages for package sys-power/acpid-2.0.32-r1:
*
* You may wish to read the Gentoo Linux Power Management Guide,
* which can be found online at:
* https://wiki.gentoo.org/wiki/Power_management/Guide
*
* Messages for package acct-user/dhcp-0:
* Adding user 'dhcp' to your system ...
* - Userid: 300
* - Shell: /sbin/nologin
* - Home: /dev/null
* - Groups: dhcp
* - GECOS: added by portage for dhcp
* Updating comment for user 'dhcp' ...
* - Comment: user for dhcp daemon
* Messages for package sys-boot/grub-2.04-r1:
* For information on how to configure GRUB2 please refer to the guide:
* https://wiki.gentoo.org/wiki/GRUB2_Quick_Start
*
* You may consider installing the following optional packages:
* sys-boot/os-prober for Detect other operating systems (grub-mkconfig)
* dev-libs/libisoburn for Create rescue media (grub-mkrescue)
* sys-fs/mdadm for Enable RAID device detection
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp/stage4-chroot.sh from the chroot
removing /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp/chroot-functions.sh from the chroot
29 Jun 2020 04:09:01 UTC: NOTICE : --- Running action sequence: build_kernel
NOTICE:catalyst:--- Running action sequence: build_kernel
Copying pre-kmerge.sh to /tmp
copying pre-kmerge.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp
Ensure the file has the executable bit set
Running pre-kmerge.sh in chroot:
chroot /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z /tmp/pre-kmerge.sh
>>> Regenerating /etc/ld.so.cache...
emerge --quiet --usepkg --buildpkg --binpkg-respect-use=y --newuse --oneshot genkernel
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-kernel/linux-firmware-20200619
>>> Emerging binary (1 of 4) app-arch/cpio-2.12-r1::gentoo
>>> Installing (1 of 4) app-arch/cpio-2.12-r1::gentoo
>>> Emerging binary (2 of 4) sys-devel/autoconf-archive-2018.03.13::gentoo
>>> Emerging (3 of 4) sys-kernel/linux-firmware-20200619::gentoo
>>> Installing (2 of 4) sys-devel/autoconf-archive-2018.03.13::gentoo
>>> Installing (3 of 4) sys-kernel/linux-firmware-20200619::gentoo
>>> Emerging (4 of 4) sys-kernel/genkernel-4.0.9::gentoo
>>> Failed to emerge sys-kernel/genkernel-4.0.9, Log file:
>>> '/var/tmp/portage/sys-kernel/genkernel-4.0.9/temp/build.log'
--2020-06-29 04:10:35-- http://mirror.bytemark.co.uk/gentoo/distfiles/90/dropbear-2020.79.tar.bz2
Resolving mirror.bytemark.co.uk... 2001:41c8:20:5fc::12, 2001:41c8:20:5e6::150, 80.68.83.150, ...
Connecting to mirror.bytemark.co.uk|2001:41c8:20:5fc::12|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-06-29 04:10:35 ERROR 404: Not Found.
--2020-06-29 04:10:35-- http://mirror.ovh.net/gentoo-distfiles/distfiles/layout.conf
Resolving mirror.ovh.net... failed: Name or service not known.
wget: unable to resolve host address ‘mirror.ovh.net’
!!! Couldn't download '.layout.conf.mirror.ovh.net'. Aborting.
--2020-06-29 04:10:36-- http://mirror.ovh.net/gentoo-distfiles/distfiles/dropbear-2020.79.tar.bz2
Resolving mirror.ovh.net... failed: Name or service not known.
wget: unable to resolve host address ‘mirror.ovh.net’
--2020-06-29 04:10:36-- http://distfiles.gentoo.org/distfiles/90/dropbear-2020.79.tar.bz2
Resolving distfiles.gentoo.org... 2600:3404:200:237::2, 2600:3402:200:227::2, 2605:bc80:3010::134, ...
Connecting to distfiles.gentoo.org|2600:3404:200:237::2|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-06-29 04:10:36 ERROR 404: Not Found.
--2020-06-29 04:10:36-- https://matt.ucc.asn.au/dropbear/releases/dropbear-2020.79.tar.bz2
Resolving matt.ucc.asn.au... 2405:3c00:5200:100::18, 130.95.13.18
Connecting to matt.ucc.asn.au|2405:3c00:5200:100::18|:443... connected.
Unable to establish SSL connection.
!!! Couldn't download 'dropbear-2020.79.tar.bz2'. Aborting.
* Fetch failed for 'sys-kernel/genkernel-4.0.9', Log file:
* '/var/tmp/portage/sys-kernel/genkernel-4.0.9/temp/build.log'
* Messages for package sys-kernel/linux-firmware-20200619:
* Building using saved configfile "/etc/portage/savedconfig/sys-kernel/linux-firmware"
* Your configuration for sys-kernel/linux-firmware-20200619 has been saved in
* "/etc/portage/savedconfig/sys-kernel/linux-firmware" for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* This package will overwrite one or more files that may belong to other
* packages (see list below).
*
* Detected file collision(s):
*
* /etc/portage/savedconfig/sys-kernel/linux-firmware
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'sys-kernel/linux-firmware-20200619' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* USE=savedconfig is active. You must handle file collisions manually.
* If you are only interested in particular firmware files, edit the saved
* configfile and remove those that you do not want.
* Messages for package sys-kernel/genkernel-4.0.9:
* Fetch failed for 'sys-kernel/genkernel-4.0.9', Log file:
* '/var/tmp/portage/sys-kernel/genkernel-4.0.9/temp/build.log'
29 Jun 2020 04:11:38 UTC: ERROR : CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/tmp/portage is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/tmp/portage is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: ERROR : CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1589, in build_kernel
env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
ERROR:catalyst:CatalystError: build aborting due to kernel build error.
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1589, in build_kernel
env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
29 Jun 2020 04:11:39 UTC: ERROR : Exception running action sequence build_kernel
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1589, in build_kernel
env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1597, in build_kernel
print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
ERROR:catalyst:Exception running action sequence build_kernel
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1589, in build_kernel
env=self.env)
File "/usr/lib64/python3.6/site-packages/catalyst/support.py", line 54, in cmd
print_traceback=False)
catalyst.support.CatalystError: cmd(['/usr/share/catalyst/targets/stage4/stage4-controller.sh', 'pre-kmerge']) exited 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1471, in run
getattr(self, x)()
File "/usr/lib64/python3.6/site-packages/catalyst/base/stagebase.py", line 1597, in build_kernel
print_traceback=True)
catalyst.support.CatalystError: build aborting due to kernel build error.
29 Jun 2020 04:11:39 UTC: NOTICE : Cleaning up... Running unbind()
NOTICE:catalyst:Cleaning up... Running unbind()
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp/kerncache is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/tmp/kerncache is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/cache/binpkgs is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/cache/binpkgs is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/run is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/run is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev/shm does not exist. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev/shm does not exist. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev/pts does not exist. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev/pts does not exist. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/tmp/portage is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/tmp/portage is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/cache/distfiles is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/cache/distfiles is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/db/repos/gentoo is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/var/db/repos/gentoo is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/dev is not a mount point. Skipping
29 Jun 2020 04:11:39 UTC: NOTICE : /release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/proc is not a mount point. Skipping
NOTICE:catalyst:/release/buildroot/amd64-dev/tmp/hardened/stage4-amd64-hardened+minimal-20200628T214504Z/proc is not a mount point. Skipping
Command exited with non-zero status 2
166.48user 36.97system 4:06.59elapsed 82%CPU (0avgtext+0avgdata 63300maxresident)k
84976inputs+4361312outputs (13major+4532790minor)pagefaults 0swaps
Full build log at /release/tmp/run/catalyst-auto.20200628T214504Z.NnxuZQ/log/hardened_stage4-minimal.log
next reply other threads:[~2020-06-29 4:11 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 4:11 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-28 3:00 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/stage4-minimal.spec catalyst
2020-09-21 3:00 catalyst
2020-09-14 3:00 catalyst
2020-09-07 3:00 catalyst
2020-08-31 3:00 catalyst
2020-08-24 3:00 catalyst
2020-08-17 3:00 catalyst
2020-08-10 3:02 catalyst
2020-08-03 3:00 catalyst
2020-07-27 3:00 catalyst
2020-07-20 3:00 catalyst
2020-07-13 3:00 catalyst
2020-07-06 3:00 catalyst
2020-06-29 3:00 catalyst
2020-06-22 3:00 catalyst
2020-06-18 0:33 catalyst
2020-06-15 3:00 catalyst
2020-06-15 0:35 catalyst
2020-06-08 3:00 catalyst
2020-06-01 3:00 catalyst
2020-05-25 3:00 catalyst
2020-05-18 3:00 catalyst
2020-05-15 14:29 catalyst
2020-05-12 16:56 catalyst
2020-05-11 16:26 catalyst
2020-05-11 11:34 catalyst
2020-05-11 3:01 catalyst
2020-05-04 3:13 catalyst
2020-04-27 3:00 catalyst
2020-04-13 4:01 catalyst
2020-04-06 3:58 catalyst
2020-03-30 3:59 catalyst
2020-03-23 3:57 catalyst
2020-03-16 3:56 catalyst
2020-03-09 3:57 catalyst
2020-03-02 3:54 catalyst
2020-02-24 3:44 catalyst
2020-02-17 3:42 catalyst
2020-02-10 3:37 catalyst
2020-02-03 3:38 catalyst
2020-01-27 3:38 catalyst
2020-01-20 3:39 catalyst
2020-01-13 3:40 catalyst
2019-12-30 6:15 catalyst
2019-12-09 1:58 catalyst
2019-07-16 3:38 catalyst
2019-07-16 3:01 catalyst
2019-07-16 2:56 catalyst
2019-07-16 2:51 catalyst
2019-05-31 11:23 catalyst
2019-05-30 11:34 catalyst
2019-05-29 17:54 catalyst
2019-05-27 11:54 catalyst
2018-09-25 3:03 catalyst
2018-09-24 20:07 catalyst
2018-08-14 16:27 catalyst
2018-08-11 9:51 catalyst
2018-08-11 9:48 catalyst
2018-07-16 22:32 catalyst
2018-07-16 22:31 catalyst
2018-07-02 9:49 catalyst
2018-06-28 5:18 catalyst
2018-06-25 16:21 catalyst
2018-06-18 6:17 catalyst
2018-06-15 22:17 catalyst
2018-05-30 2:37 catalyst
2018-02-21 0:01 catalyst
2018-02-06 10:15 catalyst
2018-02-06 3:20 catalyst
2018-02-03 21:34 catalyst
2018-02-02 4:27 catalyst
2018-01-05 9:23 catalyst
2018-01-04 13:37 catalyst
2018-01-01 11:17 catalyst
2017-12-28 18:04 catalyst
2017-12-26 21:58 catalyst
2017-12-24 21:59 catalyst
2017-12-23 3:45 catalyst
2017-12-21 21:58 catalyst
2017-12-19 21:54 catalyst
2017-12-17 22:45 catalyst
2017-12-15 7:26 catalyst
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=20200629041139.4DB1020774@nightheron.gentoo.org \
--to=catalyst@nightheron.gentoo.org \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=releng@gentoo.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