1 |
* This may however number your devices in a different way than they are now. |
2 |
* |
3 |
* If you build an initramfs including udev, then please |
4 |
* make sure that the /sbin/udevadm binary gets included, |
5 |
* and your scripts changed to use it,as it replaces the |
6 |
* old helper apps udevinfo, udevtrigger, ... |
7 |
* |
8 |
* mount options for directory /dev are no longer |
9 |
* set in /etc/udev/udev.conf, but in /etc/fstab |
10 |
* as for other directories. |
11 |
* |
12 |
* If you use /dev/md/*, /dev/loop/* or /dev/rd/*, |
13 |
* then please migrate over to using the device names |
14 |
* /dev/md*, /dev/loop* and /dev/ram*. |
15 |
* The devfs-compat rules have been removed. |
16 |
* For reference see Bug #269359. |
17 |
* |
18 |
* Rules for /dev/hd* devices have been removed |
19 |
* Please migrate to libata. |
20 |
* |
21 |
* For more information on udev on Gentoo, writing udev rules, and |
22 |
* fixing known issues visit: |
23 |
* http://www.gentoo.org/doc/en/udev-guide.xml |
24 |
* Messages for package sys-apps/man-pages-3.40: |
25 |
* If you don't have a makewhatis cronjob, then you |
26 |
* should update the whatis database yourself: |
27 |
* # makewhatis -u |
28 |
* Messages for package sys-fs/e2fsprogs-1.42: |
29 |
* No /etc/mtab file, creating one temporarily |
30 |
* Messages for package sys-libs/pam-1.1.5: |
31 |
* Some software with pre-loaded PAM libraries might experience |
32 |
* warnings or failures related to missing symbols and/or versions |
33 |
* after any update. While unfortunate this is a limit of the |
34 |
* implementation of PAM and the software, and it requires you to |
35 |
* restart the software manually after the update. |
36 |
* |
37 |
* You can get a list of such software running a command like |
38 |
* lsof / | egrep -i 'del.*libpam\.so' |
39 |
* |
40 |
* Alternatively, simply reboot your system. |
41 |
* Messages for package sys-auth/pambase-20101024-r2: |
42 |
* Starting from version 20080801, pambase optionally enables |
43 |
* SHA512-hashed passwords. For this to work, you need sys-libs/pam-1.0.1 |
44 |
* built against sys-libs/glibc-2.7 or later. |
45 |
* If you don't have support for this, it will automatically fallback |
46 |
* to MD5-hashed passwords, just like before. |
47 |
* |
48 |
* Please note that the change only affects the newly-changed passwords |
49 |
* and that SHA512-hashed passwords will not work on earlier versions |
50 |
* of glibc or Linux-PAM. |
51 |
* Messages for package sys-apps/openrc-0.9.8.4: |
52 |
* You should now update all files in /etc, using etc-update |
53 |
* or equivalent before restarting any services or this host. |
54 |
* |
55 |
* Please read the migration guide available at: |
56 |
* http://www.gentoo.org/doc/en/openrc-migration.xml |
57 |
* Messages for package sys-apps/busybox-1.20.1: |
58 |
* Could not locate user configfile, so we will save a default one |
59 |
* Your configuration for sys-apps/busybox-1.20.1 has been saved in |
60 |
* /etc/portage/savedconfig/sys-apps/busybox-1.20.1 for your editing pleasure. |
61 |
* You can edit these files by hand and remerge this package with |
62 |
* USE=savedconfig to customise the configuration. |
63 |
* You can rename this file/directory to one of the following for |
64 |
* its configuration to apply to multiple versions: |
65 |
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/ |
66 |
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}] |
67 |
* Messages for package net-misc/openssh-5.9_p1-r4: |
68 |
* Starting with openssh-5.8p1, the server will default to a newer key |
69 |
* algorithm (ECDSA). You are encouraged to manually update your stored |
70 |
* keys list as servers update theirs. See ssh-keyscan(1) for more info. |
71 |
* Remember to merge your config files in /etc/ssh/ and then |
72 |
* reload sshd: '/etc/init.d/sshd reload'. |
73 |
* Please be aware users need a valid shell in /etc/passwd |
74 |
* in order to be allowed to login. |
75 |
|
76 |
|
77 |
|
78 |
|
79 |
|
80 |
|
81 |
|
82 |
|
83 |
|
84 |
|
85 |
|
86 |
|
87 |
|
88 |
|
89 |
|
90 |
|
91 |
|
92 |
|
93 |
|
94 |
|
95 |
|
96 |
|
97 |
|
98 |
|
99 |
|
100 |
|
101 |
|
102 |
|
103 |
|
104 |
|
105 |
|
106 |
|
107 |
|
108 |
|
109 |
removing /release/buildroot/amd64-dev/tmp/default/stage3-amd64-20120719/tmp/chroot-functions.sh from the chroot |
110 |
--- Running action sequence: preclean |
111 |
copying stage3-preclean-chroot.sh to /release/buildroot/amd64-dev/tmp/default/stage3-amd64-20120719/tmp/ |
112 |
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage3-amd64-20120719/tmp/ |
113 |
Running stage3-preclean-chroot.sh in chroot /release/buildroot/amd64-dev/tmp/default/stage3-amd64-20120719/ |
114 |
>>> Regenerating /etc/ld.so.cache... |
115 |
emerge --depclean --with-bdeps=y |
116 |
!!! CONFIG_PROTECT is empty |
117 |
|
118 |
* Depclean may break link level dependencies. Thus, it is |
119 |
* recommended to use a tool such as `revdep-rebuild` (from |
120 |
* app-portage/gentoolkit) in order to detect such breakage. |
121 |
* |
122 |
* Always study the list of packages to be cleaned for any obvious |
123 |
* mistakes. Packages that are part of the world set will always |
124 |
* be kept. They can be manually added to this set with |
125 |
* `emerge --noreplace <atom>`. Packages that are listed in |
126 |
* package.provided (see portage(5)) will be removed by |
127 |
* depclean, even if they are part of the world set. |
128 |
* |
129 |
* As a safety measure, depclean will not remove any packages |
130 |
* unless *all* required dependencies have been resolved. As a |
131 |
* consequence, it is often necessary to run `emerge --update |
132 |
* --newuse --deep @world` prior to depclean. |
133 |
!!! You have no world file. |
134 |
!!! Proceeding is likely to break your installation. |
135 |
|
136 |
Calculating dependencies ... done! |
137 |
>>> Calculating removal order... |
138 |
|
139 |
dev-util/ccache |
140 |
selected: 3.1.7 |
141 |
protected: none |
142 |
omitted: none |
143 |
|
144 |
sys-apps/makedev |
145 |
selected: 3.23.1 |
146 |
protected: none |
147 |
omitted: none |
148 |
|
149 |
All selected packages: sys-apps/makedev-3.23.1 dev-util/ccache-3.1.7 |
150 |
|
151 |
>>> 'Selected' packages are slated for removal. |
152 |
>>> 'Protected' and 'omitted' packages will not be removed. |
153 |
|
154 |
>>> Unmerging (1 of 2) dev-util/ccache-3.1.7... |
155 |
>>> Unmerging (2 of 2) sys-apps/makedev-3.23.1... |
156 |
Packages installed: 118 |
157 |
Packages in world: 0 |
158 |
Packages in system: 42 |
159 |
Required packages: 118 |
160 |
Number removed: 2 |
161 |
|
162 |
* GNU info directory index is up-to-date. |
163 |
|
164 |
* IMPORTANT: 3 news items need reading for repository 'gentoo'. |
165 |
* Use eselect news to read news items. |
166 |
|
167 |
emerge -C dev-util/ccache |
168 |
!!! CONFIG_PROTECT is empty |
169 |
* This action can remove important packages! In order to be safer, use |
170 |
* `emerge -pv --depclean <atom>` to check for reverse dependencies before |
171 |
* removing packages. |
172 |
|
173 |
--- Couldn't find 'dev-util/ccache' to unmerge. |
174 |
|
175 |
>>> No packages selected for removal by unmerge |
176 |
|
177 |
!!! catalyst: preclean script failed. |
178 |
|
179 |
|
180 |
Traceback (most recent call last): |
181 |
File "modules/generic_stage_target.py", line 1154, in preclean |
182 |
" preclean","preclean script failed.",env=self.env) |
183 |
File "/usr/lib64/catalyst/modules/catalyst_support.py", line 542, in cmd |
184 |
raise CatalystError,myexc |
185 |
CatalystError |
186 |
None |
187 |
|
188 |
!!! catalyst: Build failed, could not execute preclean |
189 |
|
190 |
Traceback (most recent call last): |
191 |
File "/usr/lib64/catalyst/catalyst", line 206, in build_target |
192 |
mytarget.run() |
193 |
File "modules/generic_stage_target.py", line 1254, in run |
194 |
apply(getattr(self,x)) |
195 |
File "modules/generic_stage_target.py", line 1159, in preclean |
196 |
raise CatalystError, "Build failed, could not execute preclean" |
197 |
CatalystError |
198 |
!!! catalyst: Error encountered during run of target stage3 |
199 |
Catalyst aborting.... |
200 |
lockfile does not exist '/release/buildroot/amd64-dev/tmp/default/stage3-amd64-20120719/.catalyst_lock' |
201 |
|
202 |
|
203 |
|
204 |
Full build log at /tmp/catalyst-auto.26456/log/stage3.log |