| 1 |
On Wednesday 04 February 2004 02:42 pm, Jason Rhinelander wrote: |
| 2 |
> 1. Is there a simple way to update these timestamps when I change the |
| 3 |
> portage tree? I mean other than edit the three files (yes, I am lazy). |
| 4 |
|
| 5 |
the timestamp files are created by scripts on the master rsync server ... |
| 6 |
they're not really utilized at this point in time so you dont have to worry |
| 7 |
about it |
| 8 |
|
| 9 |
> 2. Do I need to run `emerge regen` when I update the portage tree on the |
| 10 |
> rsync server? |
| 11 |
|
| 12 |
nope ... the metadata files only exist to make cache updates on the client |
| 13 |
side faster ... the update for the ebuilds you added will take a little bit |
| 14 |
longer on the clients side, but the difference is negligible |
| 15 |
|
| 16 |
> 3. I get an error the first time I emerge something and I think it may |
| 17 |
> have something to do with this cache. Here is the jist of the error: |
| 18 |
|
| 19 |
no, it's a portage bug, unrelated to the rsync tree ... ignore the autoclean |
| 20 |
error/warnings and just delete the incomplete stuff if those messages persist |
| 21 |
-mike |
Archives