1 |
On 07/30/2010 04:57 AM, Mark David Dumlao wrote: |
2 |
> diff between the eix --dump of my PC and the server |
3 |
> |
4 |
> === |
5 |
> madumlao@trixie ~ $ diff -Naur PC server |
6 |
> --- PC 2010-07-30 19:54:38.000000000 +0800 |
7 |
> +++ server 2010-07-30 19:55:05.000000000 +0800 |
8 |
> @@ -126,7 +126,7 @@ |
9 |
> |
10 |
> # STRING |
11 |
> # The path to the ebuild.sh executable. |
12 |
> -EXEC_EBUILD_SH="%{EPREFIX_PORTAGE_EXEC}/usr/lib64/portage/bin/ebuild.sh" |
13 |
> +EXEC_EBUILD_SH="%{EPREFIX_PORTAGE_EXEC}/usr/lib/portage/bin/ebuild.sh" |
14 |
> |
15 |
> # STRING |
16 |
> # The path to the tempfile generated by "ebuild depend". |
17 |
> @@ -177,7 +177,7 @@ |
18 |
> # STRING |
19 |
> # This variable is passed unchanged to ebuild.sh |
20 |
> # Usually ebuild.sh uses it to calculate the PATH. |
21 |
> -PORTAGE_ROOTPATH="/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4" |
22 |
> +PORTAGE_ROOTPATH="/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.3.4:/usr/i686-pc-linux-gnu/x86_64-pc-linux-gnu/gcc-bin/4.4.4" |
23 |
> |
24 |
> # STRING |
25 |
> # This variable is passed unchanged to ebuild.sh |
26 |
> === |
27 |
> |
28 |
> Seems to be just paths, don't see why that would cause a problem. |
29 |
> |
30 |
> Both machines are using portage 2.1.8.3 |
31 |
> |
32 |
> On Fri, Jul 30, 2010 at 7:46 PM, Mark David Dumlao <madumlao@×××××.com> wrote: |
33 |
>> Hi guys, |
34 |
>> Eix is one of those packages where you just set it and forget it, and |
35 |
>> apparently I've forgotten there was even anything to set. |
36 |
>> |
37 |
>> I have a home PC running gentoo. If I do eix foo, and foo happens to |
38 |
>> be keyworded unmasked in my package.keywords, I get for instance: |
39 |
>> [I] dev-python/snakeoil |
40 |
>> Available versions: <yellow>(~)0.3.6.4 (~)0.3.6.5 |
41 |
>> <block-yellow>(~)0.3.7</block-yellow></yellow> |
42 |
>> Installed versions: 0.3.7(07:34:54 PHT Saturday, 10 July, 2010) |
43 |
>> Homepage: http://www.pkgcore.org/ |
44 |
>> Description: Miscellaneous python utility code. |
45 |
>> |
46 |
>> I try the same on a relatively young gentoo server I'm managing and |
47 |
>> * dev-python/snakeoil |
48 |
>> Available versions: <yellow>~0.3.6.4 ~0.3.6.5 ~0.3.7</yellow> |
49 |
>> Homepage: http://www.pkgcore.org/ |
50 |
>> Description: Miscellaneous python utility code. |
51 |
>> |
52 |
>> It's unkeyworded, however, in my package.keywords in both machines: |
53 |
>> (home machine) |
54 |
>> madumlao@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/ |
55 |
>> /etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64 |
56 |
>> |
57 |
>> (server) |
58 |
>> master@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/ |
59 |
>> /etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86 |
60 |
>> |
61 |
>> Apparently I'm missing some environment variable, but I can't for the |
62 |
>> life of me imagine how I've set it. |
63 |
>> <home PC> |
64 |
>> madumlao@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc |
65 |
>> # /etc/eixrc |
66 |
>> # |
67 |
>> # In this file system-wide defaults for variables related to eix binaries |
68 |
>> # are stored, i.e. the variables set in this file override the built-in |
69 |
>> # defaults. Both can be overridden by ~/.eixrc and by environment variables. |
70 |
>> # |
71 |
>> # It is strongly recommended to set here only those variables which you |
72 |
>> # want to *differ* from the built-in defaults (or for which you have a |
73 |
>> # particular reason why the default should never change with an eix update). |
74 |
>> # |
75 |
>> # *Otherwise you might miss changes in the defaults in newer eix versions* |
76 |
>> # which may result in confusing behavior of the eix binaries. |
77 |
>> # |
78 |
>> # ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in |
79 |
>> # /etc/eixrc which is not recommended anymore. If you want to get such a file |
80 |
>> # (i.e. a file where all variables are described and set to the current |
81 |
>> # values resp. to the built-in default values) you can redirect the output |
82 |
>> # of the options --dump or --dump-defaults, respectively. |
83 |
>> # |
84 |
>> # However once more: To avoid unexpected problems |
85 |
>> # |
86 |
>> # *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc |
87 |
>> # |
88 |
>> # Only set those for which you have a reason to do so! |
89 |
>> # |
90 |
>> # For the available variables and their defaults, see the output of the |
91 |
>> # options --dump or --dump-defaults. |
92 |
>> # For more detailed explanations see the manpage of eix. |
93 |
>> |
94 |
>> madumlao@trixie ~/store/HeCares/Photo upload functionality $ cat |
95 |
>> /etc/eix-sync.conf |
96 |
>> # eix-sync.conf |
97 |
>> ## defines options to eix-sync, caching system for portage |
98 |
>> |
99 |
>> |
100 |
>> #layman overlays to be synced (* means all) |
101 |
>> * |
102 |
>> </home PC> |
103 |
>> |
104 |
>> <server> |
105 |
>> master@zen ~ $ cat /etc/eixrc |
106 |
>> # /etc/eixrc |
107 |
>> # |
108 |
>> # In this file system-wide defaults for variables related to eix binaries |
109 |
>> # are stored, i.e. the variables set in this file override the built-in |
110 |
>> # defaults. Both can be overridden by ~/.eixrc and by environment variables. |
111 |
>> # |
112 |
>> # It is strongly recommended to set here only those variables which you |
113 |
>> # want to *differ* from the built-in defaults (or for which you have a |
114 |
>> # particular reason why the default should never change with an eix update). |
115 |
>> # |
116 |
>> # *Otherwise you might miss changes in the defaults in newer eix versions* |
117 |
>> # which may result in confusing behavior of the eix binaries. |
118 |
>> # |
119 |
>> # ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in |
120 |
>> # /etc/eixrc which is not recommended anymore. If you want to get such a file |
121 |
>> # (i.e. a file where all variables are described and set to the current |
122 |
>> # values resp. to the built-in default values) you can redirect the output |
123 |
>> # of the options --dump or --dump-defaults, respectively. |
124 |
>> # |
125 |
>> # However once more: To avoid unexpected problems |
126 |
>> # |
127 |
>> # *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc |
128 |
>> # |
129 |
>> # Only set those for which you have a reason to do so! |
130 |
>> # |
131 |
>> # For the available variables and their defaults, see the output of the |
132 |
>> # options --dump or --dump-defaults. |
133 |
>> # For more detailed explanations see the manpage of eix. |
134 |
>> |
135 |
>> master@zen ~ $ cat /etc/eix-sync.conf |
136 |
>> cat: /etc/eix-sync.conf: No such file or directory |
137 |
>> </server> |
138 |
>> |
139 |
>> All comments for the both of them, so it must be a default I'm missing |
140 |
>> that's different for the 2 machines. Any ideas? |
141 |
>> -- |
142 |
>> This email is: [ ] actionable [ ] fyi [x] social |
143 |
>> Response needed: [ ] yes [x] up to you [ ] no |
144 |
>> Time-sensitive: [ ] immediate [ ] soon [ ] none |
145 |
>> |
146 |
|
147 |
What does "eselect profile list" show you on both hosts? |