1 |
On Tue, Oct 21, 2008 at 12:21 AM, Justin <justin@×××××××××.net> wrote: |
2 |
> Mark Knecht schrieb: |
3 |
>> Anything I should try to do about this? |
4 |
>> |
5 |
>> Thanks, |
6 |
>> Mark |
7 |
>> |
8 |
>> Saving to: `/usr/portage/distfiles/scons-1.0.0.tar.gz' |
9 |
>> |
10 |
>> 100%[======================================>] 541,330 682K/s in 0.8s |
11 |
>> |
12 |
>> 2008-10-20 18:18:02 (682 KB/s) - |
13 |
>> `/usr/portage/distfiles/scons-1.0.0.tar.gz' saved [541330/541330] |
14 |
>> |
15 |
>> * checking ebuild checksums ;-) ... [ ok ] |
16 |
>> * checking auxfile checksums ;-) ... [ ok ] |
17 |
>> * checking miscfile checksums ;-) ... [ ok ] |
18 |
>> * checking scons-1.0.0.tar.gz ;-) ... [ ok ] |
19 |
>> |
20 |
>>>>> Unpacking source... |
21 |
>>>>> Unpacking scons-1.0.0.tar.gz to /var/tmp/portage/dev-util/scons-1.0.0/work |
22 |
>>>>> Source unpacked. |
23 |
>>>>> |
24 |
>> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
25 |
>> * is known to be triggered by things such as failed variable assignments |
26 |
>> * (bug #190128) or bad substitution errors (bug #200313). |
27 |
>> |
28 |
>> * Messages for package dev-util/scons-1.0.0: |
29 |
>> |
30 |
>> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
31 |
>> * is known to be triggered by things such as failed variable assignments |
32 |
>> * (bug #190128) or bad substitution errors (bug #200313). |
33 |
>> lightning ~ # |
34 |
>> |
35 |
>> |
36 |
> On my system it works. Do you have enough space in /var/tmp/portage? |
37 |
> |
38 |
> |
39 |
I think so. Seems to be about 2GB. |
40 |
|
41 |
lightning ~ # df |
42 |
Filesystem 1K-blocks Used Available Use% Mounted on |
43 |
/dev/sda2 9614148 6742592 2383180 74% / |
44 |
udev 10240 184 10056 2% /dev |
45 |
/dev/sda6 3850292 777652 2877052 22% /usr/src |
46 |
/dev/sda8 14428928 11630740 2065224 85% /home |
47 |
/dev/sda13 48070472 33619600 12008996 74% /mnt/NewMusic |
48 |
shm 508016 0 508016 0% /dev/shm |
49 |
/dev/sda5 38456308 22950852 13551956 63% /home/mark/backups |
50 |
lightning ~ # |
51 |
|
52 |
Answering Duncan's question about portage versions I'm a bit behind: |
53 |
|
54 |
lightning ~ # eix -Ic portage |
55 |
[I] app-portage/portage-utils (0.1.29@06/28/08): small and fast |
56 |
portage helper tools written in C |
57 |
[I] sys-apps/portage (2.1.4.5@10/14/08): Portage is the package |
58 |
management and distribution system for Gentoo |
59 |
Found 2 matches. |
60 |
lightning ~ # |
61 |
|
62 |
How would I put in the debug echos? I know nothing of this stuff. |
63 |
|
64 |
Probably before I do that I should at least update portage. |
65 |
|
66 |
Note also, in case it's important, that I'm somewhat concerned about |
67 |
python on this machine. I've been getting some strange messages about |
68 |
locales that I don't understand. Probably they are unrelated to this |
69 |
problem but better to disclose it now as they are the only ongoing |
70 |
problem I've got that I've not found a solution for. They show up when |
71 |
running something like layman to do an overlay update: |
72 |
|
73 |
lightning ~ # layman -s pro-audio |
74 |
* Overlay "rostov" is missing a "description" entry! |
75 |
* Overlay "rostov" is missing a "description" entry! |
76 |
* Overlay "rostov" is missing a "description" entry! |
77 |
* Overlay "rostov" is missing a "description" entry! |
78 |
* Running command "/usr/bin/svn update "/usr/portage/local/layman/pro-audio""... |
79 |
svn: warning: cannot set LC_CTYPE locale |
80 |
svn: warning: environment variable LANG is en_US |
81 |
svn: warning: please check that your locale name is correct |
82 |
At revision 1344. |
83 |
* |
84 |
* Success: |
85 |
* ------ |
86 |
* |
87 |
* Successfully synchronized overlay "pro-audio". |
88 |
lightning ~ # |
89 |
|
90 |
Here's my /etc/locale.gen file |
91 |
|
92 |
lightning ~ # cat /etc/locale.gen |
93 |
#en_US ISO-8859-1 |
94 |
en_US.UTF-8 UTF-8 |
95 |
lightning ~ # |
96 |
|
97 |
Note that I used to have the ISO-8859 included but after recent |
98 |
updates CUPS stopped printing from computers across the network. I had |
99 |
to remove it to allow my family to print. |
100 |
|
101 |
Again, probably not related but better to get this out there so we can |
102 |
disregard it. |
103 |
|
104 |
Thanks all, |
105 |
Mark |