On Mon, Apr 20, 2009 at 04:15:11PM +0100, Christian Kelly wrote:
> Andras Barna wrote:
>> no.
>> just tried
>>
>
> So, this is most likely as a result of the restart every 5mins. I'm
> working on this and will have a proper solution later in the week. For
> now, you could try setting PKG_CLIENT_TIMEOUT=600 or something even
> bigger. It may help, it may not.
That's not going to help at all. This error message is stating that the
downloaded file's content is corrupted.
1: Invalid content for action with path
usr/share/nexuiz/data/data20090403.3.pk3 chash failure: expected:
34f592b9fcf95cd86e7486004505b2d9aa56dae9 computed:
8b90cd9d0da57e7d07c6ccf774d367535b1c94ea.
2: Invalid content for action with path
usr/share/nexuiz/data/data20090403.3.pk3 chash failure: expected:
34f592b9fcf95cd86e7486004505b2d9aa56dae9 computed:
596c669fb92a0f6059d974dd7db7c61794aa29c0.
3: Invalid content for action with path
usr/share/nexuiz/data/data20090403.3.pk3 chash failure: expected:
34f592b9fcf95cd86e7486004505b2d9aa56dae9 computed:
512c2faadcd56731559e3618eec72ce11ac87fe3.
4: Invalid content for action with path
usr/share/nexuiz/data/data20090403.3.pk3 chash failure: expected:
34f592b9fcf95cd86e7486004505b2d9aa56dae9 computed:
f635036e2800f08385a8602ee68d30215dceefc7.
In each of these cases the client was trying to download content for the
file action usr/share/nexuiz/data/data20090403.3.pk3. That file is
supposed to hash to the SHA-1 value of
34f592b9fcf95cd86e7486004505b2d9aa56dae9, however each of these
transactions has returned a different incorrect value:
8b90cd9d0da57e7d07c6ccf774d367535b1c94ea
596c669fb92a0f6059d974dd7db7c61794aa29c0
512c2faadcd56731559e3618eec72ce11ac87fe3
f635036e2800f08385a8602ee68d30215dceefc7
You need to figure out why the file for this action isn't hashing
properly. This could be a bogus manifest, a corrupt file on your repo,
or some other problem that I've yet to imagine.
-j
