1 |
On 4/10/06, Daevid Vincent <daevid@××××××.com> wrote: |
2 |
> Richard, once again I thank you for your knowledge. |
3 |
> |
4 |
> > Maybe a ~x86 system just isn't for you.... |
5 |
> |
6 |
> I didn't realize ~x86 was going to be such a headache. When I first |
7 |
> installed gentoo, I read a lot of debates on the list and most people said |
8 |
> that ~x86 was fairly "stable". Plus it seems there is such a LONG lag before |
9 |
> things are marked as stable. Plus for a while (again, this is going on two |
10 |
> years ago now I've had this notebook setup) many of the packages didn't have |
11 |
> "stable" ebuilds, or worse, they were marked stable, but a dependency |
12 |
> package was ~x86 so you had to edit package.keywords and add them... |
13 |
|
14 |
Well I think ~x86 is generally usable, but you do have to be a bit |
15 |
more cautious. For example, I don't mind --sync every day, but I tend |
16 |
to delay any updates that involve portage, baselayout, or other |
17 |
lowlevel system packages until Friday nights, after making a backup, |
18 |
so I have the whole weekend to pickup the pieces if something should |
19 |
break. |
20 |
|
21 |
And today I think if you encounter anything stable that depends on a |
22 |
~x86 package, it is a bug, and should be filed as such. |
23 |
|
24 |
> |
25 |
> My file is empty?! :( |
26 |
|
27 |
> |
28 |
> Is there a way to rebuild this file? |
29 |
|
30 |
The job of depscan.sh is to rebuild this file. But if the file exists |
31 |
and is newer than the configuration in /etc, it will not do anything, |
32 |
even it if deptree is empty. So delete deptree, and run depscan.sh |
33 |
again with the --debug option. You should see a bit more happen. |
34 |
|
35 |
> How did this happen? |
36 |
|
37 |
A badly timed Ctrl-alt-del or reboot could be the culprit. There is a |
38 |
window of opportunity while depscan is running that if it is aborted, |
39 |
will leave you with an empty file. |
40 |
|
41 |
-Richard |
42 |
|
43 |
-- |
44 |
gentoo-user@g.o mailing list |