| 1 |
this problem has not been completed, is there a reason why? |
| 2 |
|
| 3 |
Chris |
| 4 |
|
| 5 |
On Sun, 2004-07-25 at 16:20, Scott Kveton wrote: |
| 6 |
> > >I believe these are errors due to the directory juggling that is going |
| 7 |
> > >on before the next release. I believe (and somebody correct me if I'm |
| 8 |
> > >wrong here) has to do with /releases/historical to save on bandwidth |
| 9 |
> > >before the release. |
| 10 |
> > |
| 11 |
> > Would this: |
| 12 |
> > |
| 13 |
> > rsync error: some files could not be transferred (code 23) at main.c(1048) |
| 14 |
> > |
| 15 |
> > Run along the same lines? I've been getting it the past 4 syncs of |
| 16 |
> > distfiles. |
| 17 |
> |
| 18 |
> Yes. This is caused because the 'historical/' directory is not readable |
| 19 |
> at this time. We didn't want to push out old data so close to a |
| 20 |
> release. This should be fixed sometime next week after the release |
| 21 |
> tempest has calmed a bit. |
| 22 |
> |
| 23 |
> Scott :-) |
| 24 |
> |
| 25 |
> -- |
| 26 |
> gentoo-mirrors@g.o mailing list |
| 27 |
---- BOFH Excuse #230: Lusers learning curve appears to be fractal |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-mirrors@g.o mailing list |
Archives