1 |
Hey yall, |
2 |
|
3 |
I have been using Catalyst sucessfully for the past 3+ years managing a |
4 |
Gentoo cluster (about 40 servers). What I do is to build stage1, stage2, |
5 |
stage3 and stage4 based on the same snapshot and them I would create |
6 |
stage4-n as a stage4 based on the prior stage4 generated, but using a newer |
7 |
stage4 this time. My last stage was based on snapshot 20101019 and now I'm |
8 |
upgrading to 20110522. But when doing the system upgrade the catalyst fails |
9 |
with the following message: |
10 |
|
11 |
Bringing system up to date using profile specific use flags |
12 |
emerge --quiet --usepkg --buildpkg --newuse -u system |
13 |
|
14 |
(...) |
15 |
|
16 |
[ebuild N ] sys-apps/openrc-0.8.2-r1 |
17 |
[ebuild U ] sys-apps/util-linux-2.19.1 [2.17.2] |
18 |
[ebuild U ] net-misc/iputils-20100418-r1 [20100418] |
19 |
[blocks B ] >=sys-kernel/linux-headers-2.6.33 |
20 |
(">=sys-kernel/linux-headers-2.6.33" is blocking |
21 |
net-firewall/iptables-1.4.6) |
22 |
|
23 |
* Error: The above package list contains packages which cannot be |
24 |
* installed at the same time on the same system. |
25 |
|
26 |
('installed', '/', 'net-firewall/iptables-1.4.6', 'nomerge') pulled in by |
27 |
net-firewall/iptables required by world |
28 |
|
29 |
('ebuild', '/', 'sys-kernel/linux-headers-2.6.36.1', 'merge') pulled in by |
30 |
sys-kernel/linux-headers:0 required by ('ebuild', '/', |
31 |
'virtual/os-headers-0', 'merge') |
32 |
|
33 |
I tried putting net-firewall/iptables as ~x86 on a package.keywords file |
34 |
referenced by the portage_confdir config but it didn't considered it. The |
35 |
right package.keyword is right that at |
36 |
/var/tmp/catalyst/tmp/supra10.10/stage4-core2-10.10-02/etc/portage/package.keywords. |
37 |
In a real world system this led to another blocking, so the solution to the |
38 |
blocking problem for catalyst upgrades in general would be better. |
39 |
|
40 |
Does anyone have any idea to help? |
41 |
|
42 |
Best, |
43 |
Daniel |