Gentoo Archives: gentoo-releng-autobuilds

From: catalyst@×××××××××××××××××××××××.org
To: releng@g.o, gentoo-releng-autobuilds@l.g.o
Subject: [gentoo-releng-autobuilds] [ia64-auto] Catalyst non-fatal build error - installcd-stage1.spec
Date: Wed, 27 Apr 2011 01:27:37
Message-Id: 20110427012736.11CC61C002@pigeon.gentoo.org
1 * Messages for package sys-apps/pciutils-3.1.7:
2
3 * The 'pcimodules' program has been replaced by 'lspci -k'
4
5 * Messages for package app-crypt/pinentry-0.8.0:
6
7 * We no longer install pinentry-curses and pinentry-qt SUID root by default.
8 * Linux kernels >=2.6.9 support memory locking for unprivileged processes.
9 * The soft resource limit for memory locking specifies the limit an
10 * unprivileged process may lock into memory. You can also use POSIX
11 * capabilities to allow pinentry to lock memory. To do so activate the caps
12 * USE flag and add the CAP_IPC_LOCK capability to the permitted set of
13 * your users.
14
15 * Messages for package net-misc/dhcpcd-5.2.12:
16
17 * Disabling zeroconf support
18 *
19 * Users upgrading from 4.0 series should pay attention to removal
20 * of compat useflag. This changes behavior of dhcp in wide manner:
21 * dhcpcd no longer sends a default ClientID for ethernet interfaces.
22 * This is so we can re-use the address the kernel DHCP client found.
23 * To retain the old behaviour of sending a default ClientID based on the
24 * hardware address for interface, simply add the keyword clientid
25 * to dhcpcd.conf or use commandline parameter -I ''
26 *
27 * Also, users upgrading from 4.0 series should be aware that
28 * the -N, -R and -Y command line options no longer exist.
29 * These are controled now by nohook options in dhcpcd.conf.
30
31 * Messages for package sys-fs/mdadm-3.1.4:
32
33 * If using baselayout-2 and not relying on kernel auto-detect
34 * of your RAID devices, you need to add 'mdraid' to your 'boot'
35 * runlevel. Run the following command:
36 * rc-update add mdraid boot
37
38 * Messages for package sys-power/acpid-2.0.6:
39
40 *
41 * You may wish to read the Gentoo Linux Power Management Guide,
42 * which can be found online at:
43 * http://www.gentoo.org/doc/en/power-management-guide.xml
44 *
45
46 * Messages for package sys-fs/e2fsprogs-1.41.12:
47 * No /etc/mtab file, creating one temporarily
48
49
50 * Messages for package sys-fs/lvm2-2.02.73-r1:
51 * Unable to find kernel sources at /usr/src/linux
52 * Unable to calculate Linux Kernel version for build, attempting to use running version
53 * Building shared LVM, it will not work inside genkernel!
54
55 * USE flag nocman is deprecated and replaced
56 * with the cman USE flag.
57 *
58 * USE flags clvm and cman are masked
59 * by default and need to be unmasked to use them
60 *
61 * If you are using genkernel and root-on-LVM, rebuild the initramfs.
62 * lvm volumes are no longer automatically created for
63 * baselayout-2 users. If you are using baselayout-2, be sure to
64 * run: # rc-update add lvm boot
65 * Do NOT add it if you are using baselayout-1 still.
66
67 * Messages for package app-accessibility/brltty-4.2:
68
69 *
70 * please be sure /etc/brltty.conf is correct for your system.
71 *
72 * To make brltty start on boot, type this command as root:
73 *
74 * rc-update add brltty boot
75
76 * Messages for package app-misc/screen-4.0.3-r4:
77
78 * Some dangerous key bindings have been removed or changed to more safe values.
79 * We enable some xterm hacks in our default screenrc, which might break some
80 * applications. Please check /etc/screenrc for information on these changes.
81
82 * Messages for package net-misc/ntp-4.2.4_p7-r1:
83 * You can find an example /etc/ntp.conf in /usr/share/ntp/
84 * Review /etc/ntp.conf to setup server info.
85 * Review /etc/conf.d/ntpd to setup init.d info.
86
87 * The way ntp sets and maintains your system time has changed.
88 * Now you can use /etc/init.d/ntp-client to set your time at
89 * boot while you can use /etc/init.d/ntpd to maintain your time
90 * while your machine runs
91
92 * Messages for package app-misc/livecd-tools-1.0.42:
93 * This package is designed for use on the LiveCD only and will do
94 * unspeakably horrible and unexpected things on a normal system.
95 * YOU HAVE BEEN WARNED!!!
96
97
98 * Messages for package sys-apps/hwsetup-1.2-r1:
99 * This package is designed for use on the LiveCD only and will do
100 * unspeakably horrible and unexpected things on a normal system.
101 * YOU HAVE BEEN WARNED!!!
102 * This package is intended for usage on the Gentoo release media. If
103 * you are not building a CD, remove this package. It will not work
104 * properly on a running system, as Gentoo does not use any of the
105 * Knoppix-style detection except for CD builds.
106
107
108 * Messages for package sys-fs/cryptsetup-1.1.3-r3:
109 * Unable to find kernel sources at /usr/src/linux
110 * Unable to calculate Linux Kernel version for build, attempting to use running version
111 * CONFIG_DM_CRYPT: is not set (required for cryptsetup)
112 *
113 * Please check to make sure these options are set correctly.
114 * Failure to do so may cause unexpected problems.
115 * This ebuild introduces a new set of scripts and configuration
116 * than the last version. If you are currently using /etc/conf.d/cryptfs
117 * then you *MUST* copy your old file to:
118 * /etc/conf.d/dmcrypt
119 * Or your encrypted partitions will *NOT* work.
120
121 * Please see the example for configuring a LUKS mountpoint
122 * in /etc/conf.d/dmcrypt
123 *
124 * If you are using baselayout-2 then please do:
125 * rc-update add dmcrypt boot
126 * This version introduces a command line arguement 'key_timeout'.
127 * If you want the search for the removable key device to timeout
128 * after 10 seconds add the following to your bootloader config:
129 * key_timeout=10
130 * A timeout of 0 will mean it will wait indefinitely.
131 *
132 * Users using cryptsetup-1.0.x (dm-crypt plain) volumes must use
133 * a compatibility mode when using cryptsetup-1.1.x. This can be
134 * done by specifying the cipher (-c), key size (-s) and hash (-h).
135 * For more info, see http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Issues_with_Specific_Versions_of_cryptsetup
136
137 * Messages for package app-crypt/gnupg-2.0.16-r1:
138
139 * If you wish to view images emerge:
140 * media-gfx/xloadimage, media-gfx/xli or any other viewer
141 * Remember to use photo-viewer option in configuration file to activate
142 * the right viewer.
143 * Please remember to restart gpg-agent if a different version
144 * of the agent is currently used. If you are unsure of the gpg
145 * agent you are using please run 'killall gpg-agent',
146 * and to start a fresh daemon just run 'gpg-agent --daemon'.
147
148 * Messages for package app-admin/syslog-ng-3.1.4:
149
150 * It is highly recommended that app-admin/logrotate be emerged to
151 * manage the log files. syslog-ng installs a file in /etc/logrotate.d
152 * for logrotate to use.
153
154 * Messages for package sys-fs/evms-2.5.5-r11:
155 * ERROR: sys-fs/evms-2.5.5-r11 failed (compile phase):
156 * Failed emake
157 *
158 * Call stack:
159 * ebuild.sh, line 56: Called src_compile
160 * environment, line 3911: Called die
161 * The specific snippet of code:
162 * emake || die "Failed emake"
163 *
164 * If you need support, post the output of 'emerge --info =sys-fs/evms-2.5.5-r11',
165 * the complete build log and the output of 'emerge -pqv =sys-fs/evms-2.5.5-r11'.
166 * The complete build log is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/build.log'.
167 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/evms-2.5.5-r11/temp/environment'.
168 * S: '/var/tmp/portage/sys-fs/evms-2.5.5-r11/work/evms-2.5.5'
169
170 * Regenerating GNU info directory index...
171 * Processed 85 info files.
172
173 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
174 * Use eselect news to read news items.
175
176
177 !!! catalyst: Error in attempt to build packages
178
179
180 Traceback (most recent call last):
181 File "modules/generic_stage_target.py", line 1362, in build_packages
182 "Error in attempt to build packages",env=self.env)
183 File "/usr/lib/catalyst/modules/catalyst_support.py", line 542, in cmd
184 raise CatalystError,myexc
185 CatalystError
186 None
187
188 !!! catalyst: livecdbuild aborting due to error.
189
190 Traceback (most recent call last):
191 File "/usr/lib/catalyst/catalyst", line 209, in build_target
192 mytarget.run()
193 File "modules/generic_stage_target.py", line 1263, in run
194 apply(getattr(self,x))
195 File "modules/generic_stage_target.py", line 1367, in build_packages
196 "build aborting due to error."
197 CatalystError
198 !!! catalyst: Error encountered during run of target livecd-stage1
199 Catalyst aborting....
200 lockfile does not exist '/var/tmp/catalyst/tmp/default/livecd-stage1-ia64-20110426/.catalyst_lock'
201
202
203
204 Full build log at /tmp/catalyst-auto.7448/log/installcd-stage1.log