On Tue, Jun 25, 2013 at 10:39 AM, toby wrote:
>> This happens from time-to-time with Snapshots. It usually does not mean
>> there is a problem, but that a partial snap went out. Wait a while for
>> the mirrors to catch up.
>
> Oh ok, but how come all the time stamps say that all the files in the
> This happens from time-to-time with Snapshots. It usually does not mean
> there is a problem, but that a partial snap went out. Wait a while for
> the mirrors to catch up.
Oh ok, but how come all the time stamps say that all the files in the
directory were last modified on the 24th (both the
On 2013 Jun 25 (Tue) at 17:44:11 +0200 (+0200), Charles RAPENNE wrote:
:On 06/25/13 16:25, toby wrote:
:>Hi there,
:>
:>I just wondered if anyone else had found that the shasums on the latest
:>(24/06/13) snapshots are wrong. I've just tried upgrading from all the
:>different mirrors here in the UK
On 06/25/13 16:25, toby wrote:
Hi there,
I just wondered if anyone else had found that the shasums on the latest
(24/06/13) snapshots are wrong. I've just tried upgrading from all the
different mirrors here in the UK & got shasum errors for all the non X
parts from the Oxford mirror, the Bytemar
On Tue, Jun 25, 2013 at 7:25 AM, toby wrote:
> Hi there,
>
> I just wondered if anyone else had found that the shasums on the latest
> (24/06/13) snapshots are wrong.
yes.
(SHA256) INSTALL.amd64: OK
(SHA256) base53.tgz: FAILED
(SHA256) bsd: FAILED
(SHA256) bsd.mp: FAILED
(SHA256) bsd.rd: OK
cksu
Hi there,
I just wondered if anyone else had found that the shasums on the latest
(24/06/13) snapshots are wrong. I've just tried upgrading from all the
different mirrors here in the UK & got shasum errors for all the non X
parts from the Oxford mirror, the Bytemark mirror and the mirrorservice
on
6 matches
Mail list logo
