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