From: catalyst@lantean.jmbsvicetto.name
To: jmbsvicetto@gmail.com,gentoo-releng-autobuilds@lists.gentoo.org
Subject: [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/admincd-stage2.spec
Date: Mon, 21 Dec 2015 02:40:36 +0000 (UTC) [thread overview]
Message-ID: <20151221024036.941B5E006E@lantean.jmbsvicetto.name> (raw)
*
* Detected file collision(s):
*
* /lib/firmware/atmsar11.fw
* /lib/firmware/tigon/tg3_tso.bin
* /lib/firmware/tigon/tg3_tso5.bin
* /lib/firmware/tigon/tg3.bin
* /lib/firmware/yamaha/ds1_ctrl.fw
* /lib/firmware/yamaha/ds1e_ctrl.fw
* /lib/firmware/yamaha/ds1_dsp.fw
* /lib/firmware/tehuti/bdx.bin
* /lib/firmware/ositech/Xilinx7OD.bin
* /lib/firmware/bnx2/bnx2-rv2p-09-6.0.17.fw
* /lib/firmware/bnx2/bnx2-rv2p-09ax-6.0.17.fw
* /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw
* /lib/firmware/bnx2/bnx2-rv2p-06-6.0.15.fw
* /lib/firmware/bnx2/bnx2-mips-09-6.2.1b.fw
* /lib/firmware/bnx2/bnx2-mips-06-6.2.1.fw
* /lib/firmware/bnx2/bnx2-mips-06-6.2.3.fw
* /lib/firmware/3com/typhoon.bin
* /lib/firmware/adaptec/starfire_tx.bin
* /lib/firmware/adaptec/starfire_rx.bin
* /lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
* /lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
* /lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
* /lib/firmware/acenic/tg2.bin
* /lib/firmware/acenic/tg1.bin
* /lib/firmware/cxgb3/t3b_psram-1.1.0.bin
* /lib/firmware/cxgb3/ael2005_opt_edc.bin
* /lib/firmware/cxgb3/ael2020_twx_edc.bin
* /lib/firmware/cxgb3/ael2005_twx_edc.bin
* /lib/firmware/cxgb3/t3c_psram-1.1.0.bin
* /lib/firmware/e100/d101m_ucode.bin
* /lib/firmware/e100/d102e_ucode.bin
* /lib/firmware/e100/d101s_ucode.bin
* /lib/firmware/sun/cassini.bin
* /lib/firmware/ess/maestro3_assp_kernel.fw
* /lib/firmware/ess/maestro3_assp_minisrc.fw
* /lib/firmware/kaweth/new_code_fix.bin
* /lib/firmware/kaweth/trigger_code.bin
* /lib/firmware/kaweth/trigger_code_fix.bin
* /lib/firmware/kaweth/new_code.bin
* /lib/firmware/cis/tamarack.cis
* /lib/firmware/cis/PE-200.cis
* /lib/firmware/cis/PE520.cis
* /lib/firmware/cis/PCMLM28.cis
* /lib/firmware/cis/SW_7xx_SER.cis
* /lib/firmware/cis/SW_8xx_SER.cis
* /lib/firmware/cis/LA-PCM.cis
* /lib/firmware/cis/MT5634ZLX.cis
* /lib/firmware/cis/COMpad4.cis
* /lib/firmware/cis/3CCFEM556.cis
* /lib/firmware/cis/RS-COM-2P.cis
* /lib/firmware/cis/DP83903.cis
* /lib/firmware/cis/SW_555_SER.cis
* /lib/firmware/cis/COMpad2.cis
* /lib/firmware/cis/3CXEM556.cis
* /lib/firmware/cis/NE2K.cis
* /lib/firmware/advansys/mcode.bin
* /lib/firmware/advansys/3550.bin
* /lib/firmware/advansys/38C1600.bin
* /lib/firmware/advansys/38C0800.bin
* /lib/firmware/qlogic/1280.bin
* /lib/firmware/qlogic/12160.bin
* /lib/firmware/qlogic/1040.bin
* /lib/firmware/korg/k1212.dsp
*
* 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-20150812' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* If you are only interested in particular firmware files, edit the saved
* configfile and remove those that you do not want.
* Messages for package media-sound/alsa-utils-1.0.29:
*
* To take advantage of the init script, and automate the process of
* saving and restoring sound-card mixer levels you should
* add alsasound to the boot runlevel. You can do this as
* root like so:
* # rc-update add alsasound boot
*
* The ALSA core should be built into the kernel or loaded through other
* means. There is no longer any modular auto(un)loading in alsa-utils.
* Messages for package app-accessibility/espeakup-0.71:
* To get espeakup to start automatically, it is currently recommended
* that you add it to the default run level, by giving the following
* command as root.
*
* rc-update add espeakup default
*
* You can also set a default voice now for espeakup.
* See /etc/conf.d/espeakup for how to do this.
^[[32;01m*^[[0m <<< Callback exit status: 0
^[[32;01m*^[[0m busybox: >> Applying patches...
^[[32;01m*^[[0m - 1.18.1-openvt.diff
^[[32;01m*^[[0m - busybox-1.20.1-mdstart.patch
^[[32;01m*^[[0m - busybox-1.20.2-bunzip2.patch
^[[32;01m*^[[0m - busybox-1.20.2-glibc-sys-resource.patch
^[[32;01m*^[[0m - busybox-1.20.2-modprobe.patch
^[[32;01m*^[[0m - busybox-1.7.4-signal-hack.patch
^[[32;01m*^[[0m busybox: >> Configuring...
^[[32;01m*^[[0m busybox: >> Compiling...
^[[32;01m*^[[0m busybox: >> Copying to cache...
^[[32;01m*^[[0m initramfs: >> Initializing...
^[[32;01m*^[[0m >> Appending base_layout cpio data...
^[[32;01m*^[[0m >> Appending auxilary cpio data...
^[[32;01m*^[[0m >> Copying keymaps
^[[32;01m*^[[0m >> Appending busybox cpio data...
^[[32;01m*^[[0m >> Appending lvm cpio data...
^[[32;01m*^[[0m LVM: Adding support (compiling binaries)...
^[[32;01m*^[[0m lvm: >> Applying patches...
^[[32;01m*^[[0m - lvm2-2.02.72-no-export-dynamic.patch
^[[32;01m*^[[0m lvm: >> Configuring...
^[[32;01m*^[[0m lvm: >> Compiling...
^[[32;01m*^[[0m >> Copying to bincache...
^[[32;01m*^[[0m >> Appending dmraid cpio data...
^[[32;01m*^[[0m DMRAID: Adding support (compiling binaries)...
^[[32;01m*^[[0m lvm: >> Using cache
^[[32;01m*^[[0m dmraid: >> Configuring...
^[[32;01m*^[[0m dmraid: >> Compiling...
^[[32;01m*^[[0m >> Copying to bincache...
^[[32;01m*^[[0m >> Appending mdadm cpio data...
^[[32;01m*^[[0m MDADM: Skipping inclusion of mdadm.conf
^[[32;01m*^[[0m MDADM: Adding support (compiling binaries)...
^[[32;01m*^[[0m mdadm: >> Compiling...
^[[32;01m*^[[0m >> Copying to bincache...
^[[32;01m*^[[0m >> Appending modules cpio data...
^[[32;01m*^[[0m >> Appending blkid cpio data...
^[[32;01m*^[[0m >> Appending modprobed cpio data...
^[[32;01m*^[[0m >> Appending linker cpio data...
^[[32;01m*^[[0m >> Finalizing cpio...
^[[32;01m*^[[0m >> Compressing cpio data (.xz)...
^[[32;01m*^[[0m Creating minimal kernel package
^[[32;01m*^[[0m Creating modules package
^[[32;01m*^[[0m
^[[32;01m*^[[0m Kernel compiled successfully!
^[[32;01m*^[[0m
^[[32;01m*^[[0m Required Kernel Parameters:
^[[32;01m*^[[0m root=/dev/$ROOT
^[[32;01m*^[[0m
^[[32;01m*^[[0m Where $ROOT is the device node for your root partition as the
^[[32;01m*^[[0m one specified in /etc/fstab
^[[32;01m*^[[0m
^[[32;01m*^[[0m If you require Genkernel's hardware detection features; you MUST
^[[32;01m*^[[0m tell your bootloader to use the provided INITRAMFS file.
^[[33;01m*^[[0m WARNING... WARNING... WARNING...
^[[33;01m*^[[0m Additional kernel cmdline arguments that *may* be required to boot properly...
^[[33;01m*^[[0m add "dolvm" for lvm support
^[[33;01m*^[[0m add "dodmraid" for dmraid support
^[[33;01m*^[[0m add "domdadm" for RAID support
^[[33;01m*^[[0m or "dodmraid=<additional options>"
^[[33;01m*^[[0m With support for several ext* filesystems available, it may be needed to
^[[33;01m*^[[0m add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
^[[32;01m*^[[0m Do NOT report kernel bugs as genkernel bugs unless your bug
^[[32;01m*^[[0m is about the default genkernel configuration...
^[[32;01m*^[[0m
^[[32;01m*^[[0m Make sure you have the latest ~arch genkernel before reporting bugs.
removing /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp/kmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp/chroot-functions.sh from the chroot
Copying post-kmerge.sh to /tmp
copying post-kmerge.sh to /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp
copying chroot-functions.sh to /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp
Ensure the file has the executable bit set
Running post-kmerge.sh in chroot:
chroot /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219 /tmp/post-kmerge.sh
removing /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp/post-kmerge.sh from the chroot
removing /home/release/buildroot/amd64-dev/tmp/hardened/livecd-stage2-amd64-20151219/tmp/chroot-functions.sh from the chroot
21 Dec 2015 02:40:35 UTC: NOTICE : --- Running action sequence: bootloader
touch: cannot touch '/home/release/buildroot/amd64-dev/builds/hardened/livecd-stage2-amd64-20151219//livecd': No such file or directory
cp: cannot create regular file '/home/release/buildroot/amd64-dev/builds/hardened/livecd-stage2-amd64-20151219/': Not a directory
tar: /home/release/buildroot/amd64-dev/builds/hardened/livecd-stage2-amd64-20151219: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Couldn't extract cdtar /usr/share/catalyst/livecd/cdtar/isolinux-elilo-memtest86+-cdtar.tar.bz2
21 Dec 2015 02:40:35 UTC: ERROR : CatalystError: cmd() NON-zero return value from: Bootloader script failed.
21 Dec 2015 02:40:36 UTC: ERROR : CatalystError: Script aborting due to error.
21 Dec 2015 02:40:36 UTC: ERROR : Exception running action sequence bootloader
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1399, in run
getattr(self, x)()
File "/usr/lib64/python2.7/site-packages/catalyst/base/stagebase.py", line 1639, in bootloader
raise CatalystError("Script aborting due to error.")
CatalystError
21 Dec 2015 02:40:36 UTC: NOTICE : Cleaning up... Running unbind()
Full build log at /home/release/tmp/run/catalyst-auto.5t9Z0X/log/hardened_admincd-stage2.log
next reply other threads:[~2015-12-21 2:40 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 2:40 catalyst [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-15 22:48 [gentoo-releng-autobuilds] [amd64-auto] Catalyst non-fatal build error - hardened/admincd-stage2.spec catalyst
2024-09-13 9:57 catalyst
2024-09-08 21:40 catalyst
2024-09-01 21:05 catalyst
2024-08-30 23:09 catalyst
2024-08-25 22:36 catalyst
2020-08-11 6:11 catalyst
2020-06-29 4:07 catalyst
2020-05-12 16:55 catalyst
2019-06-10 13:07 catalyst
2018-12-12 12:08 catalyst
2018-12-10 12:07 catalyst
2018-10-17 11:44 catalyst
2018-10-15 11:43 catalyst
2018-07-16 22:31 catalyst
2018-07-16 18:11 catalyst
2018-06-25 16:19 catalyst
2018-06-18 6:15 catalyst
2018-06-16 21:40 catalyst
2018-06-16 5:29 catalyst
2018-01-04 13:33 catalyst
2017-03-07 10:35 catalyst
2015-12-28 5:01 catalyst
2015-12-26 12:42 catalyst
2015-12-24 18:15 catalyst
2015-12-22 14:31 catalyst
2015-12-22 2:24 catalyst
2015-12-18 13:01 catalyst
2015-12-14 22:45 catalyst
2015-12-07 23:08 catalyst
2015-12-04 22:13 catalyst
2015-12-03 17:46 catalyst
2015-11-30 23:54 catalyst
2015-11-23 16:04 catalyst
2015-11-19 17:54 catalyst
2015-11-12 17:52 catalyst
2015-11-05 18:00 catalyst
2015-10-29 17:46 catalyst
2015-10-22 18:52 catalyst
2015-10-20 0:49 catalyst
2015-10-19 9:08 catalyst
2015-10-15 17:44 catalyst
2015-10-12 19:10 catalyst
2015-10-08 18:43 catalyst
2015-10-05 19:54 catalyst
2015-10-01 17:05 catalyst
2015-08-31 15:59 catalyst
2015-02-26 14:31 catalyst
2015-02-26 14:01 catalyst
2015-02-23 16:20 catalyst
2015-02-20 13:14 catalyst
2015-02-18 4:49 catalyst
2015-01-19 14:05 catalyst
2015-01-12 17:44 catalyst
2015-01-08 7:15 catalyst
2015-01-01 7:29 catalyst
2014-12-29 17:48 catalyst
2014-12-25 7:37 catalyst
2014-12-18 7:33 catalyst
2014-12-15 20:18 catalyst
2014-12-11 7:53 catalyst
2014-12-04 17:00 catalyst
2014-11-27 16:40 catalyst
2014-11-20 16:48 catalyst
2014-11-13 17:16 catalyst
2014-11-10 22:47 catalyst
2014-11-06 16:44 catalyst
2014-10-30 18:35 catalyst
2014-10-27 17:47 catalyst
2014-10-23 16:48 catalyst
2014-10-16 16:21 catalyst
2014-10-09 16:01 catalyst
2014-06-16 18:37 catalyst
2014-06-15 22:10 catalyst
2014-06-09 18:48 catalyst
2014-06-02 18:45 catalyst
2014-05-26 19:01 catalyst
2014-05-19 18:41 catalyst
2014-05-17 16:34 catalyst
2014-05-12 18:20 catalyst
2014-05-05 18:29 catalyst
2014-04-21 17:54 catalyst
2014-04-07 18:30 catalyst
2014-03-31 16:52 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=20151221024036.941B5E006E@lantean.jmbsvicetto.name \
--to=catalyst@lantean.jmbsvicetto.name \
--cc=gentoo-releng-autobuilds@lists.gentoo.org \
--cc=jmbsvicetto@gmail.com \
/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