| 1 |
On Mon, 2 Jan 2006 10:57:00 +1000, Alan E. Davis wrote: |
| 2 |
|
| 3 |
> Over a period of a week or so, while I was celebrating the holidays, |
| 4 |
> my system experienced a hardware hiccough, causing system |
| 5 |
> clock/hardware clock time to change to 2020. The upshot is that a |
| 6 |
> bunch of merges, a kernel compile, and various other system components |
| 7 |
> have files that are way out of date. |
| 8 |
> |
| 9 |
> I have experimentally touched some files with the current date and |
| 10 |
> time. |
| 11 |
|
| 12 |
Changing dates manually will confuse portage, which keeps track of the |
| 13 |
datestamps of all files it installs. The upshot is that it will no |
| 14 |
remove files where the dates have changed. The safest method of correcting |
| 15 |
the dates would be to re-emerge the affected packages. Use genlop --list |
| 16 |
--date XXX to see which you installed during the problem period, then |
| 17 |
emerge them all with the --oneshot option. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
If at first you don't succeed, call it Windows NT. |
Archives