Re: Snapshot shasum mismatch
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 > directory were last modified on the 24th (both the correctly summed files > and the the incorrect ones)? I thought that meant that all the files in > that directory had been updated on the same day. Or do you mean something > else by partial update? In this case, a close examination would show that the base sets were updated in the minute before the X sets were updated. It's likely that what occurred was the updates to the SHA256 file overlapped, resulting in the checksums for the new base sets were overwritten with the checksums for the previous base sets. > Also, I wondered if there was a way to have the installer/upgrader ask you > whether or not you want to continue if it encounters an incorrect shasum? > By default it just carries on regardless. That would involve downloading all the sets before installing any of them, as you don't want to mix sets. Where do you put them before then? It's probably doable, but working out the details would be a chunk of work for someone. Worth it? Not to me... Philip Guenther
Re: Snapshot shasum mismatch
> 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 correctly summed files and the the incorrect ones)? I thought that meant that all the files in that directory had been updated on the same day. Or do you mean something else by partial update? Also, I wondered if there was a way to have the installer/upgrader ask you whether or not you want to continue if it encounters an incorrect shasum? By default it just carries on regardless. Unfortunately I was too impatient and lazy to check beforehand this time... not a mistake I'm likely to make again anytime soon! But still, it's always nice when a piece of software picks up the slack of my many character defects, so I thought I'd ask!
Re: Snapshot shasum mismatch
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 & got shasum errors for all the non X :>parts from the Oxford mirror, the Bytemark mirror and the mirrorservice :>one... :> 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. -- I don't know anything about music. In my line you don't have to. -- Elvis Presley
Re: Snapshot shasum mismatch
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 Bytemark mirror and the mirrorservice one... Here are some examples: SHA256 (base53.tgz) = b46c621ae4be7183ab90279d887748d69b4822a309ede81067abbe7adf0b7c5c fd29dadcf424335e8614745e5dd6a9a88ad8b893decc4b5b4c0ffed26dda891c base53.tgz SHA256 (bsd) = 630e5b962a035abe5f25161895bd375979d6907b438d439ccb8e43a7d80f89e0 2de329fc109816fd8a810b0d6a411bad3710f8bb476f213ffc9e3d5d20ac2db2 bsd SHA256 (bsd.mp) = fbca7ad263c42a0265ddce05b030a9168e3d74bbac0fd3195acc75ec301e5040 af34f3faeeb26d8d7f22ed44edeb90fd17980c64d3148c44b4ec6ebcb416341a bsd.mp SHA256 (comp53.tgz) = 6229bbb09a5c1a4d5d761b86c133c15e688abc85c3e6adc6421aa46c651505f7 e0323c01d3a15016d7a0e390420a9518211542ba8e8380b3be5bae2aab7ad718 comp53.tgz SHA256 (etc53.tgz) = 443f72e113ec652574965e9c43b17644e96080d609e16db59d972fcfdb7a8ec4 d43c6f648586a6c1f1123df42693fb0ea6378c11d18c6f275374fa04ed6eb435 etc53.tgz SHA256 (game53.tgz) = 4fa2e9027a6c54a98bf6bc220a0cf385a9f53b5e0aea5067bcb3a57946bc51f6 5b3ed56e84fdae1576df27649a756cb5ac1cc88fb295bbae618623525836903f game53.tgz SHA256 (man53.tgz) = 5f3cfea012a5d44bb70197f2cd8c7febc5a9eccdd6a791774bbafe0d33e96602 1ab44139148acc480a21765f5d30bc3d94d7b18349019aa0e04069aa64293909 man53.tgz But, strangely enough, their all good for the rd kernel, the x* series and the install isos. Also the erroneous shasums are consistent across all three mirrors... Having never encountered this issue before I'm not too sure how suspicious I should be Kind regards, Toby I had the same problem yesterday. I'm not sure if it's a real problem or a hack.
Re: Snapshot shasum mismatch
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 cksum: cannot open cd53.iso: No such file or directory (SHA256) cd53.iso: FAILED (SHA256) cdboot: OK (SHA256) cdbr: OK (SHA256) comp53.tgz: FAILED (SHA256) etc53.tgz: FAILED cksum: cannot open floppy53.fs: No such file or directory (SHA256) floppy53.fs: FAILED (SHA256) game53.tgz: FAILED cksum: cannot open install53.iso: No such file or directory (SHA256) install53.iso: FAILED (SHA256) man53.tgz: FAILED cksum: cannot open pxeboot: No such file or directory (SHA256) pxeboot: FAILED (SHA256) xbase53.tgz: OK (SHA256) xetc53.tgz: OK (SHA256) xfont53.tgz: OK (SHA256) xserv53.tgz: OK (SHA256) xshare53.tgz: OK But I can't comment on the why or whether it is expected. I do know I have seen this happen in the past. -pk > 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 > one... > > Here are some examples: > > SHA256 (base53.tgz) = > b46c621ae4be7183ab90279d887748d69b4822a309ede81067abbe7adf0b7c5c > > > fd29dadcf424335e8614745e5dd6a9a88ad8b893decc4b5b4c0ffed26dda891c > base53.tgz > > SHA256 (bsd) = > 630e5b962a035abe5f25161895bd375979d6907b438d439ccb8e43a7d80f89e0 > > > 2de329fc109816fd8a810b0d6a411bad3710f8bb476f213ffc9e3d5d20ac2db2 bsd > > SHA256 (bsd.mp) = > fbca7ad263c42a0265ddce05b030a9168e3d74bbac0fd3195acc75ec301e5040 > > > af34f3faeeb26d8d7f22ed44edeb90fd17980c64d3148c44b4ec6ebcb416341a bsd.mp > > SHA256 (comp53.tgz) = > 6229bbb09a5c1a4d5d761b86c133c15e688abc85c3e6adc6421aa46c651505f7 > > > e0323c01d3a15016d7a0e390420a9518211542ba8e8380b3be5bae2aab7ad718 comp53.tgz > > SHA256 (etc53.tgz) = > 443f72e113ec652574965e9c43b17644e96080d609e16db59d972fcfdb7a8ec4 > > > d43c6f648586a6c1f1123df42693fb0ea6378c11d18c6f275374fa04ed6eb435 etc53.tgz > > SHA256 (game53.tgz) = > 4fa2e9027a6c54a98bf6bc220a0cf385a9f53b5e0aea5067bcb3a57946bc51f6 > > > 5b3ed56e84fdae1576df27649a756cb5ac1cc88fb295bbae618623525836903f game53.tgz > > SHA256 (man53.tgz) = > 5f3cfea012a5d44bb70197f2cd8c7febc5a9eccdd6a791774bbafe0d33e96602 > > > 1ab44139148acc480a21765f5d30bc3d94d7b18349019aa0e04069aa64293909 man53.tgz > > But, strangely enough, their all good for the rd kernel, the x* series and > the install isos. Also the erroneous shasums are consistent across all > three mirrors... > > Having never encountered this issue before I'm not too sure how suspicious > I should be > > Kind regards, > Toby
